.-.-.-.-.-

PK� �\�b�o����bulgarian/errmsg.sysnu�[�����Ɨ�3Dr��
K���
7X���B���Q���Cb���L������I^n����		%	K	g	�	�	�	
'
D
i
�
�
�
�
(U���=��-
B
`
w
�
�
U��
B`�Dw���-Y��Ik�+Gx���Pt�����.o�2Vx���\��e��K}���F��%���,d�)I���Cn���% [ � � !C!�!�!/"�"�"�"#y#�#�#�#*$Q$z$�$�$%K%n%�%�%�%�%.&�&�&�&3'q'�'H(�(�(g)�)�)*Q*�*�*+U+o+�+�+1,f,�,�,-2-Y-�-�-�-._.�.�./e/�/�/0C0o0�0�01T1x1�1�1�12T22�2�2�23?3�3�34F4a4�4�4	5j5�5�5�56m6�6�6�6-7\7�7�78g8�849�9:[:;W;v;�;�;	<%<�<�<=4=�=�=>8>�>�>$?C?l?�?�?�?0@\@�@�@�@�@�@AA4A[A�A�A�AEB�B�BC2CQCrC�C�C�C�C�CD0DdD|D�D�D�D�D�D#EiE�E�E�E
FDF~F�FG?G[G}G�G�GH:H�HIPI�IJ@JWJnJ�J�J�JK(KiK�K�K�K:L\L�L�L�L
MM9McM�M�M�MN*N\N�N�N�NO1OcO�O�O�O5PeP�P�P�P-QhQ�Q�QOR�R�R�R�R8StS�S�ST>T�T�TU�U�V(W�W�WXbX�X�XYjY�Y�YJZ�Z[W[�[�[8\_\|\�\�\]�]�]�^�^�^h_�_�_7`�`�`apa�ab�b�bc1c�c�c�cdCdmd�d�d�d�d4e�e�e�e9fzf�f"g|g�g�g/hoh�h�hYi�i�i�i]j�j�jk<kvk�k�k6lql�l�l,m�m�mnLnrn�n�n=o�o�o pEpnp�p�p�pDq�q�q2rmr�r�r�rss+sas�sttMt�tu'udu|u�u�u�uv>vYvyv�vw:wcww�w�w2xqx�xy�y�yAz�z�z�z{0{b{{{�{4|P|�|�|�|}-}q}�}�}(~Z~�~9w���U�ҀV����� �0�K�g�{������&�f���Ӄ�I�y���ׄ4�]������7�b���Ć܆��2�p�އ�r�����H�{�������� �H�~�������?�j���ʋ��0���ߌ�@�j�������D���ĎO�����O���t��}����F���
�r����e���ڗ�@�w�����M���љ�?�`����T���ϛ�(�Q����+�g����&����&�i���Ҡ��ס����_�4��R���çè�C����]�Ū�;�s���ܫ��,����Y�������M��&�S������$�w���2���*�C�����'�����3�}�̵;���ö,�y������a��L����[�����R���k���ɽ�����<�q���s����)�g��������9�����#�v���������
�*�\�o�������,���/������i������q���J�����Z�z���v�����C����������
�)�i�������D��������B��>���������\�����+�e����j���r���-���,�J�����5��������� ������������E�����2�����C������,�_������/�����H�������=����N������]��������O�����?�h��������A�i��������.�Z���.����8�`�������_���7�K�y����@������K���W�����k����^������h�����n�����7��.e��D���Gv�W�+��^��� :\x��Ed
	:	i	�	�	P
�
c�"T��
b
�
�
Xs�P��T��K}�?}��� S�����G����'X�������.[��;�]�Yx&M�����  � 
!K!u!�!�!�!"<"?"\"r"�"�"�"#�#\$�$%5%�%b&�&�&@'�'�(�(<)�)�)*C*u*�*�*�*&+H+}+�+�+N,k,�,�,^-�-.�.�.�./9/U/�/�/0L0w0�0�0,1|1�12C2�2�223�3�3N4�4�4�415^5�5�5636^6t6�6�6�6�6A7�7�798l8�8�8\9�9�9:�:�:;�;<�<^=�=�=�=,>{>�>�>0?z?�?]@�@�@A}A�AB\B�B�B3C�C�CDMD�D�D,EXE�E�EFNF�F�FG:GnG�GHXH�H�H�HIcI�IJOJ�JJK�K�K�K'LmL�LMkM�M�MyN�N�NDOP�PXQ�Q�R�R%SESnS�S�S�ST+TJTjT�T�T�TUAUzU�U�UVbV�V�V[W�W�W�X�X�X*Y�Y�YZ�Z�Z�[�[\2\d\�\�\0]^]�]�]�]<^|^�^_._s_#`X`f`�`aPala�a�ab^b�b�b�b{c�c�c!d�d�e�efif�f�g h�h�h�hFi�i7jyj�jdklPl�l�l=mkm�m�mYn�n�o|pOq�qs6sqs�s
t�t�t+uou�u�uvWv�v�v+w�w/x�x�xyZy�y�yz|z�z�{(|u|�|=}�}P~�~+b��2�j���Հ(����Q����M�����݃ �e���?�7����?���Ǌ�c����9�a���ی���Ս�t��V�ۏ_���Ԑ��Z�ۑ+�Ԓ�9�y�ē�g�Ɣ�M���ʕ�$�I������������U����R����*�e�����j����)�Y�����ϝ�V����(�q����&�j���Ҡ%�y���(���?���ڣ	�������;�����l���Ӧ����d�ƨ��L����0�o���Ϊ+���.�������� �U������g���8�����s��<���ֲ<����R�`���޴�r���^����>���h��m��J������Ƽ,���/��l��*����@�t����P���
����G�i�#���������K�l�����:���7����K�������Q������o���o���z�����P�����
�?�s���
�9�j��������d�����C���C���R���i��I��O���������Y������X���W�����U�����p���$���N�����U�m������E�v�������B�r�
�����N�����J���P��i���9��� ���s�Z��m�� ����h���z��U�����2������Dl�0���H���@�3S��]�[�	6	�	�	3
m
%���>�
�
��;J~���"Ku��9���~��/���,Jg��8d�����(It���2Dz���G`��1�!Kt��(.���!O���f�A�e ,!S!w!�!="�"�"#�#�#�$�$�$
%;%U%�%�%�%n&�&_'�'G(�(
)J)�)�)�)*O*�*�*"+?+�+�+@,x,�,�,�,�,�,*-`-�-.�.�.�.�.�.�./*/�/�/�/�/�/0H0�0�0�0Y1{1�1�1&2_2~2�2�223e3�3�3G4`4�5�5�6�67�7w8�89?9e9�9�9�9:b:�:�:�;�;<<�<�<#=M=~=�=�=+>`>�>�?D@G@�@�@DA{A�A�A�AAB�B�BCbC�C�CDND�D�D�D�DEkE�E�E�EfF|F�F�FGXGG�G�G�G�G�G~H�I�I�I:JK�K9L_L�L�L�LMKMmM�M�M�M
NENwN�N�N�N�NO;O{O�O�OQPqP�P�P�PQ/Q[Q�Q�Q�QR:ReR�R�R�RS6SjS�S�S�STNT�T�T�TVU�U�U�UV[VxV�V�V�V	W.W]W�W�W�WSX�X�X>Y�Y�YZ`Z�ZN[�[\�\]�]�]Z^<``�`sa�ab4bwb�b�b;c�c�c�c\d�d�d5e�e�f�f�f+g�ghQhhh�h�h�hi-iVi�i�i�iBj�j�jkTkk�kl�l�lLm�mn/nan�n�n�n.oto�opSp�pq�q�q�qAr�r�rsCsts�s�tbuv�v&w[w�w�w�w�w<xGxJx�x�xyzy�yz�z{m{�{�{|5}Z}�}�} ~Q~]~�~v"�[���ۀ
�I�Á��?�u���
�~�����K����6�p����J�j���w��#�H�_���ވ7��������<������Q�o���ы���~�Č�0�y�̍�L��ӎT��������5�]����������Y�������5�x����7�^���є��)�Z�|����3�����Ֆ��=��������5�p�К�b�����F������~��X�������?�^���$�
�����5���5�`�����ڦ=�i�ͧ�3�]�x�&�i�������Ԫ6�W�������y��ҭ�$�ݮ{�ȯ/�x����ݱ���_�����.�^���ɴ�s�<���Ͷ�6�`�ŷ#�7�K�y���Ǹ��*�W�������a�Ⱥ���`����A����?�l�����V�����I�w�߿H����;�������H�z����M�����}���-�g�v�y�|�����	�$�Y�������R���W�~����;�Z�������.�h������8���_������G�������?�q������=�h��������� �X��������Y���(�n�����#�X�|����N��������K�j�������k��������.�G�t������+�S��������� �@�m�������4�Y��������I������>��������>�_���&�<�R�����2����~��������?�`�x������q�����A�|���!�P������7����y�9�w����6�����������}��� �~������^�������%�\������W�����&�i�����'�������M�o�����)����������������D�\�����������;���L�}�����V�����������B�����Z������8]��>�^���2YQ�9�1e��,q�)}��	O	�	�	
G
a
~
5s�\w��-
U
y
�
�
0[n��x��_���Ai���(~�
M���Gz�1��
N��5e��0�� Im��	2Z|�Y��
e���k���+ U { � !F!i!�!�!�!,"�"G#�#b$�$�$�$%u%�%n&�&'g'�'�'(C(�(�(:)�)C*�*p+�+�+,J,N,R,V,Z,^,b,�,�,�,�,--t-�-�-�-�-9.S.f.�.�.u/�/'0y0�0�0�0%1}1�1�12W2�2�243�3�3�3C4�4?56�6�678778m8�8�8�89$9F9�9�9�9-:L:m:�:�:�:�:";E;T;g;z;�;�;�;6<Y<{<�<�<�<"=U=|=�=�=�=">c>>�>�>�>
?/?Z?�?@+@[@�@�@-ASA�A�A�A
B]B{B�B�BCPC�C�C�C�CD}D�D�D$E9EeE�E�EF:F{F�F�F�FGRG�G�G�G�G�G�G�H�H�I(JIJrJ�J�J&KUK�K�K�K8L;LkL�L�L*MUM�M�M�M�MN2NKNmN�N�N�N
ORO~O�O�OPP@P_PgPqP�P�P	Q&Q�Q�Q�Q{R�R�RS2S5S8S;SbS�STATkT�T�TV�V�V�WQXcY�Y�Y�YAZYZ�Z�Z�Z	[$[b[�[�[�[$\Q\~\�\�\7]X]v]�]�]^(^�^�^_/_N_p_�_�_�_�_`3`e`�`�`
a<a|a�a�abCb�b�b�b
c%c=c�c�c�c�cAd�d�d�de5eGebeue�e�e�e	f-fUf�f�f�f.g[g�g�g�gh?h�h�h�hYiWj�j�jkFk~k�k�klTl�l�l!m2m�m�m�m
n3ndn�n-o-p|p�p�pq=q~q�q�q�qr4rMr�r�r�r�r�rEs}s�s�s�s�s-tDt�t�t2uku�uNv�vwKw3x�x�xyyz_z�z&{]{�{�{�|:}�}�}#~G~�~�~%W���p�����V���ށ�7�����8��������D����?�s�Ԇ:����y��\�щH�z�%�q������Ȍ����6�\������*�p����$�a���Ɛ��ϑ�/�?���J�ԕ��<�Y��'������4�p����$�}�����u��i����I���^���6�ܟr�����~����,�a���A���P�ѥ1����A�g���ħ�x�ݨ7���ҩ>���ԪA����a�Ӭ��1�M�j�������1�t��`����3�`����]�N��E����2���1���U��I������H�����i�ۺF�}�����e�ͼm�����6����-�z�Ϳ�S��-�|��V�����L�����+����U��h����G������K���e���L�����`�������p���3�k������E�o������S������������.������I�v���b�����?��� �2�g�����Z���i���������q����h�����N�����4������n�������D�~�������J������x���6�X���������7�{�����q�t���'�����5�^������D�[�o����������,�K�r������L�p������F�[������6�s����:�������,�l������M��������=�r�������"�P������N�o������;�X��,�f��h�����'�K�����<�]�~������������������������	��������!�$�'�*�-�0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{������������������������ �#�&�)�,�/�2�5�8�;�e�h�k�n�q�t�w�z�}����������������������������������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|��������������

"%(+.147:=@CFILORUX[^adgjmpsvy|�������������������������������������Ai��:qtwz}���X��a��^�Yy��1	I	�
��Q��������

"
%
(
+
.
1
4
7
:
=
@
C
F
I
L
O
R
U
X
[
^
a
d
g
j
m
"%(+.147\_behknqtwz}�����������ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKN������������������������������ #&),/258;>ADGJMPSVY\_behknqtwz���z}�����������������������*\�H��P�:i��	!8f��
7�6c��
C�0`Gz��� _ � � � � !!!!!!!$!�!#"{"�"#3#�#�#$,$E$�$�$?%W%�%�%�&'S'�''(P(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))
)
)))))))")%)()+).)1)4)7):)=)@)C)F)I)L)O)R)U)X)[)^)a)d)g)j)m)p)s)v)y)|))�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)A*D*G*J*M*P*S*V*Y*\*_*b*e*h*k*n*q*t*w*z*}*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++
+
+++++++"+%+(+++.+1+4+7+:+=+@+C+F+I+L+O+R+U+X+[+^+a+d+g+j+m+p+s+v+y+|++�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,	,,,,,,,,!,$,',*,-,0,3,6,9,<,?,B,E,H,K,N,Q,T,W,Z,],`,c,f,i,l,o,r,u,x,{,~,�,�,�,�,�,�,�,�,-�-�-.\.�.�./W/�/�/�//0N0g0x0�0�01\1�1�1�1�1A2]2}2�2�2�23_3�3�3$4B4]4}4�4�415�5�5�566�6�6Y7�7858e8�8�8�89I9�9�9%:B:c:;<;�;�;�;�;�;�;�;�;�;�;�;M<k<n<====h=�=�=>.>�>U@�@�@<A�AJBRC�C�CDEDHDKD�D�E,FbG�G�G�GH9HTHWHZH]H`HcHfHiHlHoH�H�H�HII;I>IgIjI�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�IJJJ	JJJJJJJJ!J$J'J*J�J�J�J�J�J�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�KGLJL
M�M�M�M�M�M�M
N<N\N�N�N�NO/OkO�OAPDPGPJPMPPPSPVPYP\P_P�P�P�P�Q�Q�QR�ROS2TpT�UV�V|W�W�W	X,Y�Y)ZNZ�Z�Zr[�[	\\-\T\�\�\�\�\+]w]�]�]�]^�^_`_}_�_�_`/`^`�`�`�`La�a1b3b�b�b%c�c�cGdWdZd�d�d�d�d
e]ese�e_f�fg<gRg�g�g�ghQh�h�h3ibi�ij{j�j�j"k@kZk]k�k�k!l?lfl�l�l�l�lmm!m$m'm*m-m0m3m�m�mKn�n�n$o�o*p�p�p�pqLqq�qYr�rs�s�s�t�t�t7u�u�u(v�v"wcw�w�w)xZxy>y_y�yzHz�zt{�{}�}~�~�~3Hd��7�[������ �i�����Áށ�ɂ	��+�c�s������+�v���,�Q�����X���Ɇ�g�ć*�d���߈W�̉�~�ՊF�}����3�������\�֎F����G���֐6�|����L�j��I���ߓ�Q����]�`���ʕ&�y���ږ�6�E���՗J�f�����ט'�g���֙�C�Y�n������$�v���M�y�̝S����f��|��������d��`����)�N�j������$�A�v���D�j���ݦ�a����������ĩ�D�y���ժ�4���ū�T�~�ج2���̭%�@��J�¯'���B�n�ñ�[�������$�E�����C����?�k����(����������3�^������������&�����:�r�ջ�.�˽Z���ݾ^���ؿB������M�w��������3����_���������J��F�����M����d��g���?���;�����@�u���=�~����3��������M���F����������M���<�h�k������������������������� �#�&�)�,�/�������(�+�.�1�4�7�������!�C�F�i�������4�\���/�2�	�a�����G���h���g����\���L��h���)�����$�}��� �n����l���������������������������������������������������������������������������B������F�������(�����b����������7�U�s���%�W�s���������G����q���������H����P�^�a�d�g����8�}�h��E����Y�2� o�b�#R�pFx�Q	�	�	�
p��F
�
���o�(P��e��T�Z�I��c���z�#&l��+�:�T � � !:!�!�!�"�#�$z%�&�&�'2(�(G)�)�)�)*,*_*�*+K+�+�+�+,,1,�,>.[.�.�.�.//R/�/�/<0�0�0Z1�12�3416�6U7�7�7u8�8�9W:�:;I;�;7<u<�<�=>�>�>�>�>?~?�?�?�?�?r@�@
A
AA�A�B#CQC�C�CDaD�D�D�E�E,F�FGPG�GMHI�IlJDKLeL�L�L+MmM�M�M�M NENxN�N�NO�O*P|P�P�P@QfQ�Q�Q�QR_R�RmS-T�T�WZ>ZoZ�Z�Z6[�[�[C\|\�\]�]]^�^�_?`�`a�a�a�a�a(b�b�b=cac�c�cNd�d�d�d�d'ece�e�e�e�e�ef"f5f�f;g�g�gAh�h�ikXk=mOm_m�m�m�mn2n�noo�oXp�pqVq�qrVr�r�r)s�s�sst�t�uNv�v�v3wnwqw.x�x1y�y"z�z�zB{�{j|�|Y}�}�}a~�~�~8���<�e���݀	�5�p�ԁ ����V����x�Ƅ'�E�g�r����������$�R�m�Ն����i�����}�������+�ɋ=�l�����ˍk���������V�א��)������E���ٓ��6�����hashchkisamchkNOYESCan't create file '%-.200s' (errno: %d - %s)Can't create table '%-.200s' (errno: %d - %s)Can't create database '%-.192s' (errno: %d - %s)Can't create database '%-.192s'; database existsCan't drop database '%-.192s'; database doesn't existError dropping database (can't delete '%-.192s', errno: %d - %s)Error dropping database (can't rmdir '%-.192s', errno: %d - %s)Error on delete of '%-.192s' (errno: %d - %s)Can't read record in system tableCan't get status of '%-.200s' (errno: %d - %s)Can't get working directory (errno: %d - %s)Can't lock file (errno: %d - %s)Can't open file: '%-.200s' (errno: %d - %s)Can't find file: '%-.200s' (errno: %d - %s)Can't read dir of '%-.192s' (errno: %d - %s)Can't change dir to '%-.192s' (errno: %d - %s)Record has changed since last read in table '%-.192s'Disk full (%s); waiting for someone to free some space... (errno: %d - %s)Can't write; duplicate key in table '%-.192s'Error on close of '%-.192s' (errno: %d - %s)Error reading file '%-.200s' (errno: %d - %s)Error on rename of '%-.210s' to '%-.210s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)'%-.192s' is locked against changeSort abortedView '%-.192s' doesn't exist for '%-.192s'Got error %d - '%-.192s' from storage engineTable storage engine for '%-.192s' doesn't have this optionCan't find record in '%-.192s'Incorrect information in file: '%-.200s'Incorrect key file for table '%-.200s'; try to repair itOld key file for table '%-.192s'; repair it!Table '%-.192s' is read onlyOut of memory; restart server and try again (needed %d bytes)Out of sort memory, consider increasing server sort buffer sizeUnexpected EOF found when reading file '%-.192s' (errno: %d - %s)Too many connectionsOut of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceCan't get hostname for your addressBad handshakeAccess denied for user '%-.48s'@'%-.64s' to database '%-.192s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)No database selectedUnknown commandColumn '%-.192s' cannot be nullUnknown database '%-.192s'Table '%-.192s' already existsUnknown table '%-.129s'Column '%-.192s' in %-.192s is ambiguousServer shutdown in progressUnknown column '%-.192s' in '%-.192s''%-.192s' isn't in GROUP BYCan't group on '%-.192s'Statement has sum functions and columns in same statementColumn count doesn't match value countIdentifier name '%-.100s' is too longDuplicate column name '%-.192s'Duplicate key name '%-.192s'Duplicate entry '%-.192s' for key %dIncorrect column specifier for column '%-.192s'%s near '%-.80s' at line %dQuery was emptyNot unique table/alias: '%-.192s'Invalid default value for '%-.192s'Multiple primary key definedToo many keys specified; max %d keys allowedToo many key parts specified; max %d parts allowedSpecified key was too long; max key length is %d bytesKey column '%-.192s' doesn't exist in tableBLOB column '%-.192s' can't be used in key specification with the used table typeColumn length too big for column '%-.192s' (max = %lu); use BLOB or TEXT insteadIncorrect table definition; there can be only one auto column and it must be defined as a key%s: ready for connections.
Version: '%s'  socket: '%s'  port: %d%s: Normal shutdown
%s: Got signal %d. Aborting!
%s: Shutdown complete
%s: Forcing close of thread %ld  user: '%-.48s'
Can't create IP socketTable '%-.192s' has no index like the one used in CREATE INDEX; recreate the tableField separator argument is not what is expected; check the manualYou can't use fixed rowlength with BLOBs; please use 'fields terminated by'The file '%-.128s' must be in the database directory or be readable by allFile '%-.200s' already existsRecords: %ld  Deleted: %ld  Skipped: %ld  Warnings: %ldRecords: %ld  Duplicates: %ldIncorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keysYou can't delete all columns with ALTER TABLE; use DROP TABLE insteadCan't DROP '%-.192s'; check that column/key existsRecords: %ld  Duplicates: %ld  Warnings: %ldYou can't specify target table '%-.192s' for update in FROM clauseUnknown thread id: %luYou are not owner of thread %luNo tables usedToo many strings for column %-.192s and SETCan't generate a unique log-filename %-.200s.(1-999)
Table '%-.192s' was locked with a READ lock and can't be updatedTable '%-.192s' was not locked with LOCK TABLESBLOB, TEXT, GEOMETRY or JSON column '%-.192s' can't have a default valueIncorrect database name '%-.100s'Incorrect table name '%-.100s'The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okayUnknown errorUnknown procedure '%-.192s'Incorrect parameter count to procedure '%-.192s'Incorrect parameters to procedure '%-.192s'Unknown table '%-.192s' in %-.32sColumn '%-.192s' specified twiceInvalid use of group functionTable '%-.192s' uses an extension that doesn't exist in this MySQL versionA table must have at least 1 columnThe table '%-.192s' is fullUnknown character set: '%-.64s'Too many tables; MySQL can only use %d tables in a joinToo many columnsRow size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBsThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if neededCross dependency found in OUTER JOIN; examine your ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerCan't load function '%-.192s'Can't initialize function '%-.192s'; %-.192sNo paths allowed for shared libraryFunction '%-.192s' already existsCan't open shared library '%-.192s' (errno: %d %-.128s)Can't find symbol '%-.128s' in libraryFunction '%-.192s' is not definedHost '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.255s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192s'Invalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be usedThe host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionYou have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to useDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used storage engine can't index column '%-.192s'Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't existCan't write, because of unique constraint, to table '%-.192s'BLOB/TEXT column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe storage engine for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDuplicate entry '%-.64s' for key '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAccess denied for user '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsТрябва първо да си смените паролата със SET PASSWORD за да можете да изпълните тази командаFailed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDuplicate entry for key '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEПаролата ви е изтекла. За да влезете трябва да я смените използвайки клиент който поддрържа такива пароли.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryОтказан достъп при опит за смяна към потребител %-.48s'@'%-.64s' (използвана парола: %s). Затваряне на връзката.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.Инициализационния вектор подаден на %s е прекалено къс. Трябва да е поне %d байтаPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Клеймото за версия %.*s не съвпада. Правилната стойност е %.*sНе е намерено клеймо за версия %.*sVariable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'Избрания метод за удостоверяване %.*s не поддържа изтичане на паролиInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Приставката '%s' не може да се използва като ранна приставка. Не я добавайте в --early-plugin-load и т.н.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sЗададената папка за базата %s е неизползваема. Можете да изтриете файловете които сървъра добави в нея.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Функцията от SSL библиотеката %s върна грешка. Това обикновено е защото SSL библиотеката вече е била използвана. Заради това SSL паметта няма да се инструментира.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sПриставката '%s' не може да се използва като ранна приставка. Не я добавайте в --early-plugin-load и т.н.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sНовосъздадената от --initialize папка за базата %s е неизползваема. Можете да я изтриете.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�c\ELELcharsets/Index.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
  Copyright (c) 2003, 2025, Oracle and/or its affiliates.

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

This program is designed to work with certain software (including
  but not limited to OpenSSL) that is licensed under separate terms,
  as designated in a particular file or component or in included license
  documentation.  The authors of MySQL hereby grant you an additional
  permission to link the program and your derivative works with the
  separately licensed software that they have either included with
  the program or referenced in the documentation.

Without limiting anything contained in the foregoing, this file,
  which is part of C Driver for MySQL (Connector/C), is also subject to the
  Universal FOSS Exception, version 1.0, a copy of which can be found at
  http://oss.oracle.com/licenses/universal-foss-exception.

This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License, version 2.0, for more details.

You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software
  Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA
</copyright>

<description>
This file lists all of the available character sets.
To make maintaining easier please:
 - keep records sorted by collation number.
 - change charsets.max-id when adding a new collation.
</description>

<charset name="big5">
  <family>Traditional Chinese</family>
  <description>Big5 Traditional Chinese</description>
  <alias>big-5</alias>
  <alias>bigfive</alias>
  <alias>big-five</alias>
  <alias>cn-big5</alias>
  <alias>csbig5</alias>
  <collation name="big5_chinese_ci"	id="1"	order="Chinese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="big5_bin"	id="84"	order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="latin2">
  <family>Central European</family>
  <description>ISO 8859-2 Central European</description>
  <alias>csisolatin2</alias>
  <alias>iso-8859-2</alias>
  <alias>iso-ir-101</alias>
  <alias>iso_8859-2</alias>
  <alias>iso_8859-2:1987</alias>
  <alias>l2</alias>
  <collation name="latin2_czech_cs" 	id="2"	order="Czech" flag="compiled"/>
  <collation name="latin2_general_ci"	id="9"	flag="primary">
    <order>Hungarian</order>
    <order>Polish</order>
    <order>Romanian</order>
    <order>Croatian</order>
    <order>Slovak</order>
    <order>Slovenian</order>
    <order>Sorbian</order>
  </collation>
  <collation name="latin2_hungarian_ci"		id="21"	order="Hungarian"/>
  <collation name="latin2_croatian_ci"		id="27"	order="Croatian"/>
  <collation name="latin2_bin"	id="77"	order="Binary"	flag="binary"/>
</charset>

<charset name="dec8">
  <family>Western</family>
  <description>DEC West European</description>
  <collation name="dec8_bin"		id="69"	order="Binary"	flag="binary"/>
  <collation name="dec8_swedish_ci"	id="3"	flag="primary">
    <order>Dutch</order>
    <order>English</order>
    <order>French</order>
    <order>German Duden</order>
    <order>Italian</order>
    <order>Latin</order>
    <order>Portuguese</order>
    <order>Spanish</order>
  </collation>
</charset>

<charset name="cp850">
  <family>Western</family>
  <description>DOS West European</description>
  <alias>850</alias>
  <alias>cspc850multilingual</alias>
  <alias>ibm850</alias>
  <collation name="cp850_general_ci"	id="4"	flag="primary">
    <order>Dutch</order>
    <order>English</order>
    <order>French</order>
    <order>German Duden</order>
    <order>Italian</order>
    <order>Latin</order>
    <order>Portuguese</order>
    <order>Spanish</order>
  </collation>
  <collation name="cp850_bin"	id="80"	order="Binary"	flag="binary"/>
</charset>

<charset name="latin1">
  <family>Western</family>
  <description>cp1252 West European</description>
  <alias>csisolatin1</alias>
  <alias>iso-8859-1</alias>
  <alias>iso-ir-100</alias>
  <alias>iso_8859-1</alias>
  <alias>iso_8859-1:1987</alias>
  <alias>l1</alias>
  <alias>latin1</alias>
  <collation name="latin1_german1_ci"	id="5"	order="German Duden"/>
  <collation name="latin1_swedish_ci"	id="8"	order="Finnish, Swedish">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="latin1_danish_ci"	id="15"	order="Danish"/>
  <collation name="latin1_german2_ci"	id="31"	order="German Phonebook"	flag="compiled"/>
  <collation name="latin1_spanish_ci"	id="94"	order="Spanish"/>
  <collation name="latin1_bin"		id="47"	order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="latin1_general_ci"	id="48">
    <order>Dutch</order>
    <order>English</order>
    <order>French</order>
    <order>German Duden</order>
    <order>Italian</order>
    <order>Latin</order>
    <order>Portuguese</order>
    <order>Spanish</order>
  </collation>
  <collation name="latin1_general_cs"	id="49">
    <order>Dutch</order>
    <order>English</order>
    <order>French</order>
    <order>German Duden</order>
    <order>Italian</order>
    <order>Latin</order>
    <order>Portuguese</order>
    <order>Spanish</order>
  </collation>
</charset>

<charset name="hp8">
  <family>Western</family>
  <description>HP West European</description>
  <alias>hproman8</alias>
  <collation name="hp8_bin"		id="72"	order="Binary"	flag="binary"/>
  <collation name="hp8_english_ci"	id="6"	flag="primary">
    <order>Dutch</order>
    <order>English</order>
    <order>French</order>
    <order>German Duden</order>
    <order>Italian</order>
    <order>Latin</order>
    <order>Portuguese</order>
    <order>Spanish</order>
  </collation>
</charset>

<charset name="koi8r">
  <family>Cyrillic</family>
  <description>KOI8-R Relcom Russian</description>
  <alias>koi8-r</alias>
  <alias>cskoi8r</alias>
  <collation name="koi8r_general_ci"	id="7"	order="Russian"	flag="primary"/>
  <collation name="koi8r_bin"		id="74"	order="Binary"	flag="binary"/>
</charset>

<charset name="swe7">
  <family>Western</family>
  <description>7bit Swedish</description>
  <alias>iso-646-se</alias>
  <collation name="swe7_swedish_ci"	id="10"	order="Swedish"	flag="primary"/>
  <collation name="swe7_bin"		id="82"	order="Binary"	flag="binary"/>
</charset>

<charset name="ascii">
  <family>Western</family>
  <description>US ASCII</description>
  <alias>us</alias>
  <alias>us-ascii</alias>
  <alias>csascii</alias>
  <alias>iso-ir-6</alias>
  <alias>iso646-us</alias>
  <collation name="ascii_general_ci"	id="11"	order="English"	flag="primary"/>
  <collation name="ascii_bin"		id="65"	order="Binary"	flag="binary"/>
</charset>

<charset name="ujis">
  <family>Japanese</family>
  <description>EUC-JP Japanese</description>
  <alias>euc-jp</alias>
  <collation name="ujis_japanese_ci"	id="12"	order="Japanese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="ujis_bin"	id="91"	order="Japanese">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="sjis">
  <family>Japanese</family>
  <description>Shift-JIS Japanese</description>
  <alias>s-jis</alias>
  <alias>shift-jis</alias>
  <alias>x-sjis</alias>
  <collation name="sjis_japanese_ci" 	id="13"	order="Japanese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="sjis_bin" 	id="88"	order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="cp1251">
  <family>Cyrillic</family>
  <description>Windows Cyrillic</description>
  <alias>windows-1251</alias>
  <alias>ms-cyr</alias>
  <alias>ms-cyrillic</alias>
  <collation name="cp1251_bulgarian_ci"	id="14">
    <order>Belarusian</order>
    <order>Bulgarian</order>
    <order>Macedonian</order>
    <order>Russian</order>
    <order>Serbian</order>
    <order>Mongolian</order>
    <order>Ukrainian</order>
  </collation>
  <collation name="cp1251_ukrainian_ci"	id="23"	order="Ukrainian"/>
  <collation name="cp1251_bin"		id="50"	order="Binary"	flag="binary"/>
  <collation name="cp1251_general_ci"	id="51" flag="primary">
    <order>Belarusian</order>
    <order>Bulgarian</order>
    <order>Macedonian</order>
    <order>Russian</order>
    <order>Serbian</order>
    <order>Mongolian</order>
    <order>Ukrainian</order>
  </collation>
  <collation name="cp1251_general_cs"	id="52">
    <order>Belarusian</order>
    <order>Bulgarian</order>
    <order>Macedonian</order>
    <order>Russian</order>
    <order>Serbian</order>
    <order>Mongolian</order>
    <order>Ukrainian</order>
  </collation>
</charset>

<charset name="hebrew">
  <family>Hebrew</family>
  <description>ISO 8859-8 Hebrew</description>
  <alias>csisolatinhebrew</alias>
  <alias>iso-8859-8</alias>
  <alias>iso-ir-138</alias>
  <collation name="hebrew_general_ci"	id="16"	order="Hebrew"	flag="primary"/>
  <collation name="hebrew_bin"		id="71"	order="Binary"	flag="binary"/>
</charset>

<charset name="tis620">
  <family>Thai</family>
  <description>TIS620 Thai</description>
  <alias>tis-620</alias>
  <collation name="tis620_thai_ci"	id="18"	order="Thai">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="tis620_bin"	id="89"	order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="euckr">
  <family>Korean</family>
  <description>EUC-KR Korean</description>
  <alias>euc_kr</alias>
  <alias>euc-kr</alias>
  <collation name="euckr_korean_ci"	id="19"	order="Korean">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="euckr_bin"	id="85">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="latin7">
  <family>Baltic</family>
  <description>ISO 8859-13 Baltic</description>
  <alias>BalticRim</alias>
  <alias>iso-8859-13</alias>
  <alias>l7</alias>
  <collation name="latin7_estonian_cs"	id="20">
    <order>Estonian</order>
  </collation>
  <collation name="latin7_general_ci"	id="41">
    <order>Latvian</order>
    <order>Lithuanian</order>
    <flag>primary</flag>
  </collation>
  <collation name="latin7_general_cs"	id="42">
    <order>Latvian</order>
    <order>Lithuanian</order>
  </collation>
  <collation name="latin7_bin"	id="79"	order="Binary"	flag="binary"/>
</charset>

<charset name="koi8u">
  <family>Cyrillic</family>
  <description>KOI8-U Ukrainian</description>
  <alias>koi8-u</alias>
  <collation name="koi8u_general_ci"	id="22"	order="Ukrainian"	flag="primary"/>
  <collation name="koi8u_bin"		id="75"	order="Binary"	flag="binary"/>
</charset>

<charset name="gb2312">
  <family>Simplified Chinese</family>
  <description>GB2312 Simplified Chinese</description>
  <alias>chinese</alias>
  <alias>iso-ir-58</alias>
  <collation name="gb2312_chinese_ci"	id="24"	order="Chinese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="gb2312_bin"	id="86">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="greek">
  <family>Greek</family>
  <description>ISO 8859-7 Greek</description>
  <alias>csisolatingreek</alias>
  <alias>ecma-118</alias>
  <alias>greek8</alias>
  <alias>iso-8859-7</alias>
  <alias>iso-ir-126</alias>
  <collation name="greek_general_ci" 	id="25"	order="Greek"	flag="primary"/>
  <collation name="greek_bin"		id="70"	order="Binary"	flag="binary"/>
</charset>

<charset name="cp1250">
  <family>Central European</family>
  <description>Windows Central European</description>
  <alias>ms-ce</alias>
  <alias>windows-1250</alias>
  <collation name="cp1250_general_ci"	id="26"	flag="primary">
    <order>Hungarian</order>
    <order>Polish</order>
    <order>Romanian</order>
    <order>Croatian</order>
    <order>Slovak</order>
    <order>Slovenian</order>
    <order>Sorbian</order>
  </collation>
  <collation name="cp1250_croatian_ci"	id="44">
    <order>Croatian</order>
  </collation>
  <collation name="cp1250_polish_ci"  id="99">
    <order>Polish</order>
  </collation>
  <collation name="cp1250_czech_cs"	id="34"	order="Czech">
    <flag>compiled</flag>
  </collation>
  <collation name="cp1250_bin"		id="66"	order="Binary"	flag="binary"/>
</charset>

<charset name="gbk">
  <family>East Asian</family>
  <description>GBK Simplified Chinese</description>
  <alias>cp936</alias>
  <collation name="gbk_chinese_ci"	id="28"	order="Chinese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="gbk_bin"	id="87"	order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="gb18030">
  <family>East Asian</family>
  <description>China National Standard GB18030</description>
  <alias>cp54936</alias>
  <collation name="gb18030_chinese_ci" id="248" order="Chinese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="gb18030_bin" id="249" order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="cp1257">
  <family>Baltic</family>
  <description>Windows Baltic</description>
  <alias>WinBaltRim</alias>
  <alias>windows-1257</alias>
  <collation name="cp1257_lithuanian_ci"	id="29"	order="Lithuanian"/>
  <collation name="cp1257_bin"			id="58"	order="Binary"	flag="binary"/>
  <collation name="cp1257_general_ci"		id="59"	flag="primary">
    <order>Latvian</order>
    <order>Lithuanian</order>
  </collation>
  
  
</charset>

<charset name="latin5">
  <family>South Asian</family>
  <description>ISO 8859-9 Turkish</description>
  <alias>csisolatin5</alias>
  <alias>iso-8859-9</alias>
  <alias>iso-ir-148</alias>
  <alias>l5</alias>
  <alias>latin5</alias>
  <alias>turkish</alias>
  <collation name="latin5_turkish_ci"	id="30"	order="Turkish"	flag="primary"/>
  <collation name="latin5_bin"		id="78"	order="Binary"	flag="binary"/>
</charset>

<charset name="armscii8">
  <family>South Asian</family>
  <description>ARMSCII-8 Armenian</description>
  <alias>armscii-8</alias>
  <collation name="armscii8_general_ci"	id="32"	order="Armenian"	flag="primary"/>
  <collation name="armscii8_bin"	id="64"	order="Binary"		flag="binary"/>
</charset>

<charset name="utf8">
  <family>Unicode</family>
  <description>UTF-8 Unicode</description>
  <alias>utf-8</alias>
  <collation name="utf8_general_ci"	id="33">
   <flag>primary</flag>
   <flag>compiled</flag>
  </collation>
  <collation name="utf8_tolower_ci"	id="76">
    <flag>compiled</flag>
  </collation>
  <collation name="utf8_bin"		id="83">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="ucs2">
  <family>Unicode</family>
  <description>UCS-2 Unicode</description>
  <collation name="ucs2_general_ci"	id="35">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="ucs2_bin"	id="90">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="cp866">
  <family>Cyrillic</family>
  <description>DOS Russian</description>
  <alias>866</alias>
  <alias>csibm866</alias>
  <alias>ibm866</alias>
  <alias>DOSCyrillicRussian</alias>
  <collation name="cp866_general_ci"	id="36"	order="Russian"	flag="primary"/>
  <collation name="cp866_bin"		id="68"	order="Binary"	flag="binary"/>
</charset>

<charset name="keybcs2">
  <family>Central European</family>
  <description>DOS Kamenicky Czech-Slovak</description>
  <collation name="keybcs2_general_ci"	id="37"	order="Czech"	flag="primary"/>
  <collation name="keybcs2_bin"		id="73"	order="Binary"	flag="binary"/>
</charset>

<charset name="macce">
  <family>Central European</family>
  <description>Mac Central European</description>
  <alias>MacCentralEurope</alias>
  <collation name="macce_general_ci"	id="38"	flag="primary">
    <order>Hungarian</order>
    <order>Polish</order>
    <order>Romanian</order>
    <order>Croatian</order>
    <order>Slovak</order>
    <order>Slovenian</order>
    <order>Sorbian</order>
  </collation>
  <collation name="macce_bin"	id="43"	order="Binary"	flag="binary"/>
</charset>

<charset name="macroman">
  <family>Western</family>
  <description>Mac West European</description>
  <alias>Mac</alias>
  <alias>Macintosh</alias>
  <alias>csmacintosh</alias>
  <collation name="macroman_general_ci"	id="39"	flag="primary">
    <order>Dutch</order>
    <order>English</order>
    <order>French</order>
    <order>German Duden</order>
    <order>Italian</order>
    <order>Latin</order>
    <order>Portuguese</order>
    <order>Spanish</order>
  </collation>
  <collation name="macroman_bin"	id="53"	order="Binary"	flag="binary"/>
  
  
  
</charset>

<charset name="cp852">
  <family>Central European</family>
  <description>DOS Central European</description>
  <alias>852</alias>
  <alias>cp852</alias>
  <alias>ibm852</alias>
  <collation name="cp852_general_ci"	id="40"	flag="primary">
    <order>Hungarian</order>
    <order>Polish</order>
    <order>Romanian</order>
    <order>Croatian</order>
    <order>Slovak</order>
    <order>Slovenian</order>
    <order>Sorbian</order>
  </collation>
  <collation name="cp852_bin"	id="81"	order="Binary"	flag="binary"/>
</charset>

<charset name="cp1256">
  <family>Arabic</family>
  <description>Windows Arabic</description>
  <alias>ms-arab</alias>
  <alias>windows-1256</alias>
  <collation name="cp1256_bin"		id="67"	order="Binary"	flag="binary"/>
  <collation name="cp1256_general_ci"	id="57"	order="Arabic"	flag="primary">
    <order>Arabic</order>
    <order>Persian</order>
    <order>Pakistani</order>
    <order>Urdu</order>
  </collation>
</charset>

<charset name="geostd8">
  <family>South Asian</family>
  <description>GEOSTD8 Georgian</description>
  <collation name="geostd8_general_ci"	id="92"	order="Georgian"	flag="primary"/>
  <collation name="geostd8_bin"		id="93"	order="Binary"		flag="binary"/>
</charset>

<charset name="binary">
  <description>Binary pseudo charset</description>
  <collation name="binary"	id="63"	order="Binary">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="cp932">
  <family>Japanese</family>
  <description>SJIS for Windows Japanese</description>
  <alias>ms_cp932</alias>
  <alias>sjis_cp932</alias>
  <alias>sjis_ms</alias>
  <collation name="cp932_japanese_ci"    id="95" order="Japanese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="cp932_bin"    id="96" order="Binary">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

<charset name="eucjpms">
  <family>Japanese</family>
  <description>UJIS for Windows Japanese</description>
  <alias>eucjpms</alias>
  <alias>eucJP_ms</alias>
  <alias>ujis_ms</alias>
  <alias>ujis_cp932</alias>
  <collation name="eucjpms_japanese_ci"    id="97" order="Japanese">
    <flag>primary</flag>
    <flag>compiled</flag>
  </collation>
  <collation name="eucjpms_bin"    id="98" order="Japanese">
    <flag>binary</flag>
    <flag>compiled</flag>
  </collation>
</charset>

</charsets>

PK� �\��^��charsets/READMEnu�[���This directory holds configuration files that enable MySQL to work with
different character sets.  It contains:

charset_name.xml
    Each charset_name.xml file contains information for a simple character
    set.  The information in the file describes character types,
    lower- and upper-case equivalencies and sorting orders for the
    character values in the set.

Index.xml
    The Index.xml file lists all of the available charset configurations,
    including collations.

Each collation must have a unique number.  The number is stored
    IN THE DATABASE TABLE FILES and must not be changed.

The max-id attribute of the <charsets> element must be set to
    the largest collation number.

Compiled in or configuration file?
    When should a character set be compiled in to MySQL's string library
    (libmystrings), and when should it be placed in a charset_name.xml
    configuration file?

If the character set requires the strcoll functions or is a
    multi-byte character set, it MUST be compiled in to the string
    library.  If it does not require these functions, it should be
    placed in a charset_name.xml configuration file.

If the character set uses any one of the strcoll functions, it
    must define all of them.  Likewise, if the set uses one of the
    multi-byte functions, it must define them all.  See the manual for
    more information on how to add a complex character set to MySQL.

Syntax of configuration files
    The syntax is very simple.  Words in <map> array elements are
    separated by arbitrary amounts of whitespace. Each word must be a
    number in hexadecimal format.  The ctype array has 257 words; the
    other arrays (lower, upper, etc.) take up 256 words each after that.
PK� �\�#�{{charsets/armscii8.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�ֺHmmcharsets/ascii.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\0�@""charsets/cp1250.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�f�@l"l"charsets/cp1251.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

<unicode>
<map>
 0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F
 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 001A 001B 001C 001D 001E 001F
 0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 002A 002B 002C 002D 002E 002F
 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 003A 003B 003C 003D 003E 003F
 0040 0041 0042 0043 0044 0045 0046 0047 0048 0049 004A 004B 004C 004D 004E 004F
 0050 0051 0052 0053 0054 0055 0056 0057 0058 0059 005A 005B 005C 005D 005E 005F
 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 006A 006B 006C 006D 006E 006F
 0070 0071 0072 0073 0074 0075 0076 0077 0078 0079 007A 007B 007C 007D 007E 007F
 0402 0403 201A 0453 201E 2026 2020 2021 20AC 2030 0409 2039 040A 040C 040B 040F
 0452 2018 2019 201C 201D 2022 2013 2014 0000 2122 0459 203A 045A 045C 045B 045F
 00A0 040E 045E 0408 00A4 0490 00A6 00A7 0401 00A9 0404 00AB 00AC 00AD 00AE 0407
 00B0 00B1 0406 0456 0491 00B5 00B6 00B7 0451 2116 0454 00BB 0458 0405 0455 0457
 0410 0411 0412 0413 0414 0415 0416 0417 0418 0419 041A 041B 041C 041D 041E 041F
 0420 0421 0422 0423 0424 0425 0426 0427 0428 0429 042A 042B 042C 042D 042E 042F
 0430 0431 0432 0433 0434 0435 0436 0437 0438 0439 043A 043B 043C 043D 043E 043F
 0440 0441 0442 0443 0444 0445 0446 0447 0448 0449 044A 044B 044C 044D 044E 044F

</map>
</unicode>

</charset>

</charsets>
PK� �\�[����charsets/cp1256.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\�%�v�$�$charsets/cp1257.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\%Immcharsets/cp850.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�?�}}charsets/cp852.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\[!����charsets/cp866.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\h�g�llcharsets/dec8.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\z�vdwwcharsets/geostd8.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\��=�KKcharsets/greek.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\���Wrrcharsets/hebrew.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\/ۈ,iicharsets/hp8.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�"!H��charsets/keybcs2.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\]�	qqcharsets/koi8r.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�oocharsets/koi8u.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\����=(=(charsets/latin1.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�%ա++charsets/latin2.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\#%ppcharsets/latin5.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\�Ikq��charsets/latin7.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>
PK� �\:�MYZ!Z!charsets/macce.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

<collation name="macce_ci">
<map>
 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
 40 41 4B 4D 53 57 63 65 69 6B 73 75 79 83 85 8D
 9B 9D 9F A7 AE B2 C0 C2 C4 C6 CA D2 D3 D4 D5 D6
 D7 41 4B 4D 53 57 63 65 69 6B 73 75 79 83 85 8D
 9B 9D 9F A7 AE B2 C0 C2 C4 C6 CA D8 D9 DA DB DC
 45 47 47 59 49 91 B6 43 49 4F 45 4F 51 51 59 CE
 CE 55 71 55 5B 5B 5D 8F 5D 99 91 97 B8 5F 5F B6
 DD DE 61 DF E0 E1 E2 AD E3 E4 E5 61 E6 E7 67 6F
 6F 6D E8 E9 6D 77 EA EB 7B 81 82 7F 7F 7D 7D 8B
 8B 87 EC ED 87 89 EE EF F0 F1 F2 89 93 97 93 95
 F3 F4 F5 F6 F7 F8 F9 FA 95 A1 A1 A3 FB FC A3 A5
 A5 A9 FD FE A9 AB AB 43 B0 B0 71 CC CC BC 8F 99
 BC B4 B8 B4 BA BA BE BE C8 C8 77 D0 7B D0 67 FF

</map>
</collation>

</charset>

</charsets>
PK� �\~�Xe!e!charsets/macroman.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

<collation name="macroman_ci_ai">
<map>
 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
 40 41 51 53 57 59 63 66 68 6A 75 77 79 7B 7D 81
 91 93 95 97 9A 9C A6 A8 AA AC B0 B2 B3 B4 B5 B6
 B7 41 51 53 57 59 63 66 68 6A 75 77 79 7B 7D 81
 91 93 95 97 9A 9C A6 A8 AA AC B0 B8 B9 BA BB BC
 41 41 53 59 7D 81 9C 41 41 41 41 41 41 53 59 59
 59 59 6A 6A 6A 6A 7D 81 81 81 81 81 9C 9C 9C 9C
 BD BE BF C0 C1 C2 C3 97 C4 C5 C6 C7 C8 C9 41 81
 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 41 81
 D8 D9 DA DB 63 DC DD DE DF E0 E1 41 41 81 81 81
 E2 E3 E4 E5 E6 E7 E8 E9 AC AC EA EB EC ED EE EF
 F0 F1 F2 F3 F4 41 59 41 59 59 6A 6A 6A 6A 81 81
 F0 81 9C 9C 9C 6A F6 F7 F8 F9 FA FB FC FD FE FF

</map>
</collation>

</charset>

</charsets>
PK� �\y8��mmcharsets/swe7.xmlnu�[���<?xml version='1.0' encoding="utf-8"?>

<copyright>
 Copyright (c) 2003, 2025, Oracle and/or its affiliates.
   Use is subject to license terms

This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License, version 2.0,
  as published by the Free Software Foundation.

</charset>

</charsets>

PK� �\��t����czech/errmsg.sysnu�[�����x��	R��
C��?v��)a��t�� k���@o���/L��*Ce��	<	_	r	�	�	�	�	 
G
m
�
�
�
Kn���	'Py��.
u
�
�
)u���Je�U��'��(Z���6���+U}.Jv���	V�����_��'Ts��|�!y���� J�!x�N�� N o � � !]!�!�!�!�!."e"�"�"#@#y#�#�#3$o$�$�$W%�%�%�%9&i&�&�&�&�&'5'N'�'�'�'D(\(�(�(�(F)p)�)*V*�*-++�+L,�,�,�,6-l-�-�-:.T.�.�./K/m/�/�/0>0g0�0�01D1h1�12J2�2�2�2(3T3v3�3�394]4�4�4�4595d5�5�5�5�5$6e6�6�6+7F7g7�7�7O8j8�8�89R9�9�9�9:A:�:�:�:L;h;<�<�<@=�=<>[>|>�>�>
?w?�?�?@i@�@�@A�A�A	B(BQBzB�B�BCACvC�C�C�C�C�C�CD@D|D�D�D*E�E�E�EF6FWFyF�F�F�F�F�FGIGaGxG�G�G�G�GHNH{H�H�H�H)IcI�I�I$J@JbJ�J�J�JK�K�K5L�L�L%M<MSM�M�M�M�M
NNN~N�N�NOAOwO�O�O�OPPHPgP�P�P�PQAQnQ�Q�QRRHRnR�R�RSJSiS�S�STMT�T�T4UiU�U�U�UVYV�V�V�V#W�W�W�W�XzY
Z�Z�Z�ZG[�[�[�[O\�\�\/]�]�]<^z^�^_D_a_�_�_�_u`�`ka�a�aMb�b�bcjc�c�cUd�d�dqe�e�efef�f�f�f(gRg�g�g�g�ghfh�h�hi_i�ijaj�j�jkTk�k�k>lol�l�lBmnm�m�m!n[n�n�noVo�o�op�p�p�p1qWq�q�q"r�r�rs*sSs�s�s�s)t�t�tuRuqu�u�u�u�uvFv�v�v�v2wlw�wxIxax�x�x�x�x#y>y^y�y�yzHzdz�z�z{V{{{�{z|�|&}x}�}�}~~G~`~�~5t����V���ۀ
�?�ہ�\���ׂ�D���E�y�����:�V�j�����߅�U����8�h���Ƈ#�L�{���݈&�Q�����ˉ�!�_�͊�a���ы�7�j�׌�������7�m�����ڍ�.�Y�z������}�Ώ��/�Y�v����3�z���>����>��c��l����5�����a����T���ɚ�/�f����<������.�O���ѝC�|�����B���ԟ�X�������ܢ�Z���ã٣��Ȥ��}�P�%�ިC�������
�4�p�Ӭ�N����,�d���ͮ�����J������>�ر�D�u���в�c����۴޴�/�v��������i���'�s����e�����ԺM�ͻ8���޼G����>�t�W����������(�]���_������S���������%������b�w����������H�[��������q���@�����<�p����t���=����"�<��]�����T�����Y��������D�f�����8�h�����������[����'�����!������s����l���'���&�D�����/�����T�X���I�^���d������u���������[�~��������������f�Y��R�������_���
�@�h����G�t������[�����'�X�~������(�M�v��������t���n������?�`��������
�8������Q�v��
�����O���*�g����m�A��'�u���-|���]��$f�C��5r���N�[����	7	V	�	�	
#
�
�
(����	
�
�
N{�
Z��^��(��F���?��
.R���#W��k�/X��8\w�I��S�:�^��}���
 / P m 5!y!�!"s"�"�"�"#P#z#�#�#�#�#$7$[$$L%�%�%i&�&S'�'(`(�(X)*Q*�*�*\+}+�+�+,3,^,�,�,�,-D-�-�-.Q.�.�.~/0/0X0x0�0�0�0O1�1�1�12F2�2�2"3l3�3�3e4�45Z5�5	646h6�6�67>7k7�7�7�7�7�7 8a8�8�8H9�9�9":Q:�:�:;�;�;C<�<=w=9>�>�> ?W?�?�?+@c@�@�@\A�A.BZBxB�B C~C�C�CZD�DEAE�E�E�EF�F�F#GIG}G�G�G9H{H�H�H$IpI�I�I(J_J�J�JKiK�K	L�L�L)M\M�M�MNkN�NOcO�OP_P�P�Q?R�RAS+T_T�T�T�T�TUXUyU�U�U�U�UVHV�V�V�VW[W�W�WXHX�X�XY�YZ7ZdZ�Z[M[�[*\�\]:]l]�]�]^j^�^�^_3_v_�_`:`h`�`]a�a�a�a@b�b�b�b�bHc�c�cd&d�d�de[ef�fgVg�g�g�hZi�i�i.j�j�jqk�k"l�lMm�m�mnwn�n�n3o�o9p�p�q�r�r<tpt�tuDu�u�uev�v�vw:w�w�wxex�xiy�yzOz�z�z"{W{�{|�|b}�}~w~��@�e����1�l���݁�b�؂-����F�������Z���/�y�q�5�M�y�Ƌ�Q�����.�s���ߍ�@��H���"������ё�@�T����e�Փ�:�z�Ŕ�h�Ǖ	�N���˖�%�J�����������	�V���S����+�f�����k����*�Z�����О�W����)�r����'�k���ӡ&�z���)����@���ۤ
�������<�����m���ԧ����e�ǩ��M����1�p���ϫ,���/�����®�!�V������h�°9���±t��=���׳=����S�a���ߵ	�s���_����?���i��n��K���¼�ǽ-���0��m��+����A�u�����Q�������H�j�$�
��������L�m�����;���8����L�������R������p���p���{�����Q������@�t����:�k��������e�����D���D���S���j��J��P���������Z������Y���X�����V�����q���%���O����V�n������F�w�������C�s�����	�O�����K���Q��j���:��!���t�[��n��!�����i���{�
�V�����3����Em�1���I���A�4T��^�	\	�	
7
�
�
4n&���?
�
���<K���#Lv��:�����0���-Kh��9e�����)Ju���3E{���Ha��2��"Lu��)/���"P���g� B � f!-"T"x"�">#�#�#$�$�$�%�%�%&<&V&�&�&�&o'�'`(�(H)�)*K*�*�*�*+P+�+�+#,@,�,�,A-y-�-�-�-�-.+.a.�./�/�/�/�/�/�/
0+0�0�0�0�0�01I1�1�12Z2|2�2�2'3`33�3�334f4�4�4H5a5�6�6�7�78�8x9�9:@:f:�:�:�:;c;�;�;�<�<=�=�=�=$>N>>�>�>,?a?�?�@EAHA�A�AEB|B�B�B�BBC�C�CDcD�D�DEOE�E�E�E�EFlF�F�F�FgG}G�G�GHYH�H�H�H�H�H�HI�J�J�J;KL�L:M`M�M�M�MNLNnN�N�N�NOFOxO�O�O�O�OP<P|P�P�PRQrQ�Q�Q�QR0R\R�R�R�RS;SfS�S�S�ST7TkT�T�T�TUOU�U�U�UWV�V�V�VW\WyW�W�W�W
X/X^X�X�X�XTY�Y�Y?Z�Z�Z[a[�[O\�\]�]^�^�^[_=a�a�atb�bc5cxc�c�c<d�d�d�d]e�e�e6f�f�g�g�g,h�hiRiii�i�i�i
j.jWj�j�j�jCk�k�klUl�l�lm�m�mMn�no0obo�o�o�o/pup�p
qTq�qr�r�r�rBs�s�stDtut�t�ucv
w�w'x\x�x�x�x�x=yHyKy�y�yz{z�z {�{|n|�|�|
}6~[~�~�~!R^�w�#�\���܁�J�Ă��@�v���������L����7�q��K�k���x��$�I�`���߉8��������=������R�p���Ҍ����ō�1�z�͎�M���ԏU��������6�^����������Z�������6�y����8�_���ҕ��*�[�}����4�����֗��>������Ù��6�q�ћ�c����G��������Y�������@�_���%������6���6�a�����ۧ>�j�Ψ�4�^�y�'�j�������ի7�X�������z��Ӯ�%�ޯ|�ɰ0�y�	���޲���`�����/�_���ʵ�t�=���η�7�a�Ƹ$�8�L�z���ȹ��+�X�������b�ɻ�� �a����B����@�m�����W�����J�x��I����<��������I�{����N�����~���.�h�w�z�}�����
�%�Z�������S���X����	�<�[�������/�i������9���`���� �H��������@�r������>�i���������!�Y��������Z���)�o�����$�Y�}��� �O��������L�k�������l��������/�H�u������,�T���������!�A�n�������5�Z��������J������?��������?�`���'�=�S�����3�����������
�@�a�y������r�����B�}���"�Q������8����z�:�x����7�����������~���!�������_�������&�]������X�����'�j�����(�������N�p�����*����������������E�]�����������<����M�~�����W�����������C�����[�����9^��?�_���3ZR�:�2f��-r�*	~	�	�	
P
�
�
Hb6t�]
x
�
�
.Vz��1\o��y��`���Bj���)�N���H{�2��O��6f��1��!Jn��
3[}�Z��f��� l � � � ,!V!|!�!"G"j"�"�"�"-#�#H$�$c%�%�%�%&v&�&o'�'
(h(�(�()D)�)�);*�*D+�+q,�,�,-K-O-S-W-[-_-c-�-�-�-�-..u.�.�.�.�.:/T/g/�/�/v0�0(1z1�1�1�1&2~2�2�23X3�3�354�4�4�4D5�5@67�7�789889n9�9�9�9:%:G:�:�:�:.;M;n;�;�;�;�;#<F<U<h<{<�<�<�<7=Z=|=�=�=�=#>V>}>�>�>�>#?d?�?�?�?�?@0@[@�@A,A\A�A�A.BTB�B�B�BC^C|C�C�CDQD�D�D�D�DE~E�E�E%F:FfF�F�FG;G|G�G�G�GHSH�H�H�H�H�H�H�I�I�J)KJKsK�K�K'LVL�L�L�L9M<MlM�M�M+NVN�N�N�N�NO3OLOnO�O�O�OPSPP�P�PQQAQ`QhQrQ�Q�Q
R'R�R�R�R|S�S�ST3T6T9T<TcT�TUBUlU�U�UW�W�W�XRYdZ�Z�Z�ZB[Z[�[�[�[
\%\c\�\�\�\%]R]]�]�]8^Y^w^�^�^_)_�_�_`0`O`q`�`�`�`�`a4afa�a�ab=b}b�b�bcDc�c�c�cd&d>d�d�d�d�dBe�e�e�e	f6fHfcfvf�f�f�f
g.gVg�g�g�g/h\h�h�h�hi@i�i�i�iZjXk�k�klGll�l�lmUm�m�m"n3n�n�n�no4oeo�o.p.q}q�q�qr>rr�r�r�rs5sNs�s�s�s�s�sFt~t�t�t�t�t.uEu�u�u3vlv�vOw�wxLx4y�y�yzz{`{�{'|^|�|�|�};~�~�~$H���&�X�����q���� �W���߂�8�����9��������E����@�t�Շ;����z��]�ҊI�{�&�r������ɍ����7�]������+�q����%�b���Ǒ���В�0�@���K�Ֆ��=�Z�×�(������5�q����%�~�����v��j����J���_���7�ݠs���������-�b���B�¥Q�Ҧ2����B�h���Ũ �y�ީ8���Ӫ?���իB����b�ԭ��2�N�k�������2�u��a����4�a����^�O��F����3���2���V��J������I�����j�ܻG�~�����f�νn�����7����.�{���T��.�}��W�����M�����,����V��i����H������L���f��M�����a�������q���4�l������F�p������T������������/������J�w���c�����@���!�3�h�����[���j���������r����i�����O�����5������o�������E��������K������y���7�Y���������8�|�����r�u���(�����6�_������E�\�p����������-�L�s������M�q�����
�G�\������7�t����;�������-�m������N��������>�s������#�Q������O�p������<�Y��-�g��i�����(�L������=�^��������������������������
�
�������"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|������������	!$'*-0369<filorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������������������������������Bj��;rux{~���Y��b��_�Z	z	�	�	2
J
���
R
�
�
�
�
�
�
�
�
 #&),/258;>ADGJMPSVY\_behkn #&),/258]`cfilorux{~�����������BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILO�����������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{���{~�����������������������+]�I��Q�;j��

"9g��8�7d��D�1aH{ � � � !`!�!�!�!�!"""""""%"�"$#|#�#$4$�$�$	%-%F%�%�%@&X&�&�&�'(T(�(()Q)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)********** *#*&*)*,*/*2*5*8*;*>*A*D*G*J*M*P*S*V*Y*\*_*b*e*h*k*n*q*t*w*z*}*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*B+E+H+K+N+Q+T+W+Z+]+`+c+f+i+l+o+r+u+x+{+~+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,,,,,,,, ,#,&,),,,/,2,5,8,;,>,A,D,G,J,M,P,S,V,Y,\,_,b,e,h,k,n,q,t,w,z,},�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---
-
-------"-%-(-+-.-1-4-7-:-=-@-C-F-I-L-O-R-U-X-[-^-a-d-g-j-m-p-s-v-y-|--�-�-�-�-�-�-�-�-.�.�.
/]/�/�/0X0�0�0�001O1h1y1�1�12]2�2�2�2�2B3^3~3�3�3�34`4�4�4%5C5^5~5�5�526�6�6�67�7�7�7Z8�8969f9�9�9�9:J:�:�:&;C;d;<=<�<�<�<�<�<�<�<�<�<�<�<N=l=o=>>>>i>�>�>?/?�?VA�A�A=B�BKCSD�D�DEFEIELE�E�F-GcH�H�H�H
I:IUIXI[I^IaIdIgIjImIpI�I�I�IJJ<J?JhJkJ�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�JKKK
K
KKKKKKK"K%K(K+K�K�K�K�K�K�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L�LHMKMN�N�N�N�N�N�NO=O]O�O�O�OP0PlP�PBQEQHQKQNQQQTQWQZQ]Q`Q�Q�Q�Q�R�R�RS�SPT3UqU�VW�W}X�X�X
Y-Z�Z*[O[�[�[s\�\
]].]U]�]�]�]�],^x^�^�^�^_�_ `a`~`�`�`a0a_a�a�a�aMb�b2c4c�c�c&d�d�dHeXe[e�e�e�e�ef^ftf�f`g�gh=hSh�h�h�hiRi�i�i4jcj�j k|k�kl#lAl[l^l�l�l"m@mgm�m�m�m�mnn"n%n(n+n.n1n4n�n�nLo�o�o%p�p+q�q�q�q rMr�r�rZs�st�t�t�u�u�u8v�v�v)w�w#xdx�x�x*y[y�y�yz+z�z�z�{|�|K}�}?~�~�~av��2�e�����Ԁ׀N�����ρ��@���7�:�Y��������"�Y����Z����1�K�������J����X���ш
�����D����t�����a�͌L���"����t�Տ"�u����d���ёB�z���>�w�Ó
�M��Ô���������T���ޖ�@�d�s�ח�x�����Ř�U�����<�q�����Ě��R����{���������.���4���*����:��� ����=�W�|������)�R�o���*�r���˦�!���ʧ�D���̨<���r���ƪ�"�b����E������`�����S�n�ޮ?����ڰ�7�c����P�����ڲ���:����8���ٴ4�`���ٵ�������ط�(�S���i�l�o�r���ع7����$������}��>����r����L���������)�H�>�r�����l����B�E���2�������������X�����������h���B�����'�����0�}�����G���9�����������:�U���������e�����@�k�n�q���������������������������������������6�Z���������������B�z����������<�e������o��������;�����������_����g������{���4�����/����� �u����H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~�����������������������������������������<�������8�W�x���B����_�����U���v����%�j���	�%�W�x���?�����o�#�m���x�I�����k���������O��/�����58g}�r��{�!p����"��*P	k	�	|
"h2��
G�R!}�z�vl����<��2�,���~G�z�� W � � � 7!e!F"5#T$,%C&�&N'�'�(�(A)�)�)�)�)*O*�*�*7+_+~+�+�+�+�,�-
.4._.�.�./?/�/�/J0�01m1�1�3�3�5�6757�7'8_8�9	:e:�:�:F;�;'<Y<C=�=7>_>�>�>�>0?e?i?m?q?$@`@�@�@�@�A@B�BC]C�C�CDOD�D6E�E�EFF�FGYG�G�HaIJ�J�KLHL�L�LMOM�M�M�M�M*NMN�N�N�O�O.P�P�P�PQ7QqQ�Q�QRPRS�S�T_W�Y�Y!ZTZ�Z�ZH[�[�[.\^\�\i]^�^K_�_�`�`2a7a�a�a�a�b�b�bccc�cd:d[d�d�d�de5eLeqe�e�e�e�e�e?f�fAg�g�gbh�i�j
k�lmmYmim�m�m�mJn�n1o�o
pep�pqUq�qrKr�r�r4sfs%tRt�uv�v�v�v w#w�wbx�xCy�yRz�z�z�{|\|}�}�}~z~�~�~_����;������"���ҁ>����h�ʃ*�x�ل���$�7�O�s�������օ����2���Ї�;���/�d���ɉV�݊{���M�t���Ό}��r���ώ7�p����k�ۑC�F�����K���?��ŕa�ɖhashchkisamchkNEANONemohu vytvořit soubor '%-.200s' (chybový kód: %d - %s)Nemohu vytvořit tabulku '%-.200s' (chybový kód: %d - %s)Nemohu vytvořit databázi '%-.192s' (chybový kód: %d - %s)Nemohu vytvořit databázi '%-.192s'; databáze již existujeNemohu zrušit databázi '%-.192s', databáze neexistujeChyba při rušení databáze (nemohu vymazat '%-.192s', chyba %d - %s)Chyba při rušení databáze (nemohu vymazat adresář '%-.192s', chyba %d - %s)Chyba při výmazu '%-.192s' (chybový kód: %d - %s)Nemohu číst záznam v systémové tabulceNemohu získat stav '%-.200s' (chybový kód: %d - %s)Chyba při zjišťování pracovní adresář (chybový kód: %d - %s)Nemohu uzamknout soubor (chybový kód: %d - %s)Nemohu otevřít soubor '%-.200s' (chybový kód: %d - %s)Nemohu najít soubor '%-.200s' (chybový kód: %d - %s)Nemohu číst adresář '%-.192s' (chybový kód: %d - %s)Nemohu změnit adresář na '%-.192s' (chybový kód: %d - %s)Záznam byl změněn od posledního čtení v tabulce '%-.192s'Disk je plný (%s), čekám na uvolnění nějakého místa ... (chybový kód: %d - %s)Nemohu zapsat, zdvojený klíč v tabulce '%-.192s'Chyba při zavírání '%-.192s' (chybový kód: %d - %s)Chyba při čtení souboru '%-.200s' (chybový kód: %d - %s)Chyba při přejmenování '%-.210s' na '%-.210s' (chybový kód: %d - %s)Chyba při zápisu do souboru '%-.200s' (chybový kód: %d - %s)'%-.192s' je zamčen proti změnámTřídění přerušenoPohled '%-.192s' pro '%-.192s' neexistujeObsluha tabulky vrátila chybu %d - '%-.192s'Obsluha tabulky '%-.192s' nemá tento parametrNemohu najít záznam v '%-.192s'Nesprávná informace v souboru '%-.200s'Nesprávný klíč pro tabulku '%-.200s'; pokuste se ho opravitStarý klíčový soubor pro '%-.192s'; opravte ho.'%-.192s' je jen pro čteníMálo paměti. Přestartujte daemona a zkuste znovu (je potřeba %d bytů)Málo paměti pro třídění. Zvyšte velikost třídícího bufferuNeočekávaný konec souboru při čtení '%-.192s' (chybový kód: %d - %s)Příliš mnoho spojeníMálo prostoru/paměti pro threadNemohu zjistit jméno stroje pro Vaši adresuChyba při ustavování spojeníPřístup pro uživatele '%-.48s'@'%-.64s' k databázi '%-.192s' není povolenPřístup pro uživatele '%-.48s'@'%-.64s' (s heslem %s)Nebyla vybrána žádná databázeNeznámý příkazSloupec '%-.192s' nemůže být nullNeznámá databáze '%-.192s'Tabulka '%-.192s' již existujeNeznámá tabulka '%-.129s'Sloupec '%-.192s' v %-.192s není zcela jasnýProbíhá ukončování práce serveruNeznámý sloupec '%-.192s' v %-.192sPoužité '%-.192s' nebylo v group byNemohu použít group na '%-.192s'Příkaz obsahuje zároveň funkci sum a sloupcePočet sloupců neodpovídá zadané hodnotěJméno identifikátoru '%-.100s' je příliš dlouhéZdvojené jméno sloupce '%-.192s'Zdvojené jméno klíče '%-.192s'Zdvojený klíč '%-.192s' (číslo klíče %d)Chybná specifikace sloupce '%-.192s'%s blízko '%-.80s' na řádku %dVýsledek dotazu je prázdnýNejednoznačná tabulka/alias: '%-.192s'Chybná defaultní hodnota pro '%-.192s'Definováno více primárních klíčůZadáno příliš mnoho klíčů, je povoleno nejvíce %d klíčůZadáno příliš mnoho část klíčů, je povoleno nejvíce %d částíZadaný klíč byl příliš dlouhý, největší délka klíče je %dKlíčový sloupec '%-.192s' v tabulce neexistujeBlob sloupec '%-.192s' nemůže být použit jako klíčPříliš velká délka sloupce '%-.192s' (nejvíce %lu). Použijte BLOBMůžete mít pouze jedno AUTO pole a to musí být definováno jako klíč%s: připraven na spojení
Version: '%s'  socket: '%s'  port: %d%s: normální ukončení
%s: přijat signal %d, končím
%s: ukončení práce hotovo
%s: násilné uzavření threadu %ld uživatele '%-.48s'
Nemohu vytvořit IP socketTabulka '%-.192s' nemá index odpovídající CREATE INDEX. Vytvořte tabulku znovuArgument separátoru položek nebyl očekáván. Přečtěte si manuálNení možné použít pevný rowlength s BLOBem. Použijte 'fields terminated by'.Soubor '%-.128s' musí být v adresáři databáze nebo čitelný pro všechnySoubor '%-.200s' již existujeZáznamů: %ld  Vymazáno: %ld  Přeskočeno: %ld  Varování: %ldZáznamů: %ld  Zdvojených: %ldChybná podčást klíče -- není to řetězec nebo je delší než délka části klíčeNení možné vymazat všechny položky s ALTER TABLE. Použijte DROP TABLENemohu zrušit '%-.192s' (provést DROP). Zkontrolujte, zda neexistují záznamy/klíčeZáznamů: %ld  Zdvojených: %ld  Varování: %ldYou can't specify target table '%-.192s' for update in FROM clauseNeznámá identifikace threadu: %luNejste vlastníkem threadu %luNejsou použity žádné tabulkyPříliš mnoho řetězců pro sloupec %-.192s a SETNemohu vytvořit jednoznačné jméno logovacího souboru %-.200s.(1-999)
Tabulka '%-.192s' byla zamčena s READ a nemůže být změněnaTabulka '%-.192s' nebyla zamčena s LOCK TABLESBlob položka '%-.192s' nemůže mít defaultní hodnotuNepřípustné jméno databáze '%-.100s'Nepřípustné jméno tabulky '%-.100s'Zadaný SELECT by procházel příliš mnoho záznamů a trval velmi dlouho. Zkontrolujte tvar WHERE a je-li SELECT v pořádku, použijte SET SQL_BIG_SELECTS=1Neznámá chybaNeznámá procedura %-.192sChybný počet parametrů procedury %-.192sChybné parametry procedury %-.192sNeznámá tabulka '%-.192s' v %-.32sPoložka '%-.192s' je zadána dvakrátNesprávné použití funkce groupTabulka '%-.192s' používá rozšíření, které v této verzi MySQL neníTabulka musí mít alespoň jeden sloupecTabulka '%-.192s' je plnáNeznámá znaková sada: '%-.64s'Příliš mnoho tabulek, MySQL jich může mít v joinu jen %dPříliš mnoho položekŘádek je příliš velký. Maximální velikost řádku, nepočítaje položky blob, je %ld. Musíte změnit některé položky na blobPřetečení zásobníku threadu: použito %ld z %ld. Použijte 'mysqld --thread_stack=#' k zadání většího zásobníkuV OUTER JOIN byl nalezen křížový odkaz. Prověřte ON podmínkyTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNemohu načíst funkci '%-.192s'Nemohu inicializovat funkci '%-.192s'; %-.192sPro sdílenou knihovnu nejsou povoleny cestyFunkce '%-.192s' již existujeNemohu otevřít sdílenou knihovnu '%-.192s' (errno: %d %-.128s)Nemohu najít funkci '%-.128s' v knihovněFunkce '%-.192s' není definovánaStroj '%-.255s' je zablokován kvůli mnoha chybám při připojování. Odblokujete použitím 'mysqladmin flush-hosts'Stroj '%-.255s' nemá povoleno se k tomuto MySQL serveru připojitPoužíváte MySQL jako anonymní uživatel a anonymní uživatelé nemají povoleno měnit heslaNa změnu hesel ostatním musíte mít právo provést update tabulek v databázi mysqlV tabulce user není žádný odpovídající řádekNalezených řádků: %ld  Změněno: %ld  Varování: %ldNemohu vytvořit nový thread (errno %d). Pokud je ještě nějaká volná paměť, podívejte se do manuálu na část o chybách specifických pro jednotlivé operační systémyPočet sloupců neodpovídá počtu hodnot na řádku %ldNemohu znovuotevřít tabulku: '%-.192sNeplatné užití hodnoty NULLRegulární výraz vrátil chybu '%-.64s'Pokud není žádná GROUP BY klauzule, není dovoleno současné použití GROUP položek (MIN(),MAX(),COUNT()...) s ne GROUP položkamiNeexistuje odpovídající grant pro uživatele '%-.48s' na stroji '%-.255s'%-.128s příkaz nepřístupný pro uživatele: '%-.48s'@'%-.64s' pro tabulku '%-.64s'%-.16s příkaz nepřístupný pro uživatele: '%-.48s'@'%-.64s' pro sloupec '%-.192s' v tabulce '%-.192s'Neplatný příkaz GRANT/REVOKE. Prosím, přečtěte si v manuálu, jaká privilegia je možné použít.Argument příkazu GRANT uživatel nebo stroj je příliš dlouhýTabulka '%-.192s.%-.192s' neexistujeNeexistuje odpovídající grant pro uživatele '%-.48s' na stroji '%-.255s' pro tabulku '%-.192s'Použitý příkaz není v této verzi MySQL povolenVaše syntaxe je nějaká divnáDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useZrušeno spojení %ld do databáze: '%-.192s' uživatel: '%-.48s' (%-.64s)Zjištěn příchozí packet delší než 'max_allowed_packet'Zjištěna chyba při čtení z roury spojeníZjištěna chyba fcntl()Příchozí packety v chybném pořadíNemohu rozkomprimovat komunikační packetZjištěna chyba při čtení komunikačního packetuZjištěn timeout při čtení komunikačního packetuZjištěna chyba při zápisu komunikačního packetuZjištěn timeout při zápisu komunikačního packetuVýsledný řetězec je delší než 'max_allowed_packet'Typ použité tabulky nepodporuje BLOB/TEXT sloupceTyp použité tabulky nepodporuje AUTO_INCREMENT sloupceINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESNesprávné jméno sloupce '%-.100s'Handler použité tabulky neumí indexovat sloupce '%-.192s'Všechny tabulky v MERGE tabulce nejsou definovány stejněKvůli unique constraintu nemozu zapsat do tabulky '%-.192s'BLOB sloupec '%-.192s' je použit ve specifikaci klíče bez délkyVšechny části primárního klíče musejí být NOT NULL; pokud potřebujete NULL, použijte UNIQUEVýsledek obsahuje více než jeden řádekTento typ tabulky vyžaduje primární klíčTato verze MySQL není zkompilována s podporou RAIDUpdate tabulky bez WHERE s klíčem není v módu bezpečných update dovoleno. %sKlíč '%-.192s' v tabulce '%-.192s' neexistujeNemohu otevřít tabulkuHandler tabulky nepodporuje %sProvedení tohoto příkazu není v transakci dovolenoChyba %d - '%-.192s' při COMMITChyba %d - '%-.192s' při ROLLBACKChyba %d při FLUSH_LOGSChyba %d při CHECKPOINTSpojení %u do databáze: '%-.192s' uživatel: '%-.48s' stroj: '%-.255s' (%-.64s) bylo přerušenoHandler tabulky nepodporuje binární dumpBinlog closed, cannot RESET SOURCEPřebudování indexu dumpnuté tabulky '%-.192s' nebylo úspěšnéChyba masteru: '%-.64s'Síťová chyba při čtení z masteruSíťová chyba při zápisu na masterŽádný sloupec nemá vytvořen fulltextový indexNemohu provést zadaný příkaz, protože existují aktivní zamčené tabulky nebo aktivní transakceNeznámá systémová proměnná '%-.64s'Tabulka '%-.192s' je označena jako porušená a měla by být opravenaTabulka '%-.192s' je označena jako porušená a poslední (automatická?) oprava se nezdařilaSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionZvojený klíč '%-.64s' (číslo klíče '%-.385s')Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTPřístup pro uživatele '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartion '%-.64s' neexistujeFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionZdvojený klíč (číslo klíče '%-.192s')Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\K��r�r�danish/errmsg.sysnu�[�����^��L���6��9p���-a��V���7[m��'D��� y��9W����%	?	b	y	�	�	�	
:
{
�
�
�
@o����N���;
�
�
.Re��K��J`�]����T���/Pn6f����Kq����U����
2n��/f�U�1{���c�o��'���*J��   N � � .!�!�!"I"�"�"#=#f#�#�#c$�$�$�$�%�%�%&3&r&�&�&!'|'�'�'(-(S(z(�(/)N)�)�)7*�*+m+�+A,{,�,�,-S-�-�-).C.x.�./:/\/�/�/0-0V0s0�0�031W1�1�192�2�2�23C3e3�3�3(4L44�4�4�4(5S5r5�5�5�56T6�6�6757V7�7�7>8Y8z8�8�8A9o9�9�9:0:s:�:�:;;W;<�<�</=�=+>J>k>�>�>�>f?�?�?@X@�@�@A�A�A�ABBBkB�B�BC2CgC|C�C�C�C�C�C
D1DmD�D�DE�E�E�EF'FHFjF�F�F�F�F�FG:GRGiG�G�G�G�G�G?HlH�H�H�HITI�I�IJ1JSJ�J�J�JK�K�K&L�L�LM-MDMsM�M�M�M�M?NoN�N�NO2OhO�O�O�O�OP9PXP�P�P�PQ2Q_Q�Q�Q�QR9R_RyR�RS;SZSqS�ST>T�T�T%UZU�U�U�UVJVzV�V�VWwW�W�W�XkY�YxZ�Z�Z8[q[�[�[@\�\�\ ]]�]-^k^�^_5_R_�_�_�_f`�`\a�a�a>b�b�b
c[c�c�cFd�d�dbe�e�efVf�f�f�fgCg{g�g�g�g
hWh|h�hiPi�i�iRj�j�jkEk�k�k/l`l�l�l3m_m�m�mnLn~n�noGo�o�opqp�p�p"qHq}q�qr}r�r�rsDs|s�s�st�t�tuCubu�u�u�u�uv7v�v�v�v#w]w�w�w:xRxrx�x�x�xy/yOy�y�yz9zUzsz�z{G{l{�{k|�|}i}�}�}�}~8~Q~�~
&e����G���̀��0�́�M���Ȃ�+���,�`������!�=�Q�n���ƅ��<�k�����O�����
�3�b���Ĉ
�8�i�����Չ�F���ۊH�������Q���ǌ͌׌�����T�t�������@�a���ǎ��d���ޏ�@�]���̐�a���%�̒w�%�ΔJ�֕S�ؖ~��z��H�͙ޙ;�u���ښ�M�o�Λ#�l���ڜ�6�m���*�c���Ǟ��'�m����=�נy���h�����?�t�����ڣ����b�5�
�è(���������U����3���׭�I�����Ԯ����/�l���հ#�����)�Z�}�����O���
�Ǵʴ��b�����l�η�U����_����Q�|�����9���$���ʼ3���н*�`�C�������m����I���K������?����������t�����N�c����������4�G��������]���,�k�����(�\����`���)������(�
�I�����@�t���E�u�������0�R�����$�T�����������A�����
������i�����Y�����R�o�
����*������k���:�>���/�D���J�|�����[�����e�����A�d������l�������L�?���8�m�����E�����&�N����-�Z�������A�����
�>�d��������3�\���������Z���T������%�F�u��w����i����7�\����s�����5����M����S�'���
�[���b�j�C��
L��)u��X��r�4�A~���		<	�	�	�		
�
�
{�����q
�
�
4a��@��D��k��,m��%���8o���	=m�Q���>v��B]��/�}��9� �D��cu��� 6 S !_!�!�!Y"�"�"�"�"6#`#�#�#�#�#�#$A$e$2%�%�%O&�&9'�'�'F(�(>)�)7*�*�*B+c+�+�+�+,D,u,�,�,�,*-�-�-�-7.�.�.d/�/0>0^0�0�0�051i1�1�1�1,2{2�23R3�3�3K4�4�4@5�5�56N6�6�6�6$7Q7�7�7�7�7�78G8�8�8.9�9�9:7:�:�:;g;�;)<g<�<]=>�>�>?=?{?�?@I@@�@BA�AB@B^B�BCdC�C�C@D�D�D'EgE�E�E�E{F�F	G/GcG�G�GHaH�H�H
IVI�I�IJEJjJ�JKOK�K�K�L�LMBMvM�M�MQN�N�NIO�O�OEP�PnQ%R�R'STETtT�T�T�T�T>U_UzU�U�U�U�U.VgV�V�V�VAWiW�W�W.X{X�XY�Y�YZJZ�Z�Z3[�[\�\�\ ]R]�]�]�]P^~^�^�^_\_�_�_ `N`�`Caxa�a�a&bpb�b�b�b.c~c�c�cd�d�deAe�e�f�f<g�g�g�h@i�i�ijfj�jWk�kl�l3mpm�mn]n�n�noyop�p�qor�r"tVt�t�t*u�u�uKv�v�v�v www�wxKx�xOy�y�y5zzz�z{={�{�{�|H}�}�}]~�~p�&�K������R���Á��H����q�̓,�m���Ȅ��@����_�W��3�_����7���܌�Y���ō��&�����.����v�������&�:�z���K����� �`����N����4�����Ӗ�0�t��������v��<���9���ț�L���ʜ�Q���Ν�@�i�l�����=�����X�n��
�Q�x����`����f�ӣ&�����������"�{�צ�S�������s���K���ީ3���Ҫ�V�~�������߭n���ծ�<�o�s��N��������Z�Ȳ#�l���#�z�Ӵ9�G���ŵ�Y�߶E���ȷ%���O���T�̻1�g���ּ������տS�������'�[�����7���������.�P�
�����}�����2�S�l���!��������2�������8�������V���V���a�����7�������&�Z����� �Q���s�����K�����*��*���9���P���0���6�|���w����@�q����?���>�����<�g���W������5�����<�T�������,�]���x���)�Y���x�����5�����1���7���P��� �����Z�A���T����f����O���a��<����o���+S�����/����'��:��k�D��B	�	�	
q
�
Tm��%
�
���"1e���	2\�� m��e��s��1N���Kv��t�0[���+a����.G��f�2[��g��6h��M��( � L!":"^"�"$#m#�#�#�$�$q%�%�%�%"&<&j&�&�&U'�'F(�(.)q)�)1*g*�*�*+6+�+�+	,&,�,�,'-_-�-�-�-�-�-.G.�.�.q/|/�/�/�/�/�/0r0�0�0�0�0�0/1{1�1�1@2b2�2�2
3F3e3z3�34L4�4�4.5G5�6�6z7�7�7�8^9�9:&:L:r:�:�:�:I;q;�;�<�<�<f=�=�=
>4>e>�>�>?G?�?�@+A.AzA�A+BbB�B�B�B(C�C�CDID�D�DE5EkE�E�E�E�ERF�F�F�FMGcG�G�G�G?HfH�H�H�H�H�HeI�J�J�J!K�K�L MFMnM�M�M�M2NTN�N�N�N�N,O^O�O�O�O�O�O"PbP�P�P8QXQ�Q�Q�Q�QRBRiR�R�R�R!SLSuS�S�S�STQT�T�T�T�T5UgU�U�U=VpV�V�V�VBW_W�W�W�W�WXDXiX�X�X:YxY�Y%Z�Z�Z�ZG[�[5\�\�\{]�]o^�^A_#afa�aZb�b�bc^c�c�c"djd�d�dCe�e�ef�fog�g�ghmh�h8iOihi�i�i�ij=j�j�j�j)ktk�kl;lfl�lmxm�m3n�n�noHoqo�o�op[p�p�p:q�q�qir�r�r(sps�s�s*t[t�tzuIv�v�w
xBxvx�x�x�x#y.y1yuy�y�yaz�z{�{|T|�|�|�|~A~~�~8Dk]�	�B����0����&�\����e���Ʉ��2���˅�W�����1�Q�g�^�ш
�/�F���ŉ�r���݊��#���ʋ݋8�V�������e���ڍ�`�����3�f���;��q���ܑ�D�n��������@�q���Γ��_������E�r�����A�c���Ԗ������ח�$�p������Ǚ��W����I����-�g����e��?�����Ԡ��&�E�����n�������G�������$�P�����D�_�
�P���̪�������>�i���Ӭ�`�ϭ����įb����_��k�Ĳܲ��F�j�n��E�~����Z�#�l������G���
��2�`�������>�n���Ⱥ�H���޻�G���ϼ(����&�S���Ǿ�=�w�ֿ��0�^��/����"�g������/�a�����4�����d����N�]�`�c��������@�n�����9���>�e�����"�A��������O��������m�F������.�f�������&�X������$�O�p��������?�z�������@����U�����
�?�c����5�j������2�Q�x�����R�x��������.�[��������:�r��������'�T��������@�s�������0�s�����%�p������%�F���
�#�9������g���e�z�������&�G�_�������X�����(�c����7�|����������`� �^������w���������d����e�������E�z������C������>�x���
�P������������4�V�x����m��������������+�C�m����������"�f��3�d�������=�������u�|�)�m����A�����Dl�%�E{���@8o pL��X�	d	�	�	�	6
�
�
�
.HeZ�C
^
�
�
<`���BU|�_��F{���(P��z�e��4l���.a��y��5n��Lt�i�0T{��Ac��@r��Lv���R � � � !<!b!�!�!-"P"�"�"�"#�#.$�$I%�%�%�%&\&�&U'�'�'N(�(�(�(*)�)�)!*�**+�+W,�,�,�,1-5-9-=-A-E-I-j-�-�-�-.[.�.�.�.�. /:/M/m/�/\0�01`1�1�1�12d2�2�2�2>3�3�34q4�4�4*5�5&67�7�7�789T99�9�9::-:w:�:�:;3;T;v;�;�;�;	<,<;<N<a<o<�<�<=@=b=y=�=�=	><>c>t>�>�>	?J?f?�?�?�?�?@A@�@�@ABA�A�AB:B�B�B�B�BDCbC�C�C�C7DgD�D�D�D�DdEtE�EF FLFzF�F�F!GbG�G�G�GH9HjH�H�H�H�H�H~I�I�JK0KYK�K�K
L<LlL�L�LM"MRM�M�MN<NlN�N�N�N�NO2OTO�O�O�O�O9PeP�P�PQQ'QFQNQXQ�Q�Q�Q
R|RR�RbS�S�S�STTT"TIT{T�T(URU�U�U�V�W�WvX8YJZvZ�Z�Z([@[�[�[�[�[\I\{\�\�\]8]e]�]�]^?^]^t^�^�^_q_�_``5`W`n`q`�`�`�`aLa�a�a�a#bcb�b�b�b*cjc�c�c�cd$drd�d�d�d(eve�e�e�ef.fIf\f�f�f�f�fg<g�g�g�ghBhhh�h�h�h&i�i�i�i@j>k�k�kl-lel|l�lm;m�m�mnn�n�n�n�noKo|opqcqtq�q�q$rer�r�r�r�rs4srs�s�s�s�s,tdt�t�t�t�tu+u�u�uvRv�v5w�wx2xyty�y`z�zF{�{
|D|v|�|�}!~�~�~
.}���>���ˀ؀W���́�=�w�ł�����������m�܅+�}�׆&�Z���!�}��`�ɉC���/�a��X��������׍w����C�m���Ώ�W���Ȑ�H�o����f�����&���1���ޖ#�@���ԗ�k���ؘ�W���ϙ�d�����\�МP���ѝ0���E����àY���ݢe���٣�H���(���7����o��(�N������_�ĩ�t���%�����(����H����ɮ�4�Q�r���ȯ��[�ѰG���ձ�G����D�5�Ӵ,���ڵ����{�<��0�i���й/����P�»-�d����L���T�������п�a����:����c���=�����3�u����n���<���O�����.������2���L���3�l���G�������W����R�������,�V������:�������m�����������0�]���I�z���&�����N�����A���P����������X�����O�����5������������U�������+�e�������1�z����_����?���k������b�����X�[����l����E�y�����+�B�V�p����������2�Y�������3�W�������-�B��������Z�����!��������S������4�o�������$�Y������	�7�������5�V�t�����"�?���M��O�������2�f����#�D�e���p�������������������������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b����������������������

"LORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilo�������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~�����������������������������(P���!X[^adg���?���H�E�@	`	�	�	
0
s��
8
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
	!$'*-0369<?BEHKNQT���	CFILORUX[^adgjmpsvy|��(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/25��������������������������������������

"%(+.147:=@CFILORUX[^a���adgjmpsvy|��������������C�/��7��!Pp���Mw����Jw��*�G.a�� � � � F!�!�!�!�!�!�!�!""""�"
#b#�#�#$�$�$�$%,%i%�%&&>&i&�&�'�':(�()7)m)p)s)v)y)|))�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)***	********!*$*'***-*0*3*6*9*<*?*B*E*H*K*N*Q*T*W*Z*]*`*c*f*i*l*o*r*u*x*{*~*�*�*�*�*�*�*�*�*�*�*�*�*�*�*(+++.+1+4+7+:+=+@+C+F+I+L+O+R+U+X+[+^+a+d+g+j+m+p+s+v+y+|++�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,	,,,,,,,,!,$,',*,-,0,3,6,9,<,?,B,E,H,K,N,Q,T,W,Z,],`,c,f,i,l,o,r,u,x,{,~,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---------- -#-&-)-,-/-2-5-8-;->-A-D-G-J-M-P-S-V-Y-\-_-b-e-h-k-n-q-t-w-z-}-.l.�.�.C/�/�/0>0n0�0�0151N1_1�1�12C2�2�2�2�2(3D3d3�3�3�34F4�4�45)5D5d5�5�56x6�6�6�6f7�7�7@8�899L9o9�9�9�90:�:�:;);J;�;#<j<m<p<s<v<y<|<<�<�<�<4=R=U=�=�=$>O>p>�>�>?�?<A�A�A#ByB1C9D�D�DE,E/E2E�E�FGIHnH�H�H�H I;I>IAIDIGIJIMIPISIVI�I�I�I�I�I"J%JNJQJ{J~J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�JKKKKKK�K�K�K�K�K�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L�L.M1M�M�N�N�N�N�N�N�N#OCOyO�O�O�OPRP�P(Q+Q.Q1Q4Q7Q:Q=Q@QCQFQhQ�Q�Q�R�R�R�R�S6TUWUwV�VyWcX�X�X�XZ�Z[5[n[�[Y\�\�\]];]o]�]�]�]^^^�^�^�^�^�_`G`d`�`�`�`aEa|a�a�a3b�bccgc�cdjd�d.e>eAeme�e�e�e�eDfZf~fFg�g�g#h9hph�h�hi8i�i�ijIj�jkbk�k�k	l'lAlDl�l�lm&mMmkm�m�m�mnnnnnnnnn�n�n2ogo�op�pqwq�q�qr3rfr�r@s�s�s�t�tgu�u�uvrv�vw�w	xJx�x�xyAy�y�y�yz�z�z�{|�|1}�}%~�~�~G\x��K�o�������4�}�����ׁ�&�݂� �?�w�����Ӄ�?���τ@�e����1�l���݆0�{�؇>�x����k��*����Z���ȋ��G���2����p��Z����[����J�����(�`�~�$�]����3�e����q�t���ޕ:���Ė�&�J�Y����^�z������;�{�ə�"�W�m�����Қ�8���ћa����g����z�������ѡ �x��t�ȣ#�=�b�~������8�U����X�~�����u�����*�����"�ة�X�������H���٫+�h����F����9�T�Į%��������I����6�k�����߲�� ���ѳ�g����F������x�i�����շ�9���O�R�U�X��������Һ
�m�|�Ƽc��$�u���X�p�ڿ2�s�������.�$�X�����R�����(�+�p��������t�����>���������p���N���(����
������c�����-�������������� �;�s�������K�����&�Q�T�W�x��������������������������������������@�i�������������(�`����������"�K�������U���������!�o������{���E�����M������a����|����n����[����.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|������������������������"�l������=�^���(����E�����;���\������P������=�^���%�����U�	�S�v�^�/����Q�e������������5�������Mc��X��a�V��t��x��6�Q	�	b
N�o
-�8c��`��\R�u����"���~���d-�`�m�= s � � !K!,"#:$%)&�&4'�'�(�('){)�)�)�)�)5*�*�*+E+d+�+�+�+�,�-�-.E.�.�.�.%//�/00�0�0S1�1�3�3�5{6�67�7
8E8l9�9K:�:�:,;�;
<?<)=�=>E>p>�>�>?K?O?S?W?
@F@�@�@�@�A&B�B�BCC~C�C�C5D�DE�E�E,F�F�F?G�G�HGIJ�J�K�K.L�L�LM5MpM�M�M�MN3NrN�NoO�OPiP�P�P�PQWQ�Q�Q�Q6RS�S�TEW�Y�YZ:ZlZ�Z.[{[�[\D\�\O]�]�^1_�_q`�`aa�a�a�a�b�b�b�bIc�c�c dAdkd�d�d�de2eWee�e�e�e�e%f�f'g�g�gHhoi�j�j�l�l�l?mOmxm�m�m0n�no�o�oKp�p�p;q�q�q1rqr�rsLst8tuu�umvpv�vw	w�wHx�x)y�y8z�z�z}{|B|�|g}�}�}`~�~�~Ex���!�u���̀�l���$����N����^���݄��
��5�Y�x���������m�������!����J�{���<�Êa�Ջ�3�Z�����c��X������V��o�Q���)�,���ݒ1�q�%�Δ��G���hashchkisamchkNEJJAKan ikke oprette filen '%-.200s' (Fejlkode: %d - %s)Kan ikke oprette tabellen '%-.200s' (Fejlkode: %d - %s)Kan ikke oprette databasen '%-.192s' (Fejlkode: %d - %s)Kan ikke oprette databasen '%-.192s'; databasen eksistererKan ikke slette (droppe) '%-.192s'; databasen eksisterer ikkeFejl ved sletning (drop) af databasen (kan ikke slette '%-.192s', Fejlkode %d - %s)Fejl ved sletting af database (kan ikke slette folderen '%-.192s', Fejlkode %d - %s)Fejl ved sletning af '%-.192s' (Fejlkode: %d - %s)Kan ikke læse posten i systemfolderenKan ikke læse status af '%-.200s' (Fejlkode: %d - %s)Kan ikke læse aktive folder (Fejlkode: %d - %s)Kan ikke låse fil (Fejlkode: %d - %s)Kan ikke åbne fil: '%-.200s' (Fejlkode: %d - %s)Kan ikke finde fila: '%-.200s' (Fejlkode: %d - %s)Kan ikke læse folder '%-.192s' (Fejlkode: %d - %s)Kan ikke skifte folder til '%-.192s' (Fejlkode: %d - %s)Posten er ændret siden sidste læsning '%-.192s'Ikke mere diskplads (%s). Venter på at få frigjort plads... (Fejlkode: %d - %s)Kan ikke skrive, flere ens nøgler i tabellen '%-.192s'Fejl ved lukning af '%-.192s' (Fejlkode: %d - %s)Fejl ved læsning af '%-.200s' (Fejlkode: %d - %s)Fejl ved omdøbning af '%-.210s' til '%-.210s' (Fejlkode: %d - %s)Fejl ved skriving av filen '%-.200s' (Fejlkode: %d - %s)'%-.192s' er låst mod opdateringerSortering afbrudtView '%-.192s' eksisterer ikke for '%-.192s'Modtog fejl %d - '%-.192s' fra tabel håndteringenDenne mulighed eksisterer ikke for tabeltypen '%-.192s'Kan ikke finde posten i '%-.192s'Forkert indhold i: '%-.200s'Fejl i indeksfilen til tabellen '%-.200s'; prøv at reparere denGammel indeksfil for tabellen '%-.192s'; reparer den'%-.192s' er skrivebeskyttetIkke mere hukommelse. Genstart serveren og prøv igen (mangler %d bytes)Ikke mere sorteringshukommelse. Øg sorteringshukommelse (sort buffer size) for serverenUventet afslutning på fil (eof) ved læsning af filen '%-.192s' (Fejlkode: %d - %s)For mange forbindelser (connections)Udgået for tråde/hukommelseKan ikke få værtsnavn for din adresseForkert håndtryk (handshake)Adgang nægtet bruger: '%-.48s'@'%-.64s' til databasen '%-.192s'Adgang nægtet bruger: '%-.48s'@'%-.64s' (Bruger adgangskode: %s)Ingen database valgtUkendt kommandoKolonne '%-.192s' kan ikke være NULLUkendt database '%-.192s'Tabellen '%-.192s' findes alleredeUkendt tabel '%-.129s'Felt: '%-.192s' i tabel %-.192s er ikke entydigtDatabase nedlukning er i gangUkendt kolonne '%-.192s' i tabel %-.192sBrugte '%-.192s' som ikke var i group byKan ikke gruppere på '%-.192s'Udtrykket har summer (sum) funktioner og kolonner i samme udtrykKolonne tæller stemmer ikke med antallet af værdierNavnet '%-.100s' er for langtFeltnavnet '%-.192s' findes alleredeIndeksnavnet '%-.192s' findes alleredeEns værdier '%-.192s' for indeks %dForkert kolonnespecifikaton for felt '%-.192s'%s nær '%-.80s' på linje %dForespørgsel var tomTabellen/aliaset: '%-.192s' er ikke uniktUgyldig standardværdi for '%-.192s'Flere primærnøgler specificeretFor mange nøgler specificeret. Kun %d nøgler må brugesFor mange nøgledele specificeret. Kun %d dele må brugesSpecificeret nøgle var for lang. Maksimal nøglelængde er %dNøglefeltet '%-.192s' eksisterer ikke i tabellenBLOB feltet '%-.192s' kan ikke bruges ved specifikation af indeksFor stor feltlængde for kolonne '%-.192s' (maks = %lu). Brug BLOB i stedetDer kan kun specificeres eet AUTO_INCREMENT-felt, og det skal være indekseret%s: klar til tilslutninger
Version: '%s'  socket: '%s'  port: %d%s: Normal nedlukning
%s: Fangede signal %d. Afslutter!!
%s: Server lukket
%s: Forceret nedlukning af tråd: %ld  bruger: '%-.48s'
Kan ikke oprette IP socketTabellen '%-.192s' har ikke den nøgle, som blev brugt i CREATE INDEX. Genopret tabellenFelt adskiller er ikke som forventet, se dokumentationenMan kan ikke bruge faste feltlængder med BLOB. Brug i stedet 'fields terminated by'.Filen '%-.128s' skal være i database-folderen og kunne læses af alleFilen '%-.200s' eksisterer alleredePoster: %ld  Fjernet: %ld  Sprunget over: %ld  Advarsler: %ldPoster: %ld  Ens: %ldForkert indeksdel. Den anvendte nøgledel er ikke en streng eller længden er større end nøglelængdenMan kan ikke slette alle felter med ALTER TABLE. Brug DROP TABLE i stedet.Kan ikke udføre DROP '%-.192s'. Undersøg om feltet/nøglen eksisterer.Poster: %ld  Ens: %ld  Advarsler: %ldYou can't specify target table '%-.192s' for update in FROM clauseUkendt tråd id: %luDu er ikke ejer af tråden %luIngen tabeller i brugFor mange tekststrenge til specifikationen af SET i kolonne %-.192sKan ikke lave unikt log-filnavn %-.200s.(1-999)
Tabellen '%-.192s' var låst med READ lås og kan ikke opdateresTabellen '%-.192s' var ikke låst med LOCK TABLESBLOB feltet '%-.192s' kan ikke have en standard værdiUgyldigt database navn '%-.100s'Ugyldigt tabel navn '%-.100s'SELECT ville undersøge for mange poster og ville sandsynligvis tage meget lang tid. Undersøg WHERE delen og brug SET SQL_BIG_SELECTS=1 hvis udtrykket er korrektUkendt fejlUkendt procedure %-.192sForkert antal  parametre til proceduren %-.192sForkert(e) parametre til proceduren %-.192sUkendt tabel '%-.192s' i %-.32sFeltet '%-.192s' er anvendt to gangeForkert brug af grupperings-funktionTabellen '%-.192s' bruger et filtypenavn som ikke findes i denne MySQL versionEn tabel skal have mindst een kolonneTabellen '%-.192s' er fuldUkendt tegnsæt: '%-.64s'For mange tabeller. MySQL kan kun bruge %d tabeller i et joinFor mange felterFor store poster. Max post størrelse, uden BLOB's, er %ld. Du må lave nogle felter til BLOB'sThread stack brugt:  Brugt: %ld af en %ld stak.  Brug 'mysqld --thread_stack=#' for at allokere en større stak om nødvendigtKrydsreferencer fundet i OUTER JOIN; check dine ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerKan ikke læse funktionen '%-.192s'Kan ikke starte funktionen '%-.192s'; %-.192sAngivelse af sti ikke tilladt for delt bibliotekFunktionen '%-.192s' findes alleredeKan ikke åbne delt bibliotek '%-.192s' (errno: %d %-.128s)Kan ikke finde funktionen '%-.128s' i bibliotekFunktionen '%-.192s' er ikke defineretVærten '%-.255s' er blokeret på grund af mange fejlforespørgsler. Lås op med 'mysqladmin flush-hosts'Værten '%-.255s' kan ikke tilkoble denne MySQL-serverDu bruger MySQL som anonym bruger. Anonyme brugere må ikke ændre adgangskoderDu skal have tilladelse til at opdatere tabeller i MySQL databasen for at ændre andres adgangskoderKan ikke finde nogen tilsvarende poster i bruger tabellenPoster fundet: %ld  Ændret: %ld  Advarsler: %ldKan ikke danne en ny tråd (fejl nr. %d). Hvis computeren ikke er løbet tør for hukommelse, kan du se i brugervejledningen for en mulig operativ-system - afhængig fejlKolonne antallet stemmer ikke overens med antallet af værdier i post %ldKan ikke genåbne tabel '%-.192sForkert brug af nulværdi (NULL)Fik fejl '%-.64s' fra regexpSammenblanding af GROUP kolonner (MIN(),MAX(),COUNT()...) uden GROUP kolonner er ikke tilladt, hvis der ikke er noget GROUP BY prædikatDenne tilladelse findes ikke for brugeren '%-.48s' på vært '%-.255s'%-.128s-kommandoen er ikke tilladt for brugeren '%-.48s'@'%-.64s' for tabellen '%-.64s'%-.16s-kommandoen er ikke tilladt for brugeren '%-.48s'@'%-.64s' for kolonne '%-.192s' in tabellen '%-.192s'Forkert GRANT/REVOKE kommando. Se i brugervejledningen hvilke privilegier der kan specificeres.Værts- eller brugernavn for langt til GRANTTabellen '%-.192s.%-.192s' eksisterer ikkeDenne tilladelse eksisterer ikke for brugeren '%-.48s' på vært '%-.255s' for tabellen '%-.192s'Den brugte kommando er ikke tilladt med denne udgave af MySQLDer er en fejl i SQL syntaksenDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAfbrudt forbindelse %ld til database: '%-.192s' bruger: '%-.48s' (%-.64s)Modtog en datapakke som var større end 'max_allowed_packet'Fik læsefejl fra forbindelse (connection pipe)Fik fejlmeddelelse fra fcntl()Modtog ikke datapakker i korrekt rækkefølgeKunne ikke dekomprimere kommunikations-pakke (communication packet)Fik fejlmeddelelse ved læsning af kommunikations-pakker (communication packets)Timeout-fejl ved læsning af kommunukations-pakker (communication packets)Fik fejlmeddelelse ved skrivning af kommunukations-pakker (communication packets)Timeout-fejl ved skrivning af kommunukations-pakker (communication packets)Strengen med resultater er større end 'max_allowed_packet'Denne tabeltype understøtter ikke brug af BLOB og TEXT kolonnerDenne tabeltype understøtter ikke brug af AUTO_INCREMENT kolonnerINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESForkert kolonnenavn '%-.100s'Den brugte tabeltype kan ikke indeksere kolonnen '%-.192s'Tabellerne i MERGE er ikke defineret ensKan ikke skrive til tabellen '%-.192s' fordi det vil bryde CONSTRAINT reglerBLOB kolonnen '%-.192s' brugt i nøglespecifikation uden nøglelængdeAlle dele af en PRIMARY KEY skal være NOT NULL;  Hvis du skal bruge NULL i nøglen, brug UNIQUE istedetResultatet bestod af mere end een rækkeDenne tabeltype kræver en primærnøgleDenne udgave af MySQL er ikke oversat med understøttelse af RAIDDu bruger sikker opdaterings modus ('safe update mode') og du forsøgte at opdatere en tabel uden en WHERE klausul, der gør brug af et KEY felt. %sNøglen '%-.192s' eksisterer ikke i tabellen '%-.192s'Kan ikke åbne tabellenDenne tabeltype understøtter ikke %sDu må ikke bruge denne kommando i en transaktionModtog fejl %d - '%-.192s' mens kommandoen COMMIT blev udførtModtog fejl %d - '%-.192s' mens kommandoen ROLLBACK blev udførtModtog fejl %d mens kommandoen FLUSH_LOGS blev udførtModtog fejl %d mens kommandoen CHECKPOINT blev udførtAfbrød forbindelsen %u til databasen '%-.192s' bruger: '%-.48s' vært: '%-.255s' (%-.64s)Denne tabeltype unserstøtter ikke binært tabeldumpBinlog closed, cannot RESET SOURCEKunne ikke genopbygge indekset for den dumpede tabel '%-.192s'Fejl fra master: '%-.64s'Netværksfejl ved læsning fra masterNetværksfejl ved skrivning til masterKan ikke finde en FULLTEXT nøgle som svarer til kolonne listenKan ikke udføre den givne kommando fordi der findes aktive, låste tabeller eller fordi der udføres en transaktionUkendt systemvariabel '%-.64s'Tabellen '%-.192s' er markeret med fejl og bør repareresTabellen '%-.192s' er markeret med fejl og sidste (automatiske?) REPAIR fejledeAdvarsel: Visse data i tabeller der ikke understøtter transaktioner kunne ikke tilbagestillesFler-udtryks transaktion krævede mere plads en 'max_binlog_cache_size' bytes. Forhøj værdien af denne variabel og prøv igenDenne handling kunne ikke udføres med kørende slave, brug først kommandoen STOP SLAVEDenne handling kræver en kørende slave. Konfigurer en slave og brug kommandoen START SLAVEDenne server er ikke konfigureret som slave. Ret in config-filen eller brug kommandoen CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logKunne ikke danne en slave-tråd; check systemressourcerneBrugeren %-.64s har allerede mere end 'max_user_connections' aktive forbindelserDu må kun bruge konstantudtryk med SETLock wait timeout overskredetDet totale antal låse overstiger størrelsen på låse-tabellenUpdate lås kan ikke opnås under en READ UNCOMMITTED transaktionDROP DATABASE er ikke tilladt mens en tråd holder på globalt read lockCREATE DATABASE er ikke tilladt mens en tråd holder på globalt read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetModtog fejl %d '%-.100s' fra %sModtog temporary fejl %d '%-.100s' fra %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionEns værdier '%-.64s' for indeks '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAdgang nægtet bruger: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' eksisterer ikkeFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionFlere ens nøgler for indeks '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\ݘuh�h�dutch/errmsg.sysnu�[�����T��K���4��>z��G��m��^���	/b���-J��$9+	U	i	�

0
S
p
�
�
�
�
Yv�+Hk����
H
t
�
Q��'y���Oi�#�
.t�(��[s���'���&J,h���Qz���	�)w�Bj�����,��
��
0S� p � 5!j!�!�!-"T"�"�"#3#Z#q#�#�#�#+$\$�$�$%C%�%�%�%>&&�&M'p'�'�'O(�(�(�()=)h)�)�)*B*e*�*�*�*+?+�+�+,�,�,Z-�-.a.�.
/\/�/�/�/:0�0�0�0#1x1�12/2s2�2�23F3c3�3�3?4h4�45c5�5�5!6N6�6�6�647x7�7�78,8P8�8�8�8969v9�9�9o:�:�:	; ;�;�;2<O<p<�<�<&=T=~=�=�=>X>�>�> ?<?�?s@�@A�AB/BPB�B�B�BKCgC�C�C=D�D�D�DjE�E�E�E%FNF�F�F�FGJG_GtG�G�G�G�G�GHPHuH�H�HvI�I�I�I
J+JMJnJ�J�J�J�J�JK5KLKdKyK�K�K�K"LOLqL�L�L�L7MyM�M�MN6NkN�N�N�NsO�O	P�P�P�PQ'QVQ�Q�Q�Q�Q"RRR�R�R�RSKSpS�S�S�S�ST;TfT�T�T�TUBUmU�U�U�UVBV\V�V�VW=WTW�W�W!X~X�XY=YpY�Y�Y�Y-Z]Z�Z�Z�ZZ[�[�[�\N]�][^�^�^_T_�_�_#`t`�`aba�abNbfb�bc5cqc�c�cId�d?ee�e!fqf�f�f>g�g�g)hnh�hEifi�i�i9jej�j�j�j&k^khkrk�k�k:l_l{l�l3m�m�m5n|n�n�n(oko�opCp�p�pqBqwq�q�q/rar�r�r*s�s�s�sTt�t�tu+u`u�u�u`v�v�v�v'w_w�w�w�wox�x�x&yEygy�y�y�y�yzgz�z�z{@{�{�{|5|U|g|�|�|�|}2}�}�}�}~8~V~�~�~*O�N�����L�z���؁��4����	�H�t���Ń�*����������0�l���ކ����K�{����(�<�Y������'�V���ӊ
�:�p������M�o�����#�T��������1���Ǝ3�o���֏	�<�������ϐِ�	�?�_�����Ց�+�L�����ؒ�O���ɓ�+�H�r����L������b����5���>�Úi��e�˜3���ɝ&�`���Ş�8�Z����W���Š�!�X����N�������c�����3�ͤo��^����5�j�����Ч����X�+������������K����)���ͱ�?�{���ʲ��~�߳%�b���˴�����P�p����B�y����������U�v��_�����H����R�����D�o�����,��������&�v���S�6�t�����`����<�y�>�~�����2����������g�����A�V�{���������'�:�}�������P����^������O�����S����z�������<����3�g���8�h�������#�E�v����G�����������7�y����������_�����O�����H�e����� ������a���0�4���%�:�~�@�r�����Q�����[�����7�Z�������b�������B�5���.�c�~���;������D�����#�P�z�����7������4�Z��������)�R�w������P��J�������<�k���m����_����-�R����i����+����C����I�Q�	X�`�9��B��k��	N	�	�	h
�
*��7t����
2
�
�
�
�
��q�����g��*W��6��:��a��"c�����
.e����3c�G���4l��8S��%�s��/ � !�!:"�"�"Y#k#�#�#�#$,$I$%U%�%�%O&�&�&�&�&,'V'�'�'�'�'�'(7([(()�)�)E*z*/+�+�+<,�,4-�--.�.�.8/Y/�/�/�/0:0k0�0�0�0 1�1�1�1-2�2�2Z3�3444T4~4�4�4+5_5�5�5�5"6q6�6�6H7�7�7A8w8�869�9�9:D:v:�:�:;G;x;�;�;�;�;�;=<�<�<$=~=�=�=->�>�>�>]?�?@]@�@SAB�B�B�B3CqC�CD?DuD�D8E�E
F6FTF�F�FZG�G�G6HxH�HI]I�I�I�IqJ�J�J%KYK�K�KLWLL�LMLM�M�MN;N`N�N�NEO�O�O�P�PQ8QlQ�Q�QGR�R�R?S�S�S;T�TdUV�VWX;XjX�X�X�X�X4YUYpY�Y�Y�Y�Y$Z]Z�Z�Z�Z7[_[�[�[$\q\�\�\�]�]^@^�^�^)_�_`�`�`aHaza�a�aFbtb�b�bcRc�c�cdDd�d9ene|e�efff�f�f�f$gtg�g�gh�h�h�h7i�i�j�j2kk�k�l6m�m�m
n\n�nMo�o�ozp)qfq�q�qSr�r�rsost�t�uev�vxLx�x�x y�y�yAz�z�z�z{m{�{�{A|�|E}�}�}+~p~�~�~3����>����S�݂f����A�x��
�H������>���	�g�Ç"�c������6�{��U�M��)�U���ݏ-�y�Ґ
�O�w��������$�����l��u�����0�p��A�����V�����D����*�����ɚ�&�j��������l��2�ܞ��/������B�������G�w�ġ�6�_�b����3�w���N�d�ޤ�G�n����V����\�ɧ������v���ة�q�ͪ��I������i��A���ԭ)��Ȯ
�L�t�������ձd���˲��2�e�i��D����y���P����b����p�ɸ/�=�}����O�պ;��������E��J�¿'�]������	�����I����{����Q�����-���������$�F������s�����(�I�b�����������(�w�����.�������L���L���W�����-��������P������G���i�����A����� �u� ���/���F���&���,�r���m�����6�g�����5���4�����2�]���M������+�|���2�J�������"�S���n����O���n�����+����'���-��F����������P�7���J�����\�����E���W�2��e�����!I
����%����	�	�	
0
x
�
a�:��8
�
�
g�Jc�������'[����(R~�c��[��i��	'D���Al��j�&Q��!W����$=��\��( Q � � !!]!�!�!�!,"^"�"�"�"C#�#�#$�$B%	&0&T&�&'c'�'�'v(�(g)�)�)�)*2*`*~*�*K+�+<,�,$-g-�-'.].�.�.�.,/�/�/�/0�0�01U1|1�1�1�1�12=2�2�2g3r3}3�3�3�3�34h4v4�4�4�4�4%5q5�5�566X6~6�67<7[7p7�78B8v8�8$9=9:�:p;�;�;�<T=�=�=>B>h>�>�>�>??g?�?�@�@�@\A~A�AB*B[B�B�BC=C�C�D!E$EpE�E!FXFvF�F�FG�G�G�G?H�H�H�H+IaI�I�I�I�IHJ|J�J�JCKYK�K�K�K5L\L~L�L�L�L�L[M|N�N�NO�O�PQ<QdQ~Q�Q�Q(RJRwR�R�R�R"STSwS�S�S�S�STXT�T�T.UNUzU�U�U�UV8V_V�V�V�VWBWkW�W�W�WXGXyX�X�X�X+Y]YzY�Y3ZfZ�Z�Z�Z8[U[z[�[�[�[\:\_\�\�\0]n]�]^v^�^�^=_�_+`�`�`qa�aeb�b7ce\e�ePf�f�fgTg�g�gh`h�h�h9iyi�ij�jek�k�klcl�l.mEm^m�m�m�m
n3n�n�n�nojo�o�o1p\p�p�pnq�q)r�r�rs>sgs�s�stQt�t�t0u�u�u_v�v�vwfw�w�w xQx�xpy?z�z�{|8|l|�|�|�|}$}'}k}�}�}W~�~�~��J�������7�u�����.�:�a�S���8������&���ֆ�R����[������(�z����M����'�G�]�T�ǌ�%�<������h���ӎ������ӏ.�L�����ؐ��[���Б
�V����)�\���1�ߔg���ҕ�:�d�w���֖�6�g���ė��U�����;�h���֙�7�Y���ʚ�u�����͛���f��������ݝ�M�����?���ܠ#�]���ޡ[���5�����ʤ��;�����d�������=�v�}����F�����:�U��F���®������4�_���ɰ�V�ű������X����U��a���Ҷ�<�`�d��;�t�����P��b�����=�����(�V�|���ֽ�4�d������>���Կ��=�����y���I�������3�m�����&�T���%������]�������%�W�����*�w���Z���
�D�S�V�Y��������6�d�����/���4�[������7��������E��������c�<�������$�\�z������N��������E�f���������5�p�������6����K������5�Y�}���+�`�z�����(�G�n�����H�n��������$�Q��������0�h����������J�{������6�i�������&�i������f��������<�����/������]���[�p��������=�U�}�����N�~����Y�����-�r����������V��T�z����m���������Z�����[�������;�p������9�������4�n����F������{����*�L�n����c�������{����!�9�c��������\��)�Z������3������krc��7���:b��;q���6.	e	
f
Bx�	N}
Z
�
�
�
,���$>[P�9T��
2V���
8Kr�U��<q���F{�p�[��*b���$W��o��+d��Bj�
_��& J q � � !7!Y!�!�!6"h"�"�"B#l#�#�#�#H$�$�$�$%2%X%�%�%#&F&x&~&�&	'�'$(�(?)�)�)�)�)R*�*K+�+�+D,|,�,�, -�-�-.�. /�/M0�0�0�0'1+1/13171;1?1`1�1�1�1
2Q2�2�2�2�2303C3c3�3R4�45V5�5�5�56Z6�6�6�647�7�78g8�8�8 9�9:�:z;�;�;<=J=u=�=�=�=>#>m>�>�>
?)?J?l?�?�?�?�?"@1@D@W@e@�@�@A6AXAoA�A�A�A2BYBjB�B�B�B@C\C|C�C�C�CD7D�D�DE8E�E�E
F0FyF�F�F�F:GXG�G�G�G-H]HH�H�H�HZIjI�IJJBJpJ�J�JKXK{K�K�K�K/L`LL�L�L�L�LtM�M�NO&OOO�O�OP2PbP�P�PQQHQ�Q�QR2RbR�R�R�R�RS(SJS�S�S�S�S/T[T�T�T�T�TU<UDUNUxU�U�UVrVuV�VXW�W�W�WXXXX?XqX�XYHY�Y�Y�Z�[�[l\.]@^l^�^�^_6_�_�_�_�_`?`q`�`�`a.a[a�a�ab5bSbjb�b�bcgc�c�cd+dMdddgd�d�d�deBe}e�e�efYf�f�f�f g`g�g�g�ghhhh�h�h�hili�i�i�ij$j?jRj}j�j�j�j
k2kzk�k�kl8l^l�l�l�lmym�m�m6n4o�o�o�o#p[prp�p�p1q�q�q�qr�r�r�r�rsAsrs
t
uYuju�u�uv[v�v�v�v�vw*whw�w�w�w�w"xZxzx�x�x�x
y!y�y�yzHz�z+{�{�{(|}j}�}V~�~<��:�l���������$�s�����4�����΄M�����3�m�����}�ڇ����c�҉!�s�͊�P����s���V���9���%�W��N��������͑m���9�c���ē�M�}����>�e����\���ޖ����'���Ԛ�6���ʛ�a���Μ�M�w�ŝ�Z�����ߟR�ƠF���ǡ&���;������O���Ӧ[���ϧ	�>������-����e���D�}�����U����j������������>��������*�G�h�����߳�Q�Ǵ=��˵�=����:�+�ɸ"�~�й����q�2���&�_���ƽ%���۾F���#�Z����B���J������w���
�W�����0���
�Y���3�����)�k����d���2���E�����$�������(���B���)�b���=�y�����M����H�������"�L�������0�{�����c������}�����&�S���?�p���������D�����7���F�����}�����N�����E����+������~�����K�������!�[�������'�p�����U����5���a������X�����N�Q����b����;�o�����!�8�L�f���������	�(�O�~�����)�M�v�����#�8�v������P�����}����	�I������*�e�������O��������-��������+�L�j�������5��	�C���E�v����(\��:[~f�������������������������

"%(+.147:=@CFILORUX��������������������	BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_be����������������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������������������Fz��NQTWZ]�	�	�	5
�
�
�
>u�;�6
V
�
�
&i���.�������������������� #&),/258;>ADGJ�������9<?BEHKNQTWZ]`cfilorux�!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+�����������������������������������������	!$'*-0369<?BEHKNQTW���WZ]`cfilorux{~�����������9�%���-��Ff����Cm���� @ m � �  !�!
"="$#W#�#�$�$�$�$<%�%�%�%�%�%�%�%�%�%�%&�&'X'�'�'(~(�(�(	)")_)�)*4*_*�*z+�+0,�,---c-f-i-l-o-r-u-x-{-~-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-.......... .#.&.).,./.2.5.8.;.>.A.D.G.J.M.P.S.V.Y.\._.b.e.h.k.n.q.t.w.z.}.�.�.�.�.�.�.�.�.�.�.�./!/$/'/*/-/0/3/6/9/</?/B/E/H/K/N/Q/T/W/Z/]/`/c/f/i/l/o/r/u/x/{/~/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/0000000000 0#0&0)0,0/0205080;0>0A0D0G0J0M0P0S0V0Y0\0_0b0e0h0k0n0q0t0w0z0}0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0111
1
1111111"1%1(1+1.1114171:1=1@1C1F1I1L1O1R1U1X1[1^1a1d1g1j1m1p1s1�1b2�2�293y3�3�344d4�4�45+5D5U5�5�5�596z6�6�6�67:7Z7{7�7�7�7<8y8�899:9Z9�9�9:n:�:�:�:\;�;�;6<�<�<=B=e=�=�=�=&>�>�>??@?�?@`@c@f@i@l@o@r@u@x@{@~@*AHAKA�A�ABEBfB�B�BC�C2E�E�EFoF'G/H�H�H�H"I%I(I�I�J	K?LdL�L�L�LM1M4M7M:M=M@MCMFMIMLM�M�M�M�M�MNNDNGNqNtNwNzN}N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�NOOO�O�O�O�O�O�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P$Q'Q�QxR{R~R�R�R�R�RS9SoS�S�S�STHT�TU!U$U'U*U-U0U3U6U9U<U^U�U�U�V�V�V�V�W,XYMYmZ�Zo[Y\�\�\�\	^�^_+_d_�_O`�`�`�`
a1aea�a�a�abTb�b�b�b�b�c�c=dZd�d�d�de;ere�e�e)f�fgg]g�gh`h�h$i4i7ici�i�i�i�i:jPjtj<k�k�kl/lfl�l�l�l.m�m�mn?n�n�nXo�o�o�op7p:p�p�p�pqCqaq�q�q�q�q�q�qrrr
r
rr�r�r(s]s�st�tumu�u�u�u)v\v�v6www�wwx�x]yzy�yzhz�z{�{�{@|y|�|}7}�}�}�}~�~�~}���'������ʂ=�R�n����A�e�������*�s�����ͅ��ӆ��5�m�}���ɇ��5���ň6�[���
�'�b���ӊ&�q�΋4�n����a�֍ ���ߎP�������=���(�����f��P�����Q����@������V�t��S����)�[�����g�j���ԙ0�������@�O���ߛT�p������1�q�����M�c�x���Ȟ��.���ǟW���֡]���
�p�������ǥ�n���j����3�X�t�����.�K����N�t������k���� ������έ��N�����߮��>���ϯ!�^����<���ֱ/�J������������?����,�a�����ն���x�Ƿ�]����<�v�����n�_�����˻�/���E�H�K�N��������Ⱦ�c�r���Y���k���N�f���(�i�������$��N�����H������!�f��������j�����4���������f���D����u���������Y�����#���������������1�i�������A��������G�J�M�n��������������������������������������6�_��������������V�{����������A�������K����������e���x���q���;�����C�������W����r����d�����Q�����$�'�*�-�0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~������������������b������3�T����u���;�����1���R������F������3�T�{�����K���I�l�T�%����G�[��������+��v��CY��N��W��L��j	�	�	n
�
��,�G
�
X�D�e#v.�Y��V��RH�k�����vt����Z #!�!V"�"c#�#3$i$�$�$%A%"&'0()*�**+�+w,�,-q-�-�-�-�-+.�.�./;/Z/�/�/�/v0�1�12;2�2�2�23u3�3&4�4�4I5�5�7�7�9q:�:;�;<;<b=�=A>�>�>"?�?@5@A�AB;BfB�B�BCACECICMCD<D�D�D�D�EF�F�F9GtG�G�G+H�HII�I"J�J�J5K�K�L=M�M�N�O�O$P�P�P�P+QfQ�Q�Q�QR)RhR�ReS�S
T_T�T�T�TUMUwU�U�U,V�V�W}X;[�]�]�]0^b^�^$_q_�_
`:`�`Ea�a�b'c�cgd�dee|e�e�ezf}f�f�f?g�g�gh7hah�h�h�hi(iMiuixi�i�i�ij�jk|k�k>lem�n�n�p�p�p5qEqnq�q�q&r�r
s�s�sAt�t�t1u�u�u'vgv�vwBwx.xky�yczfz�z�z�z�{>|�|}�}.~�~�~s�8��]����V���Ƃ;�n���ʃ��k���Ä��b�������D����T���ӈ����+�O�n�y��������c��z���������@�q���2���W�ˏ��)�P�}���Y���N������L��e�G����"��Ӗ'�g��Ę��=���hashchkisamchkNEEJAKan file '%-.200s' niet aanmaken (Errcode: %d - %s)Kan tabel '%-.200s' niet aanmaken (Errcode: %d - %s)Kan database '%-.192s' niet aanmaken (Errcode: %d - %s)Kan database '%-.192s' niet aanmaken; database bestaat reedsKan database '%-.192s' niet verwijderen; database bestaat nietFout bij verwijderen database (kan '%-.192s' niet verwijderen, Errcode: %d - %s)Fout bij verwijderen database (kan rmdir '%-.192s' niet uitvoeren, Errcode: %d - %s)Fout bij het verwijderen van '%-.192s' (Errcode: %d - %s)Kan record niet lezen in de systeem tabelKan de status niet krijgen van '%-.200s' (Errcode: %d - %s)Kan de werkdirectory niet krijgen (Errcode: %d - %s)Kan de file niet blokeren (Errcode: %d - %s)Kan de file '%-.200s' niet openen (Errcode: %d - %s)Kan de file: '%-.200s' niet vinden (Errcode: %d - %s)Kan de directory niet lezen van '%-.192s' (Errcode: %d - %s)Kan de directory niet veranderen naar '%-.192s' (Errcode: %d - %s)Record is veranderd sinds de laatste lees activiteit in de tabel '%-.192s'Schijf vol (%s). Aan het wachten totdat er ruimte vrij wordt gemaakt... (Errcode: %d - %s)Kan niet schrijven, dubbele zoeksleutel in tabel '%-.192s'Fout bij het sluiten van '%-.192s' (Errcode: %d - %s)Fout bij het lezen van file '%-.200s' (Errcode: %d - %s)Fout bij het hernoemen van '%-.210s' naar '%-.210s' (Errcode: %d - %s)Fout bij het wegschrijven van file '%-.200s' (Errcode: %d - %s)'%-.192s' is geblokeerd tegen veranderingenSorteren afgebrokenView '%-.192s' bestaat niet voor '%-.192s'Fout %d - '%-.192s' van tabel handlerTabel handler voor '%-.192s' heeft deze optie nietKan record niet vinden in '%-.192s'Verkeerde info in file: '%-.200s'Verkeerde zoeksleutel file voor tabel: '%-.200s'; probeer het te reparerenOude zoeksleutel file voor tabel '%-.192s'; repareer het!'%-.192s' is alleen leesbaarGeen geheugen meer. Herstart server en probeer opnieuw (%d bytes nodig)Geen geheugen om te sorteren. Verhoog de server sort buffer sizeOnverwachte eof gevonden tijdens het lezen van file '%-.192s' (Errcode: %d - %s)Te veel verbindingenGeen thread geheugen meer; controleer of mysqld of andere processen al het beschikbare geheugen gebruikt. Zo niet, dan moet u wellicht 'ulimit' gebruiken om mysqld toe te laten meer geheugen te benutten, of u kunt extra swap ruimte toevoegenKan de hostname niet krijgen van uw adresVerkeerde handshakeToegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' naar database '%-.192s'Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' (Wachtwoord gebruikt: %s)Geen database geselecteerdOnbekend commandoKolom '%-.192s' kan niet null zijnOnbekende database '%-.192s'Tabel '%-.192s' bestaat alOnbekende tabel '%-.129s'Kolom: '%-.192s' in %-.192s is niet eenduidigBezig met het stoppen van de serverOnbekende kolom '%-.192s' in %-.192sOpdracht gebruikt '%-.192s' dat niet in de GROUP BY voorkomtKan '%-.192s' niet groeperenOpdracht heeft totaliseer functies en kolommen in dezelfde opdrachtHet aantal kolommen komt niet overeen met het aantal opgegeven waardesNaam voor herkenning '%-.100s' is te langDubbele kolom naam '%-.192s'Dubbele zoeksleutel naam '%-.192s'Dubbele ingang '%-.192s' voor zoeksleutel %dVerkeerde kolom specificatie voor kolom '%-.192s'%s bij '%-.80s' in regel %dQuery was leegNiet unieke waarde tabel/alias: '%-.192s'Foutieve standaard waarde voor '%-.192s'Meerdere primaire zoeksleutels gedefinieerdTeveel zoeksleutels gedefinieerd. Maximaal zijn %d zoeksleutels toegestaanTeveel zoeksleutel onderdelen gespecificeerd. Maximaal %d onderdelen toegestaanGespecificeerde zoeksleutel was te lang. De maximale lengte is %dZoeksleutel kolom '%-.192s' bestaat niet in tabelBLOB kolom '%-.192s' kan niet gebruikt worden bij zoeksleutel specificatieTe grote kolomlengte voor '%-.192s' (max = %lu). Maak hiervoor gebruik van het type BLOBEr kan slechts 1 autofield zijn en deze moet als zoeksleutel worden gedefinieerd.%s: klaar voor verbindingen
Version: '%s'  socket: '%s'  port: %d%s: Normaal afgesloten 
%s: Signaal %d. Systeem breekt af!
%s: Afsluiten afgerond
%s: Afsluiten afgedwongen van thread %ld  gebruiker: '%-.48s'
Kan IP-socket niet openenTabel '%-.192s' heeft geen INDEX zoals deze gemaakt worden met CREATE INDEX. Maak de tabel opnieuwDe argumenten om velden te scheiden zijn anders dan verwacht. Raadpleeg de handleidingBij het gebruik van BLOBs is het niet mogelijk om vaste rijlengte te gebruiken. Maak s.v.p. gebruik van 'fields terminated by'.Het bestand '%-.128s' dient in de database directory voor the komen of leesbaar voor iedereen te zijn.Het bestand '%-.200s' bestaat reedsRecords: %ld  Verwijderd: %ld  Overgeslagen: %ld  Waarschuwingen: %ldRecords: %ld  Dubbel: %ldFoutief sub-gedeelte van de zoeksleutel. De gebruikte zoeksleutel is geen onderdeel van een string of of de gebruikte lengte is langer dan de zoeksleutelHet is niet mogelijk alle velden te verwijderen met ALTER TABLE. Gebruik a.u.b. DROP TABLE hiervoor!Kan '%-.192s' niet weggooien. Controleer of het veld of de zoeksleutel daadwerkelijk bestaat.Records: %ld  Dubbel: %ld  Waarschuwing: %ldYou can't specify target table '%-.192s' for update in FROM clauseOnbekend thread id: %luU bent geen bezitter van thread %luGeen tabellen gebruikt.Teveel strings voor kolom %-.192s en SETHet is niet mogelijk een unieke naam te maken voor de logfile %-.200s.(1-999)
Tabel '%-.192s' was gelocked met een lock om te lezen. Derhalve kunnen geen wijzigingen worden opgeslagen.Tabel '%-.192s' was niet gelocked met LOCK TABLESBlob veld '%-.192s' can geen standaardwaarde bevattenDatabasenaam '%-.100s' is niet getoegestaanNiet toegestane tabelnaam '%-.100s'Het SELECT-statement zou te veel records analyseren en dus veel tijd in beslagnemen. Kijk het WHERE-gedeelte van de query na en kies SET SQL_BIG_SELECTS=1 als het stament in orde is.Onbekende FoutOnbekende procedure %-.192sFoutief aantal parameters doorgegeven aan procedure %-.192sFoutieve parameters voor procedure %-.192sOnbekende tabel '%-.192s' in %-.32sVeld '%-.192s' is dubbel gespecificeerdOngeldig gebruik van GROUP-functieTabel '%-.192s' gebruikt een extensie, die niet in deze MySQL-versie voorkomt.Een tabel moet minstens 1 kolom bevattenDe tabel '%-.192s' is volOnbekende character set: '%-.64s'Teveel tabellen. MySQL kan slechts %d tabellen in een join bevattenTe veel veldenRij-grootte is groter dan toegestaan. Maximale rij grootte, blobs niet meegeteld, is %ld. U dient sommige velden in blobs te veranderen.Thread stapel overrun:  Gebruikte: %ld van een %ld stack. Gebruik 'mysqld --thread_stack=#' om een grotere stapel te definieren (indien noodzakelijk).Gekruiste afhankelijkheid gevonden in OUTER JOIN. Controleer uw ON-conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerKan functie '%-.192s' niet ladenKan functie '%-.192s' niet initialiseren; %-.192sGeen pad toegestaan voor shared libraryFunctie '%-.192s' bestaat reedsKan shared library '%-.192s' niet openen (Errcode: %d %-.128s)Kan functie '%-.128s' niet in library vindenFunctie '%-.192s' is niet gedefinieerdHost '%-.255s' is geblokkeeerd vanwege te veel verbindings fouten. Deblokkeer met 'mysqladmin flush-hosts'Het is host '%-.255s' is niet toegestaan verbinding te maken met deze MySQL serverU gebruikt MySQL als anonieme gebruiker en deze mogen geen wachtwoorden wijzigenU moet tabel update priveleges hebben in de mysql database om wachtwoorden voor anderen te mogen wijzigenKan geen enkele passende rij vinden in de gebruikers tabelPassende rijen: %ld  Gewijzigd: %ld  Waarschuwingen: %ldKan geen nieuwe thread aanmaken (Errcode: %d). Indien er geen tekort aan geheugen is kunt u de handleiding consulteren over een mogelijke OS afhankelijke foutKolom aantal komt niet overeen met waarde aantal in rij %ldKan tabel niet opnieuw openen: '%-.192sFoutief gebruik van de NULL waardeFout '%-.64s' ontvangen van regexpHet mixen van GROUP kolommen (MIN(),MAX(),COUNT()...) met no-GROUP kolommen is foutief indien er geen GROUP BY clausule isDeze toegang (GRANT) is niet toegekend voor gebruiker '%-.48s' op host '%-.255s'%-.128s commando geweigerd voor gebruiker: '%-.48s'@'%-.64s' voor tabel '%-.64s'%-.16s commando geweigerd voor gebruiker: '%-.48s'@'%-.64s' voor kolom '%-.192s' in tabel '%-.192s'Foutief GRANT/REVOKE commando. Raadpleeg de handleiding welke priveleges gebruikt kunnen worden.De host of gebruiker parameter voor GRANT is te langTabel '%-.192s.%-.192s' bestaat nietDeze toegang (GRANT) is niet toegekend voor gebruiker '%-.48s' op host '%-.255s' op tabel '%-.192s'Het used commando is niet toegestaan in deze MySQL versieEr is iets fout in de gebruikte syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAfgebroken verbinding %ld naar db: '%-.192s' gebruiker: '%-.48s' (%-.64s)Groter pakket ontvangen dan 'max_allowed_packet'Kreeg leesfout van de verbindings pipeKreeg fout van fcntl()Pakketten in verkeerde volgorde ontvangenCommunicatiepakket kon niet worden gedecomprimeerdFout bij het lezen van communicatiepakkettenTimeout bij het lezen van communicatiepakkettenFout bij het schrijven van communicatiepakkettenTimeout bij het schrijven van communicatiepakkettenResultaat string is langer dan 'max_allowed_packet'Het gebruikte tabel type ondersteunt geen BLOB/TEXT kolommenHet gebruikte tabel type ondersteunt geen AUTO_INCREMENT kolommenINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrecte kolom naam '%-.100s'De gebruikte tabel 'handler' kan kolom '%-.192s' niet indexerenNiet alle tabellen in de MERGE tabel hebben identieke gedefinitiesKan niet opslaan naar table '%-.192s' vanwege 'unique' beperkingBLOB kolom '%-.192s' gebruikt in zoeksleutel specificatie zonder zoeksleutel lengteAlle delen van een PRIMARY KEY moeten NOT NULL zijn; Indien u NULL in een zoeksleutel nodig heeft kunt u UNIQUE gebruikenResultaat bevatte meer dan een rijDit tabel type heeft een primaire zoeksleutel nodigDeze versie van MySQL is niet gecompileerd met RAID ondersteuningU gebruikt 'safe update mode' en u probeerde een tabel te updaten zonder een WHERE met een KEY kolom. %sZoeksleutel '%-.192s' bestaat niet in tabel '%-.192s'Kan tabel niet openenDe 'handler' voor de tabel ondersteund geen %sHet is u niet toegestaan dit commando uit te voeren binnen een transactieKreeg fout %d - '%-.192s' tijdens COMMITKreeg fout %d - '%-.192s' tijdens ROLLBACKKreeg fout %d tijdens FLUSH_LOGSKreeg fout %d tijdens CHECKPOINTAfgebroken verbinding %u naar db: '%-.192s' gebruiker: '%-.48s' host: '%-.255s' (%-.64s)De 'handler' voor de tabel ondersteund geen binaire tabel dumpBinlog closed, cannot RESET SOURCEGefaald tijdens heropbouw index van gedumpte tabel '%-.192s'Fout van master: '%-.64s'Net fout tijdens lezen van masterNet fout tijdens schrijven naar masterKan geen FULLTEXT index vinden passend bij de kolom lijstKan het gegeven commando niet uitvoeren, want u heeft actieve gelockte tabellen of een actieve transactieOnbekende systeem variabele '%-.64s'Tabel '%-.192s' staat als gecrashed gemarkeerd en dient te worden gerepareerdTabel '%-.192s' staat als gecrashed gemarkeerd en de laatste (automatische?) reparatie poging mislukteWaarschuwing: Roll back mislukt voor sommige buiten transacties gewijzigde tabellenMulti-statement transactie vereist meer dan 'max_binlog_cache_size' bytes opslag. Verhoog deze mysqld variabele en probeer opnieuwDeze operatie kan niet worden uitgevoerd met een actieve slave, doe eerst STOP SLAVEDeze operatie vereist een actieve slave, configureer slave en doe dan START SLAVEDe server is niet geconfigureerd als slave, fix in configuratie bestand of met CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logKon slave thread niet aanmaken, controleer systeem resourcesGebruiker %-.64s heeft reeds meer dan 'max_user_connections' actieve verbindingenU mag alleen constante expressies gebruiken bij SETLock wacht tijd overschredenHet totale aantal locks overschrijdt de lock tabel grootteUpdate locks kunnen niet worden verkregen tijdens een READ UNCOMMITTED transactieDROP DATABASE niet toegestaan terwijl thread een globale 'read lock' bezitCREATE DATABASE niet toegestaan terwijl thread een globale 'read lock' bezitFoutieve parameters voor %s'%-.48s'@'%-.64s' mag geen nieuwe gebruikers creerenIncorrecte tabel definitie; alle MERGE tabellen moeten tot dezelfde database behorenDeadlock gevonden tijdens lock-aanvraag poging; Probeer herstart van de transactieHet gebruikte tabel type ondersteund geen FULLTEXT indexenKan foreign key beperking niet toevoegenKan onderliggende rij niet toevoegen: foreign key beperking gefaaldCannot delete or update a parent row: a foreign key constraint failsFout bij opbouwen verbinding naar master: %-.128sFout bij uitvoeren query op master: %-.128sFout tijdens uitvoeren van commando %s: %-.128sFoutief gebruik van %s en %sDe gebruikte SELECT commando's hebben een verschillend aantal kolommenKan de query niet uitvoeren vanwege een conflicterende read lockHet combineren van transactionele en niet-transactionele tabellen is uitgeschakeld.Optie '%s' tweemaal gebruikt in opdrachtGebruiker '%-.64s' heeft het maximale gebruik van de '%s' faciliteit overschreden (huidige waarde: %ld)Toegang geweigerd. U moet het %-.128s privilege hebben voor deze operatieVariabele '%-.64s' is SESSION en kan niet worden gebruikt met SET GLOBALVariabele '%-.64s' is GLOBAL en dient te worden gewijzigd met SET GLOBALVariabele '%-.64s' heeft geen standaard waardeVariabele '%-.64s' kan niet worden gewijzigd naar de waarde '%-.200s'Foutief argumenttype voor variabele '%-.64s'Variabele '%-.64s' kan alleen worden gewijzigd, niet gelezenFoutieve toepassing/plaatsing van '%s'Deze versie van MySQL ondersteunt nog geen '%s'Kreeg fatale fout %d: '%-.512s' van master tijdens lezen van data uit binaire logSlave SQL thread negeerde de query vanwege replicate-*-table optiesVariabele '%-.192s' is geen %s variabeleIncorrecte foreign key definitie voor '%-.192s': %sSleutel- en tabelreferentie komen niet overeenOperand behoort %d kolommen te bevattenSubquery retourneert meer dan 1 rijOnebekende prepared statement handler (%.*s) voor %s aangegevenHelp database is beschadigd of bestaat nietCyclische verwijzing in subqueriesVeld '%s' wordt van %s naar %s geconverteerdVerwijzing '%-.64s' niet ondersteund (%s)Voor elke afgeleide tabel moet een unieke alias worden gebruiktSelect %u werd geredureerd tijdens optimtalisatieTabel '%-.192s' uit een van de SELECTS kan niet in %-.32s gebruikt wordenClient ondersteunt het door de server verwachtte authenticatieprotocol niet. Overweeg een nieuwere MySQL client te gebruikenAlle delete van een  SPATIAL index dienen als NOT NULL gedeclareerd te wordenCOLLATION '%s' is niet geldig voor CHARACTER SET '%s'Slave is reeds actiefSlave is reeds gestoptOngecomprimeerder data is te groot; de maximum lengte is %d (waarschijnlijk, de lengte van de gecomprimeerde data was beschadigd)ZLIB: Onvoldoende geheugenZLIB: Onvoldoende ruimte in uitgaande buffer (waarschijnlijk, de lengte van de ongecomprimeerde data was beschadigd)ZLIB: Invoer data beschadigdRow %u was cut by GROUP_CONCAT()Rij %ld bevat niet de data voor alle kolommenRegel %ld ingekort, bevatte meer data dan invoer kolommenColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDubbele ingang '%-.64s' voor zoeksleutel '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTToegang geweigerd voor gebruiker: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' bestaat nietFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDubbele ingang voor zoeksleutel '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�y�ɕ���english/errmsg.sysnu�[��������Dr��
K���
7X���B���Q���Cb���L������I^n����		%	K	g	�	�	�	
'
D
i
�
�
�
�
(U���=��-
B
`
w
�
�
U��
B`�Dw���-Y��Ik�+Gx���Pt�����.o�2Vx���\��e��K}���F��%���,d�)I���Cn���% [ � � !C!�!�!/"�"�"�"#y#�#�#�#*$Q$z$�$�$%K%n%�%�%�%�%.&�&�&�&3'q'�'H(�(�(g)�)�)*Q*�*�*+U+o+�+�+1,f,�,�,-2-Y-�-�-�-._.�.�./e/�/�/0C0o0�0�01T1x1�1�1�12T22�2�2�23?3�3�34F4a4�4�4	5j5�5�5�56m6�6�6�6-7\7�7�78g8�849�9:[:;W;v;�;�;	<%<�<�<=4=�=�=>8>�>�>$?C?l?�?�?�?0@\@�@�@�@�@�@AA4A[A�A�A�AEB�B�BC2CQCrC�C�C�C�C�CD0DdD|D�D�D�D�D�D#EiE�E�E�E
FDF~F�FG?G[G}G�G�GH:H�HIPI�IJ@JWJnJ�J�J�JK(KiK�K�K�K:L\L�L�L�L
MM9McM�M�M�MN*N\N�N�N�NO1OcO�O�O�O5PeP�P�P�P-QhQ�Q�QOR�R�R�R�R8StS�S�ST>T�T�TU�U�V(W�W�WXbX�X�XYjY�Y�YJZ�Z[W[�[�[8\_\|\�\�\]�]�]�^�^�^h_�_�_7`�`�`apa�ab�b�bc1c�c�c�cdCdmd�d�d�d�d4e�e�e�e9fzf�f"g|g�g�g/hoh�h�hYi�i�i�i]j�j�jk<kvk�k�k6lql�l�l,m�m�mnLnrn�n�n=o�o�o pEpnp�p�p�pDq�q�q2rmr�r�r�rss+sas�sttMt�tu'udu|u�u�u�uv>vYvyv�vw:wcww�w�w2xqx�xy�y�yAz�z�z�z{0{b{{{�{4|P|�|�|�|}-}q}�}�}(~Z~�~9w���U�ҀV����� �0�K�g�{������&�f���Ӄ�I�y���ׄ4�]������7�b���Ć܆��2�p�އ�r�����H�{�������� �H�~�������?�j���ʋ��0���ߌ�@�j�������D���ĎO�����O���t��}����F���
�r����e���ڗ�@�w�����M���љ�?�`����T���ϛ�(�Q����+�g����&����&�i���Ҡ��ס����_�4��R���çè�C����]�Ū�;�s���ܫ��,����Y�������M��&�S������$�w���2���*�C�����'�����3�}�̵;���ö,�y������a��L����[�����R���k���ɽ�����<�q���s����)�g��������9�����#�v���������
�*�\�o�������,�����T�����%�P�����-����Q����6�P�2�q�����h�����m�������%�X�z����L�|�����������d����0�����*������|����u���0���/�M����8�����]�a���R�g���m�����
�~����������d�������'���������o�b��[������h����I�q���%�P�}������d����0�a�������	�1�V��������"�}���w����(�H�i���'������A������Z���������X��3�p���&�v�J��0�~��6��������f�����-o�L��>{���W�&d���$@_��
,�1��	�	�	
�
�
W��c��g
�
�
1��	O���H��7[��,`�t�	8a�� Ae��R	��\�C�g������8Yv>��|��� Y � � � � � 	!@!d!�!U"�"�"r#�#\$�$%i%�%a&'Z'�'�'e(�(�(�()<)g)�)�)�)*M*�*�*+Z+�+,�,-8-a-�-�-�-�-X.�.�.�./O/�/�/+0u0�0�0n1�12c2�23=3q3�3�34G4t4�4�4�4�4�4)5j5�56Q6�6�6+7Z7�7�7(8�8�8L9�9:�:B;�;<)<`<�<�<4=l=�=�=e>�>7?c?�?�?)@�@�@AcA�A
BJB�B�B�B!C�C�C,DRD�D�DEBE�E�E�E-FyF�F�F1GhG�G�G#HrH�HI�I�I2JeJ�J�JKtK�KLlL�L	MhM�M�NHO�OJP4QhQ�Q�Q�Q�QRaR�R�R�R�R�RSQS�S�S�STdT�T�TUQU�UV$V�V
W@WmW�WXVX�X3Y�YZCZuZ�Z�Z[s[�[�[\<\\�\]C]q]�]f^�^�^�^I_�_�_�_�_Q`�`�`a/a�ab%bdbc�c"d_d�d�d�ecf�f�f7g�ghzh�h+i�iVj�j�j&k�k�k�k<l�lBmn�n�o�oEqyq�q
rMr�rsns�s�s	tCt�t�t#unu�urv�vwXw�w�w+x`x�x y�ykz�z{�{
|�|�|I}n}�} ~:~u~�~�~k�6����O���Ɂ� �c���8���z�>�V���ψ
�Z�����7�|�����I�ˋ�Q���+������ڎ�I�]����n�ސ �C���Α(�q�В�W���ԓ��.�S���Ô���(����_�	�$�\����4�o�ʙ�#�t����3�c�����ٛ�`����2�{����0�t���ܞ/���ʟ2�����I�¡����ʢ�E�����'�v���ݤ!����n�Ц�V�����:�y���ب5�©8����˫��*�_������q�˭B���ˮ}��F����F�����\�j�����|��h����H���r��w��T���˹��к6���9���v��4����J�~����Z�����Q�s�-���������U�v�����D��A����U������[������y���y��������Z������I�}����C�t�
�������n�����M���M���\���s�
�S��Y��������#�c���&���b���a����_�����z���.���X���	�_�w������O���������L�|������X�����T���Z��s���C���*���}�d��w��*����&�r�����_���<����%����'�N�v���:���R���J�=]��g�e�@��=w/	�	�	�	H
�
'��
E
T
�
�
�
�
,U��C������9���6Tq��Bn����2S~��<N����Qj�;��+U~�28���+Y���%p�K�o6]��G � � !�!�!�"�"�"#E#_#�#�#�#x$�$i%�%Q&�&'T'�'�'�''(Y(�(�(,)I)�)*J*�*�*�*�*�*	+4+j+�+,�,�,�,�,�,�,-4-�-�-�-�-�-.R.�.�.	/c/�/�/000i0�0�01<1o1�1�1Q2j2�3�3�4�45�5�6�6%7I7o7�7�7�78l8�8�8�9�9:�:�:�:-;W;�;�;<5<j<�<�=N>Q>�>�>N?�?�?�?�?K@�@�@'AlA�A�A$BXB�B�B�BC!CuC�C�CDpD�D�D�DEbE�E�E�E�E�E�E�F�G�G�GDHI�ICJiJ�J�J�JKUKwK�K�K�KLOL�L�L�L�L�LMEM�M�M�M[N{N�N�N�NO9OeO�O�O�OPDPoP�P�P�P
Q@QtQ�Q�Q�QRXR�R�R�R`S�S�S�S"TeT�T�T�T�TU8UgU�U�UV]V�V�VHW�W�W"XjX�XXY�YZ�Z[�[�[d\F^�^�^}_�_`>`�`�`�`Ea�a�a�afb�b�b?c�c�d�d�d5e�e
f[frf�f�f�fg7g`g�g�ghLh�h�h'i^i�i�i#j�j�jVk�kl9lkl�l�l�l8m~m�mn]n�no�o�o�oKp�p�pqMq~q�q�rlst�t0ueu�u�u�u�uFvQvTv�v�vw�w�w)x�x'ywy�y�yz?{d{�{�{*|[|g|�|�},~e~�~�~S��I�����������U����@�z�˃�T�t������-�R�i����A�������F�ǈ��[�y���ۉ�$���Ί��:���֋�V���݌^��������?�g�����Ǐ� �c������
�?������A�h���ے�3�d�������=�����ߔ��%�G������̖�
�?�z�ژ$�l���	�P��������&�b�Ĝ�����I�h���.������?���?�j������G�s�ץ�=�g���0�s�����Ȩި@�a�����������ܫ�.����ҭ9����������i�����8�h���Ӳ%�}�F���״�@�j�ϵ-�A�U�����Ѷ�4�a�������k�Ҹ�)�j����K����I�v�����`�����"�S����R�¾�E������#�R�����!�W��������7�q������������.�c������\���a������E�d������8�r�����B���i���	�)�Q��������I�{����'�G�r��������*�b��������c���2�x�����-�b�����)�X�������#�U�t�������u��������8�Q�~������5�]���������*�J�w������>�c��������S������H������'�H�i���0�F�\�����<���
����������I�j��������{�����K�����+�Z������A������C������@�������������*��������h������/�f�����(�a�����0�s����1������W�y�����3�������������
��N�f������!����E�����V������`�����%�����L������d����B�g����H��h���<c[�C�;o��6{�3���Y��Qk�?	}	�	f
�
�
�
7_���:ex���
�
�
i���Ks���2��W��� Q��
;��X��?o��:��*Sw��<d��c��o���
u��5_��Ps�� 6 !Q!�!l"�"�"#$##�#x$�$%q%�%�%&M&�&�&D'�'M(�(z)�)* *T*X*\*`*d*h*l*�*�*�*�*7+~+�+�+�+,C,],p,�,�,-�-1.�.�.�.�.//�/�/�/0a0�01>1�1�1�1M2�2I3%4�4�45B5A6w6�6�6�6(7.7P7�7�7�778V8w8�8�8�89,9O9^9q9�9�9�9�9@:c:�:�:�:�:,;_;�;�;�;�;,<m<�<�<�<�<=9=d=�=>5>e>�>�>7?]?�?�?�?@g@�@�@�@AZA�A�A�ABB�B�B�B.CCCoC�C�CDDD�D�D�D�D#E\E�E�E�E�E�E�E�FG�G2HSH|H�HI0I_I�I�I�IBJEJuJ�J�J4K_K�K�K�K�KL<LULwL�L�L�LM\M�M�M�M$N'NJNiNqN{N�N�NO0O�O�OP�P�P�PQ<Q?QBQEQlQ�QRKRuR�R�RT�T�T�U[VmW�W�W�WKXcX�X�X�XY.YlY�Y�YZ.Z[Z�Z�Z�ZA[b[�[�[�[\2\�\�\#]9]X]z]�]�]�]�]^=^o^�^�^_F_�_�_�_`M`�`�`�`a/aGa�a�a�abKb�b�b�bc?cQclcc�c�c�cd7d_d�d�de8eee�e�e�efIf�f�f�fcgah�hi%iPi�i�i�i%j^j�j�j+k<k�k�k�kl=lnl�l7m7n�n�n�noGo�o�o�o�op>pWp�p�p�p�pqOq�q�q�q�qr7rNr�r�r<sus�sXt�t%uUu=v�v�v�wxix�x0ygy�y�y�zD{�{�{-|Q|�|�|}/}a}�}�}�}z~�~�~)`���A����B��������N�����I�}�ބD���'����f�ۇR���/�{�ɉ���Ҋ�����@�f���ʌ�4�z����.�k���Ў���ُ�9�I���T�ޓ�F�c�̔��1���ʕ��>�z����.���%������s�Ś�S�ɛh�Ĝ@��|������Ơ��6�k���K�ˢZ�ۣ;����K�q���Υ)����A���ܧH���ިK���
�k�ݪ#��;�W�t�������;�~��j�����=�j���
�g�X���O�����<���;���_�#�S������R�ķ�s��P������o�׺w�ɻ�@����7���׽�]�̾7����`����V����5����_� �r����Q�����(�U���o�	�V�����j�������z���=�u������O�y�����'�]�����������8�����&�S�����l�����I���*�<�q�����d���s���&������{����r�����X����>������x������N��������T�����%�����@�b�������A�������{�~���1�����?�h������N�e�y����������6�U�|�����!�V�z������P�e������@�}����D�������6�v�����%�W��������G�|������,�Z��������X�y�������#�E�b��6�p��r�����1�U������F�g������������������������
�
�������"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|�����������������	��������!�$�'�*�-�0�3�6�9�<�?�B�E�o�r�u�x�{�~�������������������������������������������������������������������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b�e�h�k�n�q�t�w�z�}������������������������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b�e�h�k�n�q�t�w�z�}������������������������������������������������������������������Ks��D{~������b��k��h�c��;S��	
'
[
�
�
�
�
�
 #&),/258;>ADGJMPSVY\_behknqtw #&),/258;>Afilorux{~��������������K
N
Q
T
W
Z
]
`
c
f
i
l
o
r
u
x
{
~
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
 #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX��������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~�����������������������������4f�R��'Z�Ds��+Bp��A�
@m��M�:jQ����i��"%(+.�- � � !=!�!�!"6"O"�"�"I#a#�#�#�$ %]%�%1&Z&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&'''''''''' '#'&')','/'2'5'8';'>'A'D'G'J'M'P'S'V'Y'\'_'b'e'h'k'n'q't'w'z'}'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'K(N(Q(T(W(Z(](`(c(f(i(l(o(r(u(x({(~(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))))))))) )#)&))),)/)2)5)8);)>)A)D)G)J)M)P)S)V)Y)\)_)b)e)h)k)n)q)t)w)z)})�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)***
*
*******"*%*(*+*.*1*4*7*:*=*@*C*F*I*L*O*R*U*X*[*^*a*d*g*j*m*p*s*v*y*|**�*�*�*�*�*�*�*�*�*�*�*$+�+�+,f,�,�,#-a-�-�-�-9.X.q.�.�.�.'/f/�/�/�/0K0g0�0�0�01(1i1�1�1.2L2g2�2�2�2;3�3�3�34�4�45c5�5$6?6o6�6�6�67S7�78/8L8m89F9�9�9�9�9�9�9�9�9�9�9�9W:u:x:;";G;r;�;�;<8<�<_>�>?F?�?T@\A�A�A(BOBRBUB�B�C6DlE�E�E�EFCF^FaFdFgFjFmFpFsFvFyF�F�F�F
GGEGHGqGtG�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�GHHH
H
HHHHHHH"H%H(H+H.H1H4H�H�H�H�H�H�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�IQJTJK�K�K�K�K�K�KLFLfL�L�L�LM9MuM�MKNNNQNTNWNZN]N`NcNfNiN�N�N�N�O�O�OP�PYQ<RzR�ST�T�U�U�UV6W�W3XXX�X�X|Y�YZ'Z7Z^Z�Z�Z�Z�Z5[�[�[�[�[\�\)]j]�]�]�]
^9^h^�^�^_V_�_;`=`�`�`/a�a�aQbabdb�b�b�b�bcgc}c�cid�deFe\e�e�e�e'f[f�fg=glg�g)h�h�h	i,iJidigi�i�i+jIjpj�j�j�j�j%k(k+k.k1k4k7k:k=k�k�kUl�l�l.m�m4n�n�n�n)oVo�opcp�pq�qr�r�r�rAs�s�s2tu,umu�u�u3vdv�v�vw4w�w�w�x&y�yTz�zH{�{�{j||�|�|;}n}�}�}�}�}W~�~�~�~�~I�@�C�b���������+�b����c�����:�T���ǃ�S�����a���څ����M����}����"�j�։U���+���
�}�ތ+�~���
�m���ڎK�����G���̐�V���̑'�����ɒ�]�����I�m�|���������Ε�^����
�E�z�����͗��%�[�����������ʛ7���=���3�Þ�C���)����F�`��������2�[�x���3�{���ԣ�*���Ӥ�M���եE���$�{���ϧ�+�k�����N������i����\�w��H���%���@�l����Y�������"�C����A����=�i����&����������1�\���r�u�x�{����@�����-���������G����{�����U�����ý�2�Q�G�{���u����K�N���;����������a������"�����q���K�����0�����9�������P���B���������C�^��������n���#�&�I�t�w�z���������������������������������������?�c���������������K����������$�E�n������x��������D������#���"�h����p����#�����=�����8�����)�~���'�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~�����������������������������������������������E������A�`�����K����h�����^�������.�s����.�`�����H����x�,�v�����R����t�������"���X��8�#�����>�A�p�����{������*y���
�+�3Yt��+q;	
�
P�[*
�
�
�� u���E��;�5���'�P����`���@nO> ]!5"L#�#W$�$�%&J&�&�&�&�&'X'�'(@(h(�(�(�(�(�)�*+=+h+�+�+
,H,�,�,S-�-.v.�.�0�0�2�34>4�405h5�67n7�78O8�809b9L:�:@;h;�;�;�;9<n<r<v<z<-=i=�=�=�=�>I?�?@f@�@�@AXA�A?B�B�BOC�CDbDE�EjF'G�G�H IQI�I�I(JXJ�J�J�JK3KVK�K�K�L�L7M�M�M�M!N@NzN�N�NOYO(P�P�QhT�V�V*W]W�W�WQX�X�X7YgY�YrZ[�[T\�\�]�];^@^�^�^�^�_�_�_`l`�`	aCada�a�a�ab>bUbzb�b�b�b�b�bHc�cJd�d�dke�f�gh�i
jjbjrj�j�j�jSk�k:l�lmnm�mn^n�noTo�o�o=pop.q[q�r	s�s�s�s)t,t�tku�uLv�v[w�w�w�x%yeyz�z�z{�{�{�{h|�|�|�| }D}�}�}�}+~�~�~G��q�Ӏ3�����"�-�@�X�|�������߂
�(���;���ل$�D���8�m���҆_������'�V�}���׉��&�{���؋@�y����t��L�O����T���H��Βj�ғhashchkisamchkNOYESCan't create file '%-.200s' (errno: %d - %s)Can't create table '%-.200s' (errno: %d - %s)Can't create database '%-.192s' (errno: %d - %s)Can't create database '%-.192s'; database existsCan't drop database '%-.192s'; database doesn't existError dropping database (can't delete '%-.192s', errno: %d - %s)Error dropping database (can't rmdir '%-.192s', errno: %d - %s)Error on delete of '%-.192s' (errno: %d - %s)Can't read record in system tableCan't get status of '%-.200s' (errno: %d - %s)Can't get working directory (errno: %d - %s)Can't lock file (errno: %d - %s)Can't open file: '%-.200s' (errno: %d - %s)Can't find file: '%-.200s' (errno: %d - %s)Can't read dir of '%-.192s' (errno: %d - %s)Can't change dir to '%-.192s' (errno: %d - %s)Record has changed since last read in table '%-.192s'Disk full (%s); waiting for someone to free some space... (errno: %d - %s)Can't write; duplicate key in table '%-.192s'Error on close of '%-.192s' (errno: %d - %s)Error reading file '%-.200s' (errno: %d - %s)Error on rename of '%-.210s' to '%-.210s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)'%-.192s' is locked against changeSort abortedView '%-.192s' doesn't exist for '%-.192s'Got error %d - '%-.192s' from storage engineTable storage engine for '%-.192s' doesn't have this optionCan't find record in '%-.192s'Incorrect information in file: '%-.200s'Incorrect key file for table '%-.200s'; try to repair itOld key file for table '%-.192s'; repair it!Table '%-.192s' is read onlyOut of memory; restart server and try again (needed %d bytes)Out of sort memory, consider increasing server sort buffer sizeUnexpected EOF found when reading file '%-.192s' (errno: %d - %s)Too many connectionsOut of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceCan't get hostname for your addressBad handshakeAccess denied for user '%-.48s'@'%-.64s' to database '%-.192s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)No database selectedUnknown commandColumn '%-.192s' cannot be nullUnknown database '%-.192s'Table '%-.192s' already existsUnknown table '%-.129s'Column '%-.192s' in %-.192s is ambiguousServer shutdown in progressUnknown column '%-.192s' in '%-.192s''%-.192s' isn't in GROUP BYCan't group on '%-.192s'Statement has sum functions and columns in same statementColumn count doesn't match value countIdentifier name '%-.100s' is too longDuplicate column name '%-.192s'Duplicate key name '%-.192s'Duplicate entry '%-.192s' for key %dIncorrect column specifier for column '%-.192s'%s near '%-.80s' at line %dQuery was emptyNot unique table/alias: '%-.192s'Invalid default value for '%-.192s'Multiple primary key definedToo many keys specified; max %d keys allowedToo many key parts specified; max %d parts allowedSpecified key was too long; max key length is %d bytesKey column '%-.192s' doesn't exist in tableBLOB column '%-.192s' can't be used in key specification with the used table typeColumn length too big for column '%-.192s' (max = %lu); use BLOB or TEXT insteadIncorrect table definition; there can be only one auto column and it must be defined as a key%s: ready for connections.
Version: '%s'  socket: '%s'  port: %d%s: Normal shutdown
%s: Got signal %d. Aborting!
%s: Shutdown complete
%s: Forcing close of thread %ld  user: '%-.48s'
Can't create IP socketTable '%-.192s' has no index like the one used in CREATE INDEX; recreate the tableField separator argument is not what is expected; check the manualYou can't use fixed rowlength with BLOBs; please use 'fields terminated by'The file '%-.128s' must be in the database directory or be readable by allFile '%-.200s' already existsRecords: %ld  Deleted: %ld  Skipped: %ld  Warnings: %ldRecords: %ld  Duplicates: %ldIncorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keysYou can't delete all columns with ALTER TABLE; use DROP TABLE insteadCan't DROP '%-.192s'; check that column/key existsRecords: %ld  Duplicates: %ld  Warnings: %ldYou can't specify target table '%-.192s' for update in FROM clauseUnknown thread id: %luYou are not owner of thread %luNo tables usedToo many strings for column %-.192s and SETCan't generate a unique log-filename %-.200s.(1-999)
Table '%-.192s' was locked with a READ lock and can't be updatedTable '%-.192s' was not locked with LOCK TABLESBLOB, TEXT, GEOMETRY or JSON column '%-.192s' can't have a default valueIncorrect database name '%-.100s'Incorrect table name '%-.100s'The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okayUnknown errorUnknown procedure '%-.192s'Incorrect parameter count to procedure '%-.192s'Incorrect parameters to procedure '%-.192s'Unknown table '%-.192s' in %-.32sColumn '%-.192s' specified twiceInvalid use of group functionTable '%-.192s' uses an extension that doesn't exist in this MySQL versionA table must have at least 1 columnThe table '%-.192s' is fullUnknown character set: '%-.64s'Too many tables; MySQL can only use %d tables in a joinToo many columnsRow size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBsThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if neededCross dependency found in OUTER JOIN; examine your ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerCan't load function '%-.192s'Can't initialize function '%-.192s'; %-.192sNo paths allowed for shared libraryFunction '%-.192s' already existsCan't open shared library '%-.192s' (errno: %d %-.128s)Can't find symbol '%-.128s' in libraryFunction '%-.192s' is not definedHost '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.255s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192s'Invalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be usedThe host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionYou have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to useDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used storage engine can't index column '%-.192s'Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't existCan't write, because of unique constraint, to table '%-.192s'BLOB/TEXT column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe storage engine for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDuplicate entry '%-.64s' for key '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAccess denied for user '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDuplicate entry for key '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\��'
����estonian/errmsg.sysnu�[��������)H{��2��
:n��>u��3d��En���7]���:|��_���,	F	U	�	�	�	�	�	
<
_
�
�
�
*Gn����2k��
A
�
K_����G�(j� v��(<Ut��S���}���&Ms���_t�d�?x���)R�_�����#��*���u��%t���	 * E u � � !9!u!�!�!"U"�"�"V#x#�#�#$L$c$�$�$�$%7%[%�%�%&S&o&�&�&�&B'g'�'�'H(�(*)|)�)I*�*�*+\+�+�+,R,l,�,-C-r-�-�-.>.e.�.�.�.�.S//�/0a0�0�01?1k1�1�12P2t2�2�2�23P3{3�3�3�34;4|4�45B5]5~5�56f6�6�6�67i7�7�7�7)8X8�8�89c990:�:;W;<S<r<�<�<=!=�=�=�=0>�>�>?4?�?�? @?@h@�@�@�@,AXA�A�A�A�A�ABB0BWB�B�B�BAC�C�CD.DMDnD�D�D�D�D�DE,E`ExE�E�E�E�E�EFeF�F�F�F	G@GzG�GH;HWHyH�H�HI6I�IJLJ�J
K<KSKjK�K�K�KL$LeL�L�L�L6MXM�M�M�MNN5N_N~N�N�NO&OXO�O�O�OP-P_P�P�P�P1QaQ�Q�Q�Q)RdR�R�RKS�S�S�S�S4TpT�T�T
U:U�U�UV�V�W$X�X�XY^Y�Y�YZfZ�Z�ZF[�[\S\�\�\4][]x]�]�]^�^�^�_�_�_d`�`�`3a�a�ablb�bc�c�c�c-d|d�d�de?eie�e�e�e�e0f}f�f�f5gvg�ghxh�h�h+iki�i�iUj�j�j�jYk�k�kl8lrl�l�l2mmm�m�m(n�n�noHono�o�o9p�p�pqAqjq�q�q�q@r�r�r.sis�s�s�stt't]t�tuuIu�uv#v`vxv�v�v�v�v:wUwuw�w
x6x_x{x�x�x.ymy�yz�z�z={�{�{�{|,|^|w|�|0}L}�}�}�}~)~m~�~�~$V�5�s�����S�ЁT������.�I�e�y������$�d���ф�G�w���Յ2�[������5�`���ڇ��0�n�܈�p�����F�y����������F�|�������=�h���Ȍ��.���ݍ�>�h������B���M����M���r���{����D����p����c���ؘ�>�u�����K���Ϛ�=�^����R���͜�&�W����1�m����,����,�o���ء�
�ݢģ��e�:��X���ɨɩ�I���� �c�˫�A�y�����2����_������S��,�Y������*�}���8�����0�I�����-�����9���ҶA���ɷ2����Ǹ�g��R�����a�����X���q���Ͼ���� �B�w���y�����/�m�������?�����)�|����������0�b�u�������2�����Z�����+�V�����3����W����<�V�8�w����n�����s�������+�^������R�����������l����8�����2�����������}���8���7�U���
�@�����e�i���Z�o���u����������������l�������/���������w�j��c�����
�p����Q�y���-�X��������l����8�i��������9�^���������*���������0�P�q���/�����I������b��������'�`��;�x���.�~�R��8����>������n��5w�T��F��'��_�.l���
,Hg��4�
	9	�	�	 
�
�
��_��
k
�
�
o�9��W���P��?c��
!4h�|�@i��(Im�"Z��'d�K�o�����@a~F��% � � � !!a!�!�!�!�!�!"H"l"�"]#�#$z$�$d%�%"&q&�&i'(b(�()m)�)�)�)*D*o*�*�*�*+U+�+�+",b,�,
-�-.@.i.�.�.�.�.`/�/�/�/0W0�0�031}1�1�1v2�2&3k3�34E4y4�4�45O5|5�5�5�5�5616r6�67Y7�7�738b8�8909�9�9T:�:;�;J<�<=1=h=�=�=<>t>�>�>m?�??@k@�@�@1A�A�ABkB�BCRC�C�C�C)D�D�D4EZE�E�E
FJF�F�F�F5G�G�G�G9HpH�H�H+IzI�IJ�J�J:KmK�K�K#L|L�LMtM�MNpN�N�OPP�PRQ<RpR�R�R�R�RSiS�S�S�S�STTYT�T�T�T!UlU�U�UVYV�VW,W�WXHXuX�X"Y^YZ;Z�Z![K[}[�[�[ \{\�\�\]D]�]�]^K^y^�^n_�_�_`Q`�`�`�`�`Ya�a�ab7b�b
c-clcd�d*ege�e�e�fkg�gh?h�h
i�i�i3j�j^k�k�k.l�l�l�lDm�mJn
o�o�p�pMr�r�rsUs�stvt�t�tuKu�u�u+vvv�vzw�wx`x�x�x3yhy�y(z�zs{�{$|�|}�}�}Q~v~�~(B}�� �s��>�����W���т�(�k���@�����F�^���׉�b����?������&�Q�ӌ �Y���3���&�����Q�e���&�v��(�K���֒0�y�ؓ�_���ܔ��6�[���˕ ���0����g��,�d����<�w�Қ��+�|�����;�k������!�h����:������8�|����7���Ҡ:�����Q�ʢ����ң
�M����/�~�ȥ�)���'�v�ا	�^�����B������=�ʪ@�
���Ӭ�2�g������y�ӮJ���ӯ���N����N�����d�r�������
�p����P���z�'����\���Ӻ�ػ>���A��~���<���#�R������b�����"�Y�{�5���������]�~�����L�
�I���'�]������c�'�����������������b�����Q������K�|�������v�����U���U���d���{��[�$�a��������+�k���.���j���i����g���������6���`����g������ �W��������T��������`����\���b��{���K���2�����l����2����.�z�����g��
�D�����-����/V~�B���&Z��"R�Ee�"�o�"m�H��E		7
�
�
�
P�/��
M\����4]���K������A��>\y��Jv����
:[���DV����!Yr�C��3]��:@��3a���-x�S�w> e � � O!�!�!"�"#�#�#�#$M$g$�$�$�$�%�%q&�&Y'�'(\(�(�(�(/)a)�)�)4*Q*�*
+R+�+�+�+�+,,<,r,�,'-�-�-�-�-�-�-.<.�.�.�.�./&/Z/�/�/0k0�0�0181q1�1�12D2w2�2�2Y3r3�45�5�56�6�78-8Q8w8�8�8�89t9�9�9�:;';�;�;�;5<_<�<�<===r=�=�>V?Y?�?@V@�@�@�@ASA�A�A/BtB�BC,C`C�C�C�CD)D}D�D�D
ExE�E�E�EFjF�F�F�F�F�F�F�G�H�HILI&J�JKKqK�K�K�K'L]LL�L�L�LMWM�M�M�M�MN NMN�N�NOcO�O�O�O�OPAPmP�P�P�PQLQwQ�Q�Q�QRHR|R�R�RSS`S�S�S�ShT�T�TU*UmU�U�U�U�UV@VoV�V�V	WeW�W�WPX�X�X*YrY�Y`Z�Z"[�[$\�\�\l]N_�_�_�`�`aFa�a�a�aMb�b�bcnc�c�cGd�d�e�e�e=f�fgcgzg�g�g�gh?hhh�h�hiTi�i�i/jfj�j�j+k�k�k^l�lmAmsm�m�m�m@n�n�noeo�o"p�p�p�pSq�q�qrUr�r�r�sttuv8vmv�v�v�v�vNwYw\w�w�wx�x�x1y�y/zz�z�z{G|l|�|�|2}c}o}�}�~4m���[�Հ�Q���������"�]�����H���ӄ'�\�|�������5�Z�q����I������'�N�ω���c������
�,���֋�B���ތ$�^����f����Ə�G�o�����ϐ�(�k���đ���G���Ȓ!�I�p�����;�l�������E�����-�O������ԗ��G����,�t�ƚ�X��������.�j�̝ɞ��%�Q�p���6����ɡG�ŢG�r������O�{�ߦ�E�o���8�{�����%�Щ�H�i���ê���������6����ڮA��������#�q�����@�p���۳-���N���ߵ!�H�r�׶5�I�]�����ٷ�<�i���ĸ��s�ڹ	�1�r�����S����Q�~�¼��h����*�[����Z�ʿ��M������+�Z�����)�_��������?�y������������6�k�����
�d���i������M�l�����
�@�z���
�$�J���q����1�Y��������Q������/�O�z�������	�2�j�������"�k���:������5�j�����1�`�������+�]�|������}��������@�Y��������=�e��������2�R�������F�k�������%�[�����"�P������/�P�q���8�N�d�����D������������Q�r�������$�������S�����3�b������I���%���K����� �H��������
�����2�������!�p�����	�7�n�����0�i�����8�{���
�9�����	�_�������;����$�������
���V�n�����
�)���#�M�����^����� �h����-�����T�����l����J�o����P�p��Dkc�K�Cw�>��;���$a�		Y	s	�	G
�
�
n��?g���
B
m
�
�
�
��q���S{� �:��_���(Y��C��`��Gw��B��2[��Dl��k��w���}��	=g��' X { � � 	!>!"Y"�"t#�#�#$,$�$%�%�%&y&�&�&$'U'�'�'L(�(U)�)�*�*
+(+\+`+d+h+l+p+t+�+�+�+�+?,�,�,�,�,-K-e-x-�-�-�.�.9/�/�/�/�/70�0�0�01i1�12F2�2�2�2U3�3Q4-5�5�5!6J6I77�7�780868X8�8�8�8?9^99�9�9�9:4:W:f:y:�:�:�:;H;k;�;�;�;�;4<g<�<�<�<=4=u=�=�=�=�=>A>l>�>?=?m?�?�??@e@�@�@�@AoA�A�A�A#BbB�B�B�BC%C�C�C�C6DKDwD�D�DELE�E�E�EF+FdF�F�F�F�FGG�GH�H:I[I�I�I
J8JgJ�J�J�JJKMK}K�KL<LgL�L�L�L�LMDM]MM�M�MNNdN�N�N�N,O/OROqOyO�O�O�OP8P�P�PQ�Q�QR$RDRGRJRMRtR�R SSS}S�S�SU�U�U�VcWuX�X�XYSYkY�Y�Y�YZ6ZtZ�Z�Z	[6[c[�[�[\I\j\�\�\�\]:]�]�]+^A^`^�^�^�^�^�^_E_w_�_�_`N`�`�`�`$aUa�a�a�ab7bOb�b�b�bcSc�c�c�cdGdYdtd�d�d�d�de?ege�e�ef@fmf�f�f�fgQg�g�g�gkhii�ij-jXj�j�j�j-kfk�k�k3lDl�l�l�lmEmvm�m?n?o�o�o�opOp�p�p�pq"qFq_q�q�q�q�qrWr�r�r�r�r	s?sVs�s�sDt}t�t`u�u-v]vEw�w�w�x#yqy�y8zoz�z�z�{L|�|�|5}Y}�}�} ~7~i~�~�~���1�h����!�I����J���#����V����Q����L���/����n��Z���7���ъ���ڋ���&�H�n���ҍ��<������6�s���؏�����A�Q���\��	�N�k�ԕ��9���Җ�F�������6���-��������{�͛��[�ќp�̝H���������Ρ�>�s�ŢS�ӣb��C����S�y���֦1����I����P����S�Ī�s��+��C�_�|�������C�����r����E�r�İ�o�`���W����D�ǴC���g�+�[���Ʒ��Z�̸�{��X���Ⱥ�w�߻�Ѽ�H�����?���߾�e�Կ?����h����^�����=����g�(�z���&�Y����0�]���w��^�����r����������E�}�����#�W�������/�e�����������@�����.�[�����t�����Q���2�D�y����l���{���.�����%�����"�z�����`����F�������������V��������\�����-����H�j�
������I�������������9�����G�p������V�m������������>�]�������)�^�������X�m������H�����"�L�������>�~����-�_��������O��������4�b�������'�`�������+�M�j���>�x��z�����9�]�����N�o��������������������	��������!�$�'�*�-�0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~��������������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�J�M�w�z�}�������������������������������������������������������������������������
�
�������"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|�����������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������S{��$L��������j�� s��p�k��	C[�	�

/c�����

"%(+.147:=@CFILORUX[^adgjmpsvy|"
%
(
+
.
1
4
7
:
=
@
C
F
I
n
q
t
w
z
}
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
SVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`������������������������ #&),/258;>ADGJMPSVY\_behknqtwz}������������������������������<nZ�/b�L{��3Jx��I�Hu��U�BrY����!q� 
 
 $ ' * - 0 3 6 � 5!�!�!"E"�"�"#>#W#�#�#Q$i$�$�$�%(&e&�&9'b'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'(((
(
((((((("(%(((+(.(1(4(7(:(=(@(C(F(I(L(O(R(U(X([(^(a(d(g(j(m(p(s(v(y(|((�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(S)V)Y)\)_)b)e)h)k)n)q)t)w)z)})�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)***
*
*******"*%*(*+*.*1*4*7*:*=*@*C*F*I*L*O*R*U*X*[*^*a*d*g*j*m*p*s*v*y*|**�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++	++++++++!+$+'+*+-+0+3+6+9+<+?+B+E+H+K+N+Q+T+W+Z+]+`+c+f+i+l+o+r+u+x+{+~+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,�,�,-n-�-�-+.i.�.�.�.A/`/y/�/�/�//0n0�0�0�01S1o1�1�1�1202q2�2�263T3o3�3�3�3C4�4�45%5�5�56k6�6,7G7w7�7�7�7"8[8�8	979T9u9:N:�:�:�:�:�:�:�:�:�:�:�:_;};�;'<*<O<z<�<�<=@=�=g?�?	@N@�@\AdB�BC0CWCZC]C�C�D>EtF�F�F�FGKGfGiGlGoGrGuGxG{G~G�G�G�G�GHHMHPHyH|H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�HIII	IIIIIIII!I$I'I*I-I0I3I6I9I<I�I�I�I�I�I�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�JYK\KL�L�L�L�L�L�LMNMnM�M�M�MNAN}N�NSOVOYO\O_ObOeOhOkOnOqO�O�O�O�P�P�P'Q�QaRDS�S�T$U�U�V�V�VW>X�X;Y`Y�Y�Y�Z�Z[/[?[f[�[�[�[�[=\�\�\�\�\]�]1^r^�^�^�^_A_p_�_�_`^`�`CaEa�a�a7b�b�bYciclc�c�c�c�cdod�d�dqe�e$fNfdf�f�f�f/gcg�g
hEhth�h1i�i�ij4jRjljoj�jk3kQkxk�k�k�k�k-l0l3l6l9l<l?lBlEl�l�l]m�m�m6n�n<o�o�op1p^p�pqkq�q r�r	s�s�s�sIt�t�t:u
v4vuv�v�v;wlw�w�wx<x�xy�y.z�z\{�{P|�|�|r}�}�}�}C~v~�~�~�~�~_�����Q��H�K�j�������3�j�����k���ǃB�\���τ�[����i��������U���������*�r�ފ]�ȋ3�������3���Ŏ�u����S�����O���ԑ�^���Ԓ/�����ѓ	�e�����Q�u�����������֖�f�����M�������՘��-�c������������Ҝ?���E���;�˟��K���1����N�h������� �:�c�����;�����ܤ�2���ۥ �U�¦ݦM��,�����ר�3�s����V������q�ƫ�d���P�ȭ-���H�t�ɯ�a���ư�
�*�K�����I����E�q����.���������9�d���z�}��������H�����5���������O���!������]�����˾�:�Y�O������}���"�S�V���C�
���	������i���'���*����y���S����8����A�������X���J��������	�K�f��������v���+�.�Q�|������������������������������������������G�k���������������S��������	�,�M�v��������������$�L���
���+���*�p����x����+�����E�����@�����1�����/�Y�\�_�b�e�h�k�n�q�t�w�z�}����������������������������������������������������M�����	�I�h�����S���%�p�����f��������6�{����6�h�����P�
�����4�~�����Z����|����!�$�'�*��`���@�+�����F�I�x���������2��%���3�	;a|��3	y	C
	�X�c
2����(�}���M�&�C�=���/�X����h���HvW F!e"=#T$�$_%�%�&
'R'�'�'�'�'"(`(�()H)p)�)�)�)�)�*,,E,p,�,�,-P-�-�-[.�./~/�/�1�1�3�45F5�586p6�78v8�89W9�98:j:T;�;H<p<�<�<�<A=v=z=~=�=5>q>�>�>�>�?Q@�@AnA�A�A$B`B�BGC�C�CWD�DEjEF�FrG/HI�I(JYJ�J�J0K`K�K�K�KL;L^L�L�L�M�M?N�N�NO)OHO�O�O�O"PaP0Q�Q�RpU�WX2XeX�X�XYY�YZ?ZoZ�Zz[ \�\\]^�^�^C_H_�_�_�_�`�`a$ata�abKblb�b�b�b&cFc]c�c�c�c�c�c�cPd�dRe�efsf�g�hikk"kjkzk�k�k�k[l�lBm�mnvn�nofo�op\p�p�pEqwq6rcr�st�t�t�t1u4u�usv�vTw�wcx�xy�y-zmz{�{�{$|�|�|�|p}�}�}�}(~L~�~�~�~3��O����y�ہ;�����*�5�H�`�������ă��0���C����,�L���@�u���ڇg�����/�^�����ߊ��.������H������|��T�W����\���P���֓r�ڔhashchkisamchkEIJAHEi suuda luua faili '%-.200s' (veakood: %d - %s)Ei suuda luua tabelit '%-.200s' (veakood: %d - %s)Ei suuda luua andmebaasi '%-.192s' (veakood: %d - %s)Ei suuda luua andmebaasi '%-.192s': andmebaas juba eksisteeribEi suuda kustutada andmebaasi '%-.192s': andmebaasi ei eksisteeriViga andmebaasi kustutamisel (ei suuda kustutada faili '%-.192s', veakood: %d - %s)Viga andmebaasi kustutamisel (ei suuda kustutada kataloogi '%-.192s', veakood: %d - %s)Viga '%-.192s' kustutamisel (veakood: %d - %s)Ei suuda lugeda kirjet süsteemsest tabelistEi suuda lugeda '%-.200s' olekut (veakood: %d - %s)Ei suuda identifitseerida jooksvat kataloogi (veakood: %d - %s)Ei suuda lukustada faili (veakood: %d - %s)Ei suuda avada faili '%-.200s' (veakood: %d - %s)Ei suuda leida faili '%-.200s' (veakood: %d - %s)Ei suuda lugeda kataloogi '%-.192s' (veakood: %d - %s)Ei suuda siseneda kataloogi '%-.192s' (veakood: %d - %s)Kirje tabelis '%-.192s' on muutunud viimasest lugemisest saadikKetas täis (%s). Ootame kuni tekib vaba ruumi... (veakood: %d - %s)Ei saa kirjutada, korduv võti tabelis '%-.192s'Viga faili '%-.192s' sulgemisel (veakood: %d - %s)Viga faili '%-.200s' lugemisel (veakood: %d - %s)Viga faili '%-.210s' ümbernimetamisel '%-.210s'-ks (veakood: %d - %s)Viga faili '%-.200s' kirjutamisel (veakood: %d - %s)'%-.192s' on lukustatud muudatuste vastuSorteerimine katkestatudVaade '%-.192s' ei eksisteeri '%-.192s' jaoksTabeli handler tagastas vea %d - '%-.192s'Tabeli '%-.192s' handler ei toeta antud operatsiooniEi suuda leida kirjet '%-.192s'-sVigane informatsioon failis '%-.200s'Tabeli '%-.200s' võtmefail on vigane; proovi seda parandadaTabeli '%-.192s' võtmefail on aegunud; paranda see!Tabel '%-.192s' on ainult lugemiseksMälu  sai otsa. Proovi MySQL uuesti käivitada (puudu jäi %d baiti)Mälu sai sorteerimisel otsa. Suurenda MySQL-i sorteerimispuhvritOotamatu faililõpumärgend faili '%-.192s' lugemisel (veakood: %d - %s)Liiga palju samaaegseid ühendusiMälu sai otsa. Võimalik, et aitab swap-i lisamine või käsu 'ulimit' abil MySQL-le rohkema mälu kasutamise lubamineEi suuda lahendada IP aadressi masina nimeksVäär handshakeLigipääs keelatud kasutajale '%-.48s'@'%-.64s' andmebaasile '%-.192s'Ligipääs keelatud kasutajale '%-.48s'@'%-.64s' (kasutab parooli: %s)Andmebaasi ei ole valitudTundmatu käskTulp '%-.192s' ei saa omada nullväärtustTundmatu andmebaas '%-.192s'Tabel '%-.192s' juba eksisteeribTundmatu tabel '%-.129s'Väli '%-.192s' %-.192s-s ei ole üheneServeri seiskamine käibTundmatu tulp '%-.192s' '%-.192s'-s'%-.192s' puudub GROUP BY klauslisEi saa grupeerida '%-.192s' järgiLauses on korraga nii tulbad kui summeerimisfunktsioonidTulpade arv erineb väärtuste arvustIdentifikaatori '%-.100s' nimi on liiga pikkKattuv tulba nimi '%-.192s'Kattuv võtme nimi '%-.192s'Kattuv väärtus '%-.192s' võtmele %dVigane tulba kirjeldus tulbale '%-.192s'%s '%-.80s' ligidal real %dTühi päringEi ole unikaalne tabel/alias '%-.192s'Vigane vaikeväärtus '%-.192s' jaoksMitut primaarset võtit ei saa ollaLiiga palju võtmeid. Maksimaalselt võib olla %d võtitVõti koosneb liiga paljudest osadest. Maksimaalselt võib olla %d osaVõti on liiga pikk. Maksimaalne võtmepikkus on %dVõtme tulp '%-.192s' puudub tabelisBLOB-tüüpi tulpa '%-.192s' ei saa kasutada võtmenaTulba '%-.192s' pikkus on liiga pikk (maksimaalne pikkus: %lu). Kasuta BLOB väljatüüpiVigane tabelikirjeldus; Tabelis tohib olla üks auto_increment tüüpi tulp ning see peab olema defineeritud võtmena%s: ootab ühendusi
Version: '%s'  socket: '%s'  port: %d%s: MySQL lõpetas
%s: sain signaali %d. Lõpetan!
%s: Lõpp
%s: Sulgen jõuga lõime %ld  kasutaja: '%-.48s'
Ei suuda luua IP socketitTabelil '%-.192s' puuduvad võtmed. Loo tabel uuestiVäljade eraldaja erineb oodatust. Tutvu kasutajajuhendigaBLOB-tüüpi väljade olemasolul ei saa kasutada fikseeritud väljapikkust. Vajalik 'fields terminated by' määrang.Fail '%-.128s' peab asuma andmebaasi kataloogis või olema kõigile loetavFail '%-.200s' juba eksisteeribKirjeid: %ld  Kustutatud: %ld  Vahele jäetud: %ld  Hoiatusi: %ldKirjeid: %ld  Kattuvaid: %ldVigane võtme osa. Kasutatud võtmeosa ei ole string tüüpi, määratud pikkus on pikem kui võtmeosa või tabelihandler ei toeta seda tüüpi võtmeidALTER TABLE kasutades ei saa kustutada kõiki tulpasid. Kustuta tabel DROP TABLE abilEi suuda kustutada '%-.192s'. Kontrolli kas tulp/võti eksisteeribKirjeid: %ld  Kattuvaid: %ld  Hoiatusi: %ldYou can't specify target table '%-.192s' for update in FROM clauseTundmatu lõim: %luEi ole lõime %lu omanikÜhtegi tabelit pole kasutuselLiiga palju string tulbale %-.192s tüübile SETEi suuda luua unikaalset logifaili nime %-.200s.(1-999)
Tabel '%-.192s' on lukustatud READ lukuga ning ei ole muudetavTabel '%-.192s' ei ole lukustatud käsuga LOCK TABLESBLOB-tüüpi tulp '%-.192s' ei saa omada vaikeväärtustVigane andmebaasi nimi '%-.100s'Vigane tabeli nimi '%-.100s'SELECT lause peab läbi vaatama suure hulga kirjeid ja võtaks tõenäoliselt liiga kaua aega. Tasub kontrollida WHERE klauslit ja vajadusel kasutada käsku SET SQL_BIG_SELECTS=1Tundmatu vigaTundmatu protseduur '%-.192s'Vale parameetrite hulk protseduurile '%-.192s'Vigased parameetrid protseduurile '%-.192s'Tundmatu tabel '%-.192s' %-.32s-sTulp '%-.192s' on määratletud topeltVigane grupeerimisfunktsiooni kasutusTabel '%-.192s' kasutab laiendust, mis ei eksisteeri antud MySQL versioonisTabelis peab olema vähemalt üks tulpTabel '%-.192s' on täisVigane kooditabel '%-.64s'Liiga palju tabeleid. MySQL suudab JOINiga ühendada kuni %d tabelitLiiga palju tulpasidLiiga pikk kirje. Kirje maksimumpikkus arvestamata BLOB-tüüpi välju on %ld. Muuda mõned väljad BLOB-tüüpi väljadeksThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if neededRistsõltuvus OUTER JOIN klauslis. Kontrolli oma ON tingimusiTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerEi suuda avada funktsiooni '%-.192s'Ei suuda algväärtustada funktsiooni '%-.192s'; %-.192sTeegi nimes ei tohi olla kataloogiFunktsioon '%-.192s' juba eksisteeribEi suuda avada jagatud teeki '%-.192s' (veakood: %d %-.128s)Ei leia funktsiooni '%-.128s' antud teegisFunktsioon '%-.192s' ei ole defineeritudMasin '%-.255s' on blokeeritud hulgaliste ühendusvigade tõttu. Blokeeringu saab tühistada 'mysqladmin flush-hosts' käsugaMasinal '%-.255s' puudub ligipääs sellele MySQL serverileTe kasutate MySQL-i anonüümse kasutajana, kelledel pole parooli muutmise õigustTeiste paroolide muutmiseks on nõutav tabelite muutmisõigus 'mysql' andmebaasisEi leia vastavat kirjet kasutajate tabelisSobinud kirjeid: %ld  Muudetud: %ld  Hoiatusi: %ldEi suuda luua uut lõime (veakood %d). Kui mälu ei ole otsas, on tõenäoliselt tegemist operatsioonisüsteemispetsiifilise veagaTulpade hulk erineb väärtuste hulgast real %ldEi suuda taasavada tabelit '%-.192s'NULL väärtuse väärkasutusregexp tagastas vea '%-.64s'GROUP tulpade (MIN(),MAX(),COUNT()...) kooskasutamine tavaliste tulpadega ilma GROUP BY klauslita ei ole lubatudSellist õigust ei ole defineeritud kasutajale '%-.48s' masinast '%-.255s'%-.128s käsk ei ole lubatud kasutajale '%-.48s'@'%-.64s' tabelis '%-.64s'%-.16s käsk ei ole lubatud kasutajale '%-.48s'@'%-.64s' tulbale '%-.192s' tabelis '%-.192s'Vigane GRANT/REVOKE käsk. Tutvu kasutajajuhendigaMasina või kasutaja nimi GRANT lauses on liiga pikkTabelit '%-.192s.%-.192s' ei eksisteeriSellist õigust ei ole defineeritud kasutajale '%-.48s' masinast '%-.255s' tabelile '%-.192s'Antud käsk ei ole lubatud käesolevas MySQL versioonisViga SQL süntaksisDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useÜhendus katkestatud %ld andmebaasile: '%-.192s' kasutajale: '%-.48s' (%-.64s)Saabus suurem pakett kui lubatud 'max_allowed_packet' muutujagaViga ühendustoru lugemiselfcntl() tagastas veaPaketid saabusid vales järjekorrasViga andmepaketi lahtipakkimiselViga andmepaketi lugemiselKontrollaja ületamine andmepakettide lugemiselViga andmepaketi kirjutamiselKontrollaja ületamine andmepakettide kirjutamiselTulemus on pikem kui lubatud 'max_allowed_packet' muutujagaValitud tabelitüüp ei toeta BLOB/TEXT tüüpi väljuValitud tabelitüüp ei toeta AUTO_INCREMENT tüüpi väljuINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESVigane tulba nimi '%-.100s'Tabelihandler ei oska indekseerida tulpa '%-.192s'Kõik tabelid MERGE tabeli määratluses ei ole identsedEi suuda kirjutada tabelisse '%-.192s', kuna see rikub ühesuse kitsendustBLOB-tüüpi tulp '%-.192s' on kasutusel võtmes ilma pikkust määratlemataKõik PRIMARY KEY peavad olema määratletud NOT NULL piiranguga; vajadusel kasuta UNIQUE tüüpi võtitTulemis oli rohkem kui üks kirjeAntud tabelitüüp nõuab primaarset võtitAntud MySQL versioon on kompileeritud ilma RAID toetaKatse muuta tabelit turvalises rezhiimis ilma WHERE klauslita. %sVõti '%-.192s' ei eksisteeri tabelis '%-.192s'Ei suuda avada tabelitAntud tabelitüüp ei toeta %s käskeSeda käsku ei saa kasutada transaktsiooni seesViga %d - '%-.192s' käsu COMMIT täitmiselViga %d - '%-.192s' käsu ROLLBACK täitmiselViga %d käsu FLUSH_LOGS täitmiselViga %d käsu CHECKPOINT täitmiselÜhendus katkestatud %u andmebaas: '%-.192s' kasutaja: '%-.48s' masin: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceEi suutnud leida FULLTEXT indeksit, mis kattuks kasutatud tulpadegaEi suuda täita antud käsku kuna on aktiivseid lukke või käimasolev transaktsioonTundmatu süsteemne muutuja '%-.64s'Tabel '%-.192s' on märgitud vigaseks ja tuleb parandadaTabel '%-.192s' on märgitud vigaseks ja viimane (automaatne?) parandus ebaõnnestusHoiatus: mõnesid transaktsioone mittetoetavaid tabeleid ei suudetud tagasi keridaMitme lausendiga transaktsioon nõudis rohkem ruumi kui lubatud 'max_binlog_cache_size' muutujaga. Suurenda muutuja väärtust ja proovi uuestiThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesKasutajal %-.64s on juba rohkem ühendusi kui lubatud 'max_user_connections' muutujagaAinult konstantsed suurused on lubatud SET klauslisKontrollaeg ületatud luku järel ootamisel; Proovi transaktsiooni otsast alataLukkude koguarv ületab lukutabeli suuruseUuenduslukke ei saa kasutada READ UNCOMMITTED transaktsiooni käigusDROP DATABASE ei ole lubatud kui lõim omab globaalset READ lukkuCREATE DATABASE ei ole lubatud kui lõim omab globaalset READ lukkuVigased parameetrid %s-leKasutajal '%-.48s'@'%-.64s' ei ole lubatud luua uusi kasutajaidVigane tabelimääratlus; kõik MERGE tabeli liikmed peavad asuma samas andmebaasisLukustamisel tekkis tupik (deadlock); alusta transaktsiooni otsastAntud tabelitüüp ei toeta FULLTEXT indekseidCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sViga käsu %s täitmisel: %-.128sVigane %s ja %s kasutusTulpade arv kasutatud SELECT lausetes ei kattuEi suuda täita päringut konfliktse luku tõttuTransaktsioone toetavate ning mittetoetavate tabelite kooskasutamine ei ole lubatudMäärangut '%s' on lauses kasutatud topeltUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionKattuv väärtus '%-.64s' võtmele '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTLigipääs keelatud kasutajale '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' ei eksisteeriFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionKattuv väärtus võtmele '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�J�Q��french/errmsg.sysnu�[�����ޙ�O��� S���0m��L��-n��W���Fv��#F��7fz�		.	@	m	�	�	�	�	
(
L
h
�
�
.T����
5Y��
/
i
�
�
#Ae���O��@c��4���5T���
R������>c���+In��8�%��3W����Q�`�-X��%v�L���V � � � !Q!�!�!�!�!"<"b"�"�"�")#f#�#�#$h$�$%�%�%&D&�&�&','w'�'�'�'�'Z(�(�(�()G)t)�))*M*�*�*\+�+P,�,-�-.].�.�./R/�/0(0q0�041q1�1�1L2p2�2�2�23\3�3�34Y4�4�45T5�5�5�5�5J6�6�6�67;7\7�7�7�78'8S8}8�8#9Q9�9�9�9/:G:�:�:�:;];�;�;<*<k<�<�<$=Q=�=�=r>�>P?�?X@�@�@�@AGAcA�A�A>BrB�BCJCvC�CDbD�D�D�DE*EnE�E�E�E�EF%FCFWFrF�F�F�F!G�G�GHXHpH�H�H�H�HII2IJInI�I�I�I�I�IJ1JaJ�J�J�JKKK�K�K�KFL}L�L�L�LMDMxM�MFN�NOLO~O�O�O�O
P+PXPfP�P�PQ2QxQ�Q�Q�QRHRZRwR�R�R�RSVShS�S�S�S6TYToT�T�T�T/UsU�U�U�UVkV�VW5W�W�W�WX1XvX�X�XYOY|Y�YZPZ[�[f\�\]R]�]�]^X^�^�^)_�_�_M`�`�`�`va�a�a�abBb�bc�cd#d�d�d9eue�e
fEf�f�fVg�g�g?hoh�h�h iTi�i�i�i�i�i8jrj�j�jkwk�kl`l�lm8mmm�m�m6n�n�n
o;o�o�o�oBpzp�p�p4qtq�qr8rjr�rsFs�s�s�s t{t�t u^u�u�u�uv:v�v�v6wpw�w�w�wxCxWxix�x�xDyXy�y�yFzez�z�z�z�z{?{|{�{�{|L|x|�|�|�|}p}�}�}B~�~3��6�]�n�����	�r���́���J�k����4�f���4�w����0�c������І�f�v�������އ�6�l���ۈ�X��������z���Ҋ�4�}���ً
�"�E�x���$�K����(�[�����.�7�=�G�T�^�f���ď��1�Z�����ѐ�7�]�v�ԑ%�N�����͒��<���ѓ
���<����>���F�ØH�����P���=�N���� �J�����ߝ>���ܞ�J�����ݟ(���Ӡ�7�n����6�~���T���y��>�y����%�;�W�*��ߨ����@������l���Ү5�m����T���ư�/�Q���f�����R���:�y���״��9�y�̵���D�G����߷�|��K���Һ!���ܻ���μ���=���6����G����M������������o���������?�~���8�O�f�
�����H�x������!�>�b��������B�����@������z�����$�����[����k���������	�T�����'������:�z������U�����
�+�S�-�W����k����S�����#�m���(�t�������)������_����������E����������,�j����W����h�����'�Q�����"�5�T�����m������b���0�s�����@��������-�t����d�������
�:�f��������(�S����S��%�]������������\�p����8�e����+�p��(�|���"����	������A��"��4�\�
S��i��"l��<|�P	�	
�
�
�
"E_���=j�2
_
�
�
uQo�#i��1s�'B�X��#f��L�Lp���"_v���e�fi���'}���Uw�f�*|�
�, � (!G!�!�!"Z"p"�"�"�"�#�#N$z$�$%D%Z%q%�%�%&&+&A&f&�&�&�&�'+(Z(�()�)1*w*�*+�+i,�,-\-�-�-.D.n.�.�.�./L/m/�/0:0w0�0-1_1�1m2�2�2�23$3S3�3�34F4q4�4�4K5�5�56P6�67{7�78o8�8�89-9h9�9�9:-:C:P:V:�:�:;`;�;<;<�<�<+=W=�=�=R>�>�>h?�?�@-AeA�A�A�AJB�B�B�BIC�C,D�D�D�DLE�E�E+FeF�FGgG�G�GHTH~H�H'I�I�I�IJbJ�J�J	K=K�K�K'LPL�L�L�L2M�M�MNoNOQO�O�O�O<PxP�P:QhQ�QHRfR�RS�S�T'U�U�V�V�VW=WOWhW�W�W�WX9XWXqX�X�XYIYvY�Y�Y1ZhZ�Z�Za[�[0\j\�\�\N]w]�]V^�^B_v_�_�_`A`u`�`�`-aka�a�ablb�b�bc�c�cdVd�d�de,eRe�e�e8frf�fg_g�g�gmh/ii�i	j'j9k�k%lYl�l�l_m�mn�no�o�oEp�p�pq7q�q�q�rbst�tGu�v�vwgw�w3x`x�xy;yfy�y�y?z�z�z1{�{!|i|�|�|I}�}�}~}~B��y�݀g��5���˂�}���҃
�C�u�Ȅ>����M����&�H�}������߉׊����ߍ,�g����\���ُ�E�{���(�u��������{���7�t�������{�˕;�}����+���Η-�o����1�S������ �u������o���f������H���̞'�J���џ�N�������6�v����n���آ�h���ѣ��9����'����S����A�p��'�b�����W���ө�:�~��|�˫-�^���	�R���֭��5������_��(�U�������l�β(����(�ڴH����=�����S���Ƿ�E�o�ٸ_�Ź�H���
�ϻ|�ԽL����(�V�-���	���U���N����x������A���E�t�>�w�������s�-����i����������b���M�|����4�c���|�"�N���N���[���e����\�H�t������q�����j����U����>�������J���M���j���y�����n���H���������J���C���7�d�����K���0���'����f������>�u�����Y���T�����t���l�o���
�U���(���h��@���D���"����)��,����3����"��s�$b��J�0S���	�,P{�,Uw�r��	w	�	k
�
w�n��4
�
�
��G�D�A!`���(:���M��7Q�)Q��5\��� Hr���H�_���	7e���<@v��(c��L���9a���= Y � � � !>!�!�!,"k"�"D#�#�$�$�$&%�%�%%&k&'['�'(B(t(�(�(�()D)�)**�*)+�+�+q,�,�,-P-�-�-..S.�.�.,/b/�/�/0$0R0[0f0�0�0(1|1�1�122!2,2s2�2�23!333X3{3�3�304f4�4�45c5�5�5�5�5`6�6�6727�7�7	9Y9�9%:m:G;�;\<�<�<�<�<%=M=i=�=�=>?Z?|?�?@:@�@�@�@4AcA�A�AQBRC�C�C�CWD�D�DE,EYE�EF?F�F�FGXG�G�G�G
H2H]H~H�HI#IbI�I�IJ9JnJ�J�JKK$K4KRK�KM"MYM�M{NOO�O�O�OPJP|P�P�PQ1QSQtQ�Q�QR0RCRZRuR�R�R$S[S�S�ST#T>TnT�T�T�TU;UhU�U�U�UVAVjV�V�VW6WWWkW�W�WXHX�X�X"YUYY�Y�YZ#ZJZpZ�Z�Z�Z
[^[�[�[H\�\]F]]�]=^�^=_w_�_y`�`'a�a�c�c!d�d6ele�e�efTf�f�f1gXg�gh'h�hHi�ij7j�j�jgk�k�k�k4lKlsl�l�lm6mem�m�mAn�n�n�no�o�oMp�pqkq�q�q�qrNr�r�r+sss�sLtwt�t&uRu�u�u2vrv�v�vw�w�xsyWz�z�z�z{.{E{�{�{�{�{:|m|�|}�}~�~�~
2s������6�����ā�݂���B�t���*�`���܅�t���I�w����K���׈(�|���щ�ފQ�����Ƌ�E�����]�|���$�J�]���֎�8�b����+�Z����3�y����:���i���\���Ĕ��$�`�}�����N�j���ߖ�v���ŗ�8�`�������T������<�W�������n�)�G�g���ל7���ɞ�f����
�h������!��T�z���ţ���q��������ǧ��A���Ъ4�k���ī߫��Ь
�L�z�%�;�������S�r��O�9�k���D��/���߳o��D�\�x�Ƶ����ŷ��0���ڸ���4�v���Ǻ,���������.�`�������H�m�Ƚ/�^���Ǿ�O����i�����G�r�����V������F����L������Q��������~����`���@������������<�p��������b���4������o������6�b�����-�b�y�������>�f��������8�l�����5�`����������3�^�������%�P�w��������;�X���������������-���������%�U�����1�P�m��������D�k�������)�@�W��������8�e��������>�z�����7�w�����;�]�������C�������
�S�����j�����0�Z�s���������y����5�����
�������I�r����z��������u�����-�`��_���D������/�v�����'�^������G�������K������_����?�^�������D����X�y��:��_�g�r������_�~�	�x����R����#�<�u����n�!���������/W�#Cd���%�+��)Wh�������	�	
U
�
�
��;y�
[
h
�
�
�
��
��U���;r����'�+\��6:m��u�W��'q��9}��j��+q��>k���H��G����/p��� l � � J!t!�!�!"?"g"�"#;#^#�#�#�#-$|$�$�$%%^%�%e&�&D'�',(K(a(�(�(X)�)0*s*�*+Q+y+�+,7,�,-�-K.�.8/_/}/�/�/�/�/�/�/�/�/ 0#060�0�011D1e1�1�1�1�1O2�2"3�3�34-4K4�4�4585m5�56`6�6�67O7�7 8�8�9:A:v:�:�;�;�;1<U<�<�<�<�<=S=�=�=�=�= >H>c>�>�>�>�>�>�>#?Z?�?�?�?�?(@Q@�@�@�@�@!A[A�A�A�AB(BMBtB�B�B"CnC�C�CDJD�D�DE4ENEqE�E�EF;FxF�F�F	G4G`GzG�G�G0H�H�H�H�H#IrI�I�IJ+JXJ�J�J�J	K#K;KVKYK�K]L.M�M�M�MNbN�N�N�NOKO�O�O�OP\P�P�P�PQ.QNQnQ�Q�Q�QR;RYRtR�R�RS9S�S�S�S�S�S�ST-TpT�T�T�TcU�UVUVyV�V�V�V�V�V�VuW�W�WXTXmYZIZ�Z�[�\�\=][]�]�]^1^@^p^�^�^�^-_^_�_�_�_`V`�`�`�`�`#aha�a�aOb�b�b�b�b�b�bcIchc�c�cd/dqd�d�d eSeye�e�efSftf�f�f�fg9gag�g�g"hHhoh�h�h�h�hi1iKipi�i�ijEjcj�j�j�jk8krk�kll>l�l�mn]n�n�n�n�n.o�o�opRp�p�p
q
qQqqq�q�q�q�r�s�s�stkt�t�t
u8uWuwu�u�u�uv'vCvav�v�vwwBw^w�w�wxEx�x�x:y�y@z�z�z�{�{L|�|x}�}+~�~�~�~!���+�L�������'�u������K�X�׃�L�������E�v����d����x��\�����W���ډ;��������I�Ì8������؎&�l��/�W���{���Ñ�'�N���ג�H���ȓ�-�k��6�h��������;�^�����)�T����'�X���כ�O�������i�ܞP�П"�Q���&�š!���C�٣�]��#�Y���Ȧ���(���8����m���Ϊ�+���߫D����9����;����j�ȯ:���I�����ѱ��H�i���۲Q�ǳ	�U���Ǵ�j�ĵ��S����Z����������������P���!�e�нB�����c�̿4��&�d����P�����4�r���)�����i����`�����G�����n���}���(�{���.�X��������f���������+�X���L�����
�>�x������H������7�i���(�c����O������������/�����������Y���2���<����E�z���-�w���	�R����c����m����P��c������:�d�����'�����U�����b���.�a������P�����4�����K�������)�n���������
�'�N�k��������P�~������[�s������8�i������w����!�S�����Z������ �-�k����
�0�]������G�J�|�����.�X�������L����F���8�r�������F������@CFILORUX[^adgjmpsvy|���������������������������������NQTWZ]`cfilorux{~������������������������������ #&),/258;>ADGJMPSVY\_behknqtwz}��������������������������������������GJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORU��Ny�������!Dl�	 	u	�	�	S
�
G��^���
-_��"%(+_behknqtwz}�����������������������������wz}��������������������������������S������������������������������ #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������!$'*-0369<?BEHKNQTWZ]`cfilorux{~���������������������������������WZ]����������� #&)��\�V��1r���%ps����2q�:g���;q�A � � �!�!k")#,#/#v#�#.$\$_$b$y$|$$�$�$�$�$8%�%�%>&h&�&'8'o'�'�'�',(�(�(�(/)*}*�*T+�+�+�+�+�+�+�+�+�+,,,,,,,,,, ,#,&,),,,/,2,5,8,;,>,A,D,G,J,M,P,S,V,Y,\,_,b,e,h,k,n,q,t,w,z,},�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---
-
------->-A-D-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-.......... .#.&.).,./.2.5.8.;.>.A.D.G.J.M.P.S.V.Y.\._.b.e.h.k.n.q.t.w.z.}.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.///
/
///////"/%/(/+/./1/4/7/:/=/@/C/F/I/L/O/R/U/X/[/^/a/d/g/j/m/p/s/v/y/|//�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�0�01s1�1232�2�2�23O3�3�3�3�34?4�4�455D5e5�5�5�5666a6�6�67.7�7�7�7�7858�8�89[9z9�9:`:�:<;�;�;�;�;</<w<�</=^=�=�=�=h>�>�>�>�>�>�>�>�>�>???�?�?�?|@@�@�@�@BAmA�A
B�CAD^D�D�D�E�F;GVG�G�G�G�G
H3I�I�J�JK2KsK�K�K�K�K�K�K�K�K�K�K�KLILLLjLmL�L�L�L�L�L�LMMM
M
MMMMMMM"M%MUMXM[M^MaMdMgMjMmMpMsMvMyM|MM�M�M�M�M�M�MNN+NNNQNOOO"O%O(O+O.O1O4O7O:O=O@OCOFOIOLO�O�OtPQQQQQJQtQ�Q�Q�QR&RkR�R�RS�S�S�S�S�S�S�S�S�S�S�S�S8T;TGUJUMU|UV�V�W�W�XyY�Y�Z3[H[p[�\
]�]�]�]^�^%_p_�_�_�_�_`'`C`�`�`a=aKalab�b�b�bc>cgc�c�c�c5d]d�dAe�e�e�eDf�f�fNg�g�g�g�gh3hPhth�h�h�h�i
jyj�j�j�jkCk�k�kl_l�l�lBm�m�mAnfn�n�n�n�noUo�o�o�o�oppNp�p�p�p�p�p�p�p�p�pqQq�q�q#r�rs�s�s tZt�t�t�tdu�uvuvw^w�wxKx�x�x+y�ybz�z�z{1{�{�{%|M|n|�|}W}~�~
�2����T�ǁ܁��F���˂��:�=������5�W�r���]�����������S�����
�O����������$�]�����X�����7�s��`����i�ڍ�H��ǎ3�������j�ڑ;���ے�j�ʓ�7��������ݕ)�s����)�����&�^���
�D�n���ʙٙ=�i�ޚ���+�k�����I�j���ל��*�R�����
�Q��
�`��'���������� �Q��������H���������u�����է
���ب��1�q�����0�u����2���X���ج
�,�i���ȭ�Y�����l�Ư�`���԰D������@�r���ɳ�k�����@�_�����Q����?���Ʒ�?�������>�U�����
�ϻһջػ
�>����R������F��r�����v���Z�����	� �e���������(�K���3�w���������b�'�^����e���7�|�����W���S�����X����U�����-�K������/�e���^��������)�e���T������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�������@�C�F�I�L�O������9�[�^��������L�t���G�J�!�y�����_����������t���d�-�����A�����<�����8�����,���������������������������������������������������������������������Z������^�������@�����z���&�)������O�m�����=�o����������_������������`���h�v�y�|�����P��/]����(q�J�8��4z�;j��	
^
�
�
i���
�
�^�����@h�}��l�r
)a�	{���;>���C � R!�!l"�"�"#R#�#�#�$�%�&�'�()�)J*+_+�+�+,*,D,w,�,0-c-�-�-�-.(.I./V0s0�0�01G1j1�1�1T2�23r3�3&4
656I8�8m9�9
:�:�:�;o<�< =a=�=O>�>�>�?3@�@�@�@A,A�A�A�A�A�A�B�B"C%C(CD�D;EiE�E�E1FyF�FG�G	HDH�HIhI�IeJK�K�L\M1N}N�NOCO�O�O�OP8P]P�P�P�P Q�QBR�R�RSXS~S�S�ST1TwT�T�UEVW�Y-\V\�\�\�\N]�]�][^�^�^/_�_u`a�aWb�b2c�c�cdd@deeUeye�efff�f�f�fg?g{g�g�g�g�ghh:hMh�hSi�ijYj�j�k+mpmUogowo�o�o�opJp�p#q�qrpr�r#sns�stnt�t�tAu�u�u�v�v�wfx�x�xKy�y�yFz�zI{�{:|�|}Z}�}�~�~q��y���P�Ł��+�T�}�����!�M����8����n�΅0���ކ?�]��������ه����<�j�������6��������ʋ��/���C��U�����ڎ�4����ؐ�5���֑n��ѓA�����	�]������N�+�ǘ/�hashchkisamchkNONOUINe peut créer le fichier '%-.200s' (Errcode: %d - %s)Ne peut créer la table '%-.200s' (Errcode: %d - %s)Ne peut créer la base '%-.192s' (Erreur %d - %s)Ne peut créer la base '%-.192s'; elle existe déjàNe peut effacer la base '%-.192s'; elle n'existe pasNe peut effacer la base '%-.192s' (erreur %d - %s)Erreur en effaçant la base (rmdir '%-.192s', erreur %d - %s)Erreur en effaçant '%-.192s' (Errcode: %d - %s)Ne peut lire un enregistrement de la table 'system'Ne peut obtenir le status de '%-.200s' (Errcode: %d - %s)Ne peut obtenir le répertoire de travail (Errcode: %d - %s)Ne peut verrouiller le fichier (Errcode: %d - %s)Ne peut ouvrir le fichier: '%-.200s' (Errcode: %d - %s)Ne peut trouver le fichier: '%-.200s' (Errcode: %d - %s)Ne peut lire le répertoire de '%-.192s' (Errcode: %d - %s)Ne peut changer le répertoire pour '%-.192s' (Errcode: %d - %s)Enregistrement modifié depuis sa dernière lecture dans la table '%-.192s'Disque plein (%s). J'attend que quelqu'un libère de l'espace... (Errcode: %d - %s)Ecriture impossible, doublon dans une clé de la table '%-.192s'Erreur a la fermeture de '%-.192s' (Errcode: %d - %s)Erreur en lecture du fichier '%-.200s' (Errcode: %d - %s)Erreur en renommant '%-.210s' en '%-.210s' (Errcode: %d - %s)Erreur d'écriture du fichier '%-.200s' (Errcode: %d - %s)'%-.192s' est verrouillé contre les modificationsTri alphabétique abandonnéLa vue (View) '%-.192s' n'existe pas pour '%-.192s'Reçu l'erreur %d - '%-.192s' du handler de la tableLe handler de la table '%-.192s' n'a pas cette optionNe peut trouver l'enregistrement dans '%-.192s'Information erronnée dans le fichier: '%-.200s'Index corrompu dans la table: '%-.200s'; essayez de le réparerVieux fichier d'index pour la table '%-.192s'; réparez le!'%-.192s' est en lecture seulementManque de mémoire. Redémarrez le démon et ré-essayez (%d octets nécessaires)Manque de mémoire pour le tri. Augmentez-la.Fin de fichier inattendue en lisant '%-.192s' (Errcode: %d - %s)Trop de connexionsManque de 'threads'/mémoireNe peut obtenir de hostname pour votre adresseMauvais 'handshake'Accès refusé pour l'utilisateur: '%-.48s'@'@%-.64s'. Base '%-.192s'Accès refusé pour l'utilisateur: '%-.48s'@'@%-.64s' (mot de passe: %s)Aucune base n'a été sélectionnéeCommande inconnueLe champ '%-.192s' ne peut être vide (null)Base '%-.192s' inconnueLa table '%-.192s' existe déjàTable '%-.129s' inconnueChamp: '%-.192s' dans %-.192s est ambiguArrêt du serveur en coursChamp '%-.192s' inconnu dans %-.192s'%-.192s' n'est pas dans 'group by'Ne peut regrouper '%-.192s'Vous demandez la fonction sum() et des champs dans la même commandeColumn count doesn't match value countLe nom de l'identificateur '%-.100s' est trop longNom du champ '%-.192s' déjà utiliséNom de clef '%-.192s' déjà utiliséDuplicata du champ '%-.192s' pour la clef %dMauvais paramètre de champ pour le champ '%-.192s'%s près de '%-.80s' à la ligne %dQuery est videTable/alias: '%-.192s' non uniqueValeur par défaut invalide pour '%-.192s'Plusieurs clefs primaires définiesTrop de clefs sont définies. Maximum de %d clefs allouéTrop de parties specifiées dans la clef. Maximum de %d partiesLa clé est trop longue. Longueur maximale: %dLa clé '%-.192s' n'existe pas dans la tableChamp BLOB '%-.192s' ne peut être utilisé dans une cléChamp '%-.192s' trop long (max = %lu). Utilisez un BLOBUn seul champ automatique est permis et il doit être indexé%s: Prêt pour des connexions
Version: '%s'  socket: '%s'  port: %d%s: Arrêt normal du serveur
%s: Reçu le signal %d. Abandonne!
%s: Arrêt du serveur terminé
%s: Arrêt forcé de la tâche (thread) %ld  utilisateur: '%-.48s'
Ne peut créer la connexion IP (socket)La table '%-.192s' n'a pas d'index comme celle utilisée dans CREATE INDEX. Recréez la tableSéparateur de champs inconnu.  Vérifiez dans le manuelVous ne pouvez utiliser des lignes de longueur fixe avec des BLOBs. Utiliser 'fields terminated by'.Le fichier '%-.128s' doit être dans le répertoire de la base et lisible par tousLe fichier '%-.200s' existe déjàEnregistrements: %ld  Effacés: %ld  Non traités: %ld  Avertissements: %ldEnregistrements: %ld  Doublons: %ldMauvaise sous-clef. Ce n'est pas un 'string' ou la longueur dépasse celle définie dans la clefVous ne pouvez effacer tous les champs avec ALTER TABLE. Utilisez DROP TABLENe peut effacer (DROP) '%-.192s'. Vérifiez s'il existeEnregistrements: %ld  Doublons: %ld  Avertissements: %ldYou can't specify target table '%-.192s' for update in FROM clauseNuméro de tâche inconnu: %luVous n'êtes pas propriétaire de la tâche no: %luAucune table utiliséeTrop de chaînes dans la colonne %-.192s avec SETNe peut générer un unique nom de journal %-.200s.(1-999)
Table '%-.192s' verrouillée lecture (READ): modification impossibleTable '%-.192s' non verrouillée: utilisez LOCK TABLESBLOB '%-.192s' ne peut avoir de valeur par défautNom de base de donnée illégal: '%-.100s'Nom de table illégal: '%-.100s'SELECT va devoir examiner beaucoup d'enregistrements ce qui va prendre du temps. Vérifiez la clause WHERE et utilisez SET SQL_BIG_SELECTS=1 si SELECT se passe bienErreur inconnueProcédure %-.192s inconnueMauvais nombre de paramètres pour la procedure %-.192sParamètre erroné pour la procedure %-.192sTable inconnue '%-.192s' dans %-.32sChamp '%-.192s' spécifié deux foisUtilisation invalide de la clause GROUPTable '%-.192s' : utilise une extension invalide pour cette version de MySQLUne table doit comporter au moins une colonneLa table '%-.192s' est pleineJeu de caractères inconnu: '%-.64s'Trop de tables. MySQL ne peut utiliser que %d tables dans un JOINTrop de champsLigne trop grande. Le taille maximale d'une ligne, sauf les BLOBs, est %ld. Changez le type de quelques colonnes en BLOBDébordement de la pile des tâches (Thread stack). Utilisées: %ld pour une pile de %ld.  Essayez 'mysqld --thread_stack=#' pour indiquer une plus grande valeurDépendance croisée dans une clause OUTER JOIN. Vérifiez la condition ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerImposible de charger la fonction '%-.192s'Impossible d'initialiser la fonction '%-.192s'; %-.192sChemin interdit pour les bibliothèques partagéesLa fonction '%-.192s' existe déjàImpossible d'ouvrir la bibliothèque partagée '%-.192s' (errno: %d %-.128s)Impossible de trouver la fonction '%-.128s' dans la bibliothèqueLa fonction '%-.192s' n'est pas définieL'hôte '%-.255s' est bloqué à cause d'un trop grand nombre d'erreur de connexion. Débloquer le par 'mysqladmin flush-hosts'Le hôte '%-.255s' n'est pas authorisé à se connecter à ce serveur MySQLVous utilisez un utilisateur anonyme et les utilisateurs anonymes ne sont pas autorisés à changer les mots de passeVous devez avoir le privilège update sur les tables de la base de donnée mysql pour pouvoir changer les mots de passe des autresImpossible de trouver un enregistrement correspondant dans la table userEnregistrements correspondants: %ld  Modifiés: %ld  Warnings: %ldImpossible de créer une nouvelle tâche (errno %d). S'il reste de la mémoire libre, consultez le manual pour trouver un éventuel bug dépendant de l'OSColumn count doesn't match value count at row %ldImpossible de réouvrir la table: '%-.192sUtilisation incorrecte de la valeur NULLErreur '%-.64s' provenant de regexpMélanger les colonnes GROUP (MIN(),MAX(),COUNT()...) avec des colonnes normales est interdit s'il n'y a pas de clause GROUP BYUn tel droit n'est pas défini pour l'utilisateur '%-.48s' sur l'hôte '%-.255s'La commande '%-.128s' est interdite à l'utilisateur: '%-.48s'@'@%-.64s' sur la table '%-.64s'La commande '%-.16s' est interdite à l'utilisateur: '%-.48s'@'@%-.64s' sur la colonne '%-.192s' de la table '%-.192s'Commande GRANT/REVOKE incorrecte. Consultez le manuel.L'hôte ou l'utilisateur donné en argument à GRANT est trop longLa table '%-.192s.%-.192s' n'existe pasUn tel droit n'est pas défini pour l'utilisateur '%-.48s' sur l'hôte '%-.255s' sur la table '%-.192s'Cette commande n'existe pas dans cette version de MySQLErreur de syntaxeDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useConnection %ld avortée vers la bd: '%-.192s' utilisateur: '%-.48s' (%-.64s)Paquet plus grand que 'max_allowed_packet' reçuErreur de lecture reçue du pipe de connexionErreur reçue de fcntl() Paquets reçus dans le désordreImpossible de décompresser le paquet reçuErreur de lecture des paquets reçusTimeout en lecture des paquets reçusErreur d'écriture des paquets envoyésTimeout d'écriture des paquets envoyésLa chaîne résultat est plus grande que 'max_allowed_packet'Ce type de table ne supporte pas les colonnes BLOB/TEXTCe type de table ne supporte pas les colonnes AUTO_INCREMENTINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESNom de colonne '%-.100s' incorrectLe handler de la table ne peut indexé la colonne '%-.192s'Toutes les tables de la table de type MERGE n'ont pas la même définitionÉcriture impossible à cause d'un index UNIQUE sur la table '%-.192s'La colonne '%-.192s' de type BLOB est utilisée dans une définition d'index sans longueur d'indexToutes les parties d'un index PRIMARY KEY doivent être NOT NULL; Si vous avez besoin d'un NULL dans l'index, utilisez un index UNIQUELe résultat contient plus d'un enregistrementCe type de table nécessite une clé primaire (PRIMARY KEY)Cette version de MySQL n'est pas compilée avec le support RAIDVous êtes en mode 'safe update' et vous essayez de faire un UPDATE sans clause WHERE utilisant un index. %sL'index '%-.192s' n'existe pas sur la table '%-.192s'Impossible d'ouvrir la tableCe type de table ne supporte pas les %sVous n'êtes pas autorisé à exécute cette commande dans une transactionErreur %d - '%-.192s' lors du COMMITErreur %d - '%-.192s' lors du ROLLBACKErreur %d lors du FLUSH_LOGSErreur %d lors du CHECKPOINTConnection %u avortée vers la bd: '%-.192s' utilisateur: '%-.48s' hôte: '%-.255s' (%-.64s)Ce type de table ne supporte pas les copies binairesBinlog closed, cannot RESET SOURCELa reconstruction de l'index de la table copiée '%-.192s' a échouéErreur reçue du maître: '%-.64s'Erreur de lecture réseau reçue du maîtreErreur d'écriture réseau reçue du maîtreImpossible de trouver un index FULLTEXT correspondant à cette liste de colonnesImpossible d'exécuter la commande car vous avez des tables verrouillées ou une transaction activeVariable système '%-.64s' inconnueLa table '%-.192s' est marquée 'crashed' et devrait être réparéeLa table '%-.192s' est marquée 'crashed' et le dernier 'repair' a échouéAttention: certaines tables ne supportant pas les transactions ont été changées et elles ne pourront pas être restituéesCette transaction à commandes multiples nécessite plus de 'max_binlog_cache_size' octets de stockage, augmentez cette variable de mysqld et réessayezCette opération ne peut être réalisée avec un esclave actif, faites STOP SLAVE d'abordCette opération nécessite un esclave actif, configurez les esclaves et faites START SLAVELe server n'est pas configuré comme un esclave, changez le fichier de configuration ou utilisez CHANGE MASTER TOImpossible d'initialiser les structures d'information de maître, vous trouverez des messages d'erreur supplémentaires dans le journal des erreurs de MySQLImpossible de créer une tâche esclave, vérifiez les ressources systèmeL'utilisateur %-.64s possède déjà plus de 'max_user_connections' connexions activesSeules les expressions constantes sont autorisées avec SETTimeout sur l'obtention du verrouLe nombre total de verrou dépasse la taille de la table des verrousUn verrou en update ne peut être acquit pendant une transaction READ UNCOMMITTEDDROP DATABASE n'est pas autorisée pendant qu'une tâche possède un verrou global en lectureCREATE DATABASE n'est pas autorisée pendant qu'une tâche possède un verrou global en lectureMauvais arguments à %s'%-.48s'@'%-.64s' n'est pas autorisé à créer de nouveaux utilisateursDéfinition de table incorrecte; toutes les tables MERGE doivent être dans la même base de donnéeDeadlock découvert en essayant d'obtenir les verrous : essayez de redémarrer la transactionLe type de table utilisé ne supporte pas les index FULLTEXTImpossible d'ajouter des contraintes d'index externeImpossible d'ajouter un enregistrement fils : une constrainte externe l'empècheImpossible de supprimer un enregistrement père : une constrainte externe l'empècheError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDuplicata du champ '%-.64s' pour la clef '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAccès refusé pour l'utilisateur: '%-.48s'@'@%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setLa partition '%-.64s' n'existe pasFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDuplicata du champ pour la clef '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\!�F�++german/errmsg.sysnu�[�������N��H�Am��K��G��I���:b���5o��/r�x	�	�	
g
�
�
�
�
�
Hi���D���
0
Z
v
�
�
�
R��j�@����5��W��0�b��B\���"s��29g���n���'7�m�@d���(\��F�+d�= � � � � �!�!,"�"�"%#O#�#�#F$�$�$�$8%_%}%�%�%&H&y&�&�&6'z'�'�';(z(�(M)�)*V*�*A++�+�+,8,\,u,�,�,>-u-�-�-�-.Y.�.�.1/�/�/�01�1�1p2�23<3�34^4�455b5�526q6�67�7�7828S8�8�8V9�9�9:y:�:�:2;^;�;�;�;8<�<�<�<=C=z=�=�=>A>o>�>�>R?�?@F@[@z@A"A�A�A�AB^B�B�BCCC�C�C9D�D�D=EeE/F�FGnGBH�H�H�H'I`I�IJ'JRJ�J�JKK|K�K7LjL�L�LM-M`M�M�MN[NsN�N�N�N�N�N$OPO�O�O�O`P�PQHQcQ�Q�Q�Q�QR#R>R]R�R�R�R�RS!S<SbS�STITqT�T�TUNU�U�U*VIVqV�V�VWRW�WXnX�XKY�Y�Y�Y�Y7Z\Z�Z�Z�Z[K[z[�[�[;\c\�\�\�\]K]r]�]�]^5^z^�^�^-_\_~_�_�_`^`�`�`�`aXa�abub�b
cNc�c�c�cddd�d�de>e}e�ef�f�gahi3i�i�i,j{j�jklk�kl}l�l2m�m�mKntn�no2oZoptpEq�q�q�r�r<s~s�sSt�tuKu�uNvqv�vwcw�w�wxUx�x�x�x�x0ydy�y�yz�z�z@{�{�{K|�|�|9}�}�}L~�~�~���L���؀!�z���	�y����a����9�b����|���L����9�}���ڇ@�҈�h���ɉ��K�i���݊:������D�Ԍ��@�\�����ٍ�[������Q�����ӏ�L����3���S�ǒ3���֓�K�]�����������.�V���Ė ���͗�U���H���Ǚ�@���%���U���˜����A�k���ڝ%�[����$�b���۟7�c���Ơ�Y���ۡ��P����h����K���Ƥ��3�������åҥܥ��P�z���Φ��5�g�����I�e�Ө;�e���ة��0�z�̪"�U����2����������9�ױ5����������0�k���ߴ�8����5�������K����A�����ܸ�\����,�ƺh��W����.�c�����ɽ����Q�$������x��������D�����,�����
�B�~�����������(�e����������"�S�z�����L�����������_�������D�����L�����=���������r���]����l���	�c���|���������+�M�����������:�x����"���J����C���������	�-�J�|�������
�L����t�����E�p���
�����x���!�����������&�q����D����8�W��������r�����'�H�p�J�v���"�����9�r����B�����G��������H����*�~���
�4���d���'���K�����;�v�%W�$g��,bu����-H�p�����	D	m	�	
P
�
�
�
$Jz���Ah��
�
e���5�7���)x��k�3h��b�
I����b�"t*�J��P��5b�� | � 2!�!�!T"�"#>#b#�#�#�#�#�#P$}$�$�$r%�%�%;&_&�&]'�'�'1(c(�(�(!)q)�)*g*�*+_+�+�++,c,�,�,--Z-�-�-N.�.�.�.�.//b/�/�/�/�/-0�01V1�1�2�2�263g3�3�344�4�4�4�5=6j6�6�6J7�7l89h9�9#:5:\:�:�:�:�:;�;<�<�<=Z=�=�=�=�= >K>N>k>�>�>�>?%?�?k@�@ADA�AqB�BCOC�C�D�DKE�EF#FRF�F�F�FG5GWG�G�G�G]HzH�H�HmI�I$J�J�J�JKHKdK�K�K)L[L�L�L�L;M�M�MNRN�NOAO�OP]P�P�PQ@QmQ�Q�QRBRmR�R�R�R�RSPS�S�SHT{T�T�TkU�U�U'V�V�V'W�WX�XmY�Y�Y�Y;Z�Z�Z	[?[�[\l\�\]]�]�]$^k^�^_B_�_�_'`\`�`�`;aga�a�a#b]b�b�b!cIc}c�cdgd�d�d�d#eke�efWf�fRg�g�g�g/huh�h
isi�ij�j�j�jLk'l�l`m�m�n�n-oMovo�o�o�op3pRprp�p�p�p qIq�q�q�q"rjr�r�r4s�s�sit�t�tu�u�u�u�v�v{w�w�wx=xzx�x	y7yfy�y�yzUz�z�z{L{�{1|?|�|�|)}E}e}�}�}7~q~�~�~T�����h�����B�`�r���^���̈́����R���=��)�~����D�p�҉2�؊��U�(���ێ�J����l����H�t���ّ0�x����j��Z����3�������U���{��N������)�n�ߚ�;���Л�C�|����w�̝*����&�_�������>�Π��ԣ��e����<���ͧ�:�~���ߨa����M���/���8�p���߬�3����t���ٮ�d����f����I�j���ı�-�Y���M���/����������D���ʶ�`�����
�:���ɸ��"�%�o�����:���Ⱥ�'���ƻ
�1�r�ż�`�Ƚ���߾X�z���9�`����4������V�s���,����f�����B������7�n���X�����'�a�������(�,����a���<�a������%�v���3������@�~��������I�����F����
����� �a���f���B����������>������K�z���~���w�����	�����f�6�X������%�X�������������:�m�������[������������V������������J�����
���,�H����D�w��8�������	�������5���0�������*�������|�p�� �i�`�?��
Pw���1	�	�	
�
1���C��a
�
�	y�}�[�b
e�l�[��]��(��i���B�Ge���Me���G � � � ;!�!$"�"�"X#�#�#H$�$�$*%m%�%
&�&&'G'�'�'}(�(z)Z*�*�*�*+R+a+s+�+�+,A,�,�,&-p-�-.b.�.�.,/n/�/�/�/0Y0�0�0�01/1R1�1-2�2�2�23B3p3�3�3�34H4u4y4�4�45a5�5�56�6�6�67r7�7�7�7 8v8�8�8�8!9U9w9�9:e:�:�:};<�<�<=_=�=&>^>�>9?�?*@O@{@�@�@�@#AAA}ABcB�BbC�C*D�D�D EQE�E�E�EgF�F�F�FeG�G�GH?H]H�H�H�H�HIaI�I*J5J@JMJZJeJ�J�J+K9KZKlK�K�K�K4LiL�L�LMAM�M�M�MN3N�N�NO9OkO�OPBQ�Q3R^R�R�ST�T�T�TU+U^U�U�UV*VMVMW�W�WXAXsX�X�XYmY�Y�YZ�Z�[�[�[3\�\�\]9]e]�]�]N^x^�^_K_�_�_�_$`F`k`�`�`a?a\a�abbEbrb�b�bcAcOc]cmc�cd?e[e�e�e�f�g�g�g'hAh�h�h�h
i:iji�i�i�ij:jij|j�j�j�jk]k�k�kl=l\lwl�l�l�l"mGmtm�m�mn.nWnzn�n�n
o<ooo�o�o�o p=p�p�p)q[q�q�q�qr=r\r�r�r�r�r"sFs�s�s1t�t�t9uu�uvvv�vvw�w4x�x(y`y�y�{|Z|}o}�}�}~I~�~�~#j��<�`�Հ��(�O�p�˂&�����!�m�����̈́��Q�o����-�z�����H���1����T���ω�*�P���Ί�d��������"�_����)�k�����I�3������ƒ��/�N�g�~�ܓ��.�s����S���E���
�C�k���՘��8�o������$����D�{����c���ߝ�L����P������=���֠�a����
� ����ã���H�~�פ+�J�����ܥ]�������G�q������d���Ш�l�����s����*�T���լ��'�:�]�������*�R�����ծ�V���ׯ��+�q���ɰ���H���ӱ8�P�u�����ݲ)�D���b�����մ�p����T���� �F��������Z�W�����߻��K�ļ��'�W�վS�տ�9�@�z���	�m����������	�F�����^�t�����"�Q��������r�����}��h������$�}�������#�'�����7�i������%�m������e��������?�g�������'�R������h������G�����<������P�������0�����������X����� �Q��������E�����:����y�������W�u�������'�L�����m����S�������M�o������f�������&���w��������=�q������n��������)�L�l�������3�^�������N����t��������@�����#�=�f�����
�1�^����1�j����������G�}�������+�b�y�������
�>�q������,�N�w����,�p����)�t��������|����C���� ����3�i��������@�S����A�n���C����5���K��=��0f�X�}�Mh��3`���G	�	�	�	1
�
�
	R��>x��
1
}
�
&��Qs>�����&L��B����\u��S�Z�.5�&h��\|���%^�d�4b�����( � )!�!";"�"�"#@#�#$K$t$�$�$W%�%�%�%&&�&'F'�'(L(�(�(�()D)t)�)�)�)*5*`*+d+�+�+4-o-s-�-�-	.>.�.3/�/�/0`0�0�0%1N1r1�1�12Q2�2�223d3�3�3'4w4�4�45-5�5�5"6�6�6�6
747h7�7�7�78R8�8�8+9�9�9:/:T:x:�:;T;t;�;�;�;<f<�<�<	=;=A=�=�=�>�>}?@e@�@�@�@A�ABiB�BC?C�C�C�CXDpD�DRE�E�FGqG�G�G�G�G�G�G�G�GH#HYH\HoH�HIPISI}I�I�I�IJ&J�JK[K�KLLLfL�L�LMHMqM�M�MDN�N�N*OSO�O�OYP�P�Q=RzR�R�R�S
T8TjT�T�T�T�T0UKU�U�U�U
V/VYV�V�V�V�V�VWW(W\W�W�W�WX2XaX�X�X�XY-YZY�Y�YZZ?ZaZ�Z�Z�Z�Z[[�[�[�[U\�\�\�\<]m]�]�]�]^V^t^�^�^ _B_m_�_�_`-`i`�`�`a3a\a�a�ab>bdb�b�b�b#cBc\ctc�c�c7d�dge�e�efXf�f�f�f%gVg�g�g�ghRh�h�h�h%iLigi�i�i�i�i
jEjtj�j�j�jkNkrk�k�k�k�kll;lfl�l�l5m8m�mnUn�n�n�n�n�n�no4o�o�opJp�p�qEr�r/s�su/uvu�u�u�uIvjvyv�v�vw4wfw�w�w�wxVx�x�x�xy-y\y�y�y*z�z�z�z�z{'{*{L{�{�{�{|@|h|�|�|}Y}�}�}�}#~K~�~�~�~�~+Nr��/�[�����Հ���@�j�����́��=�~���΂��!�E�q���߃<�M�w�����H�������5�g����X�����҈C�F�����Ӊ�5�͊͋�-�W���݌�C�q�����ԍ�+�G�`�|�����=�W�{���͏�L�~�Ґ�s��y����ӓ-��������d�Ɩ��/�Z�T�ژd���Ù�6�`���Ś��K������N�������0�~���ם@���؞I���&����6���ߡ�t�ڢ6��������q���Ŧ�_���G�h���0���֩��&�`���ʪ�@���ī�(�f����o���ϭ߮I��t���ܱ��b���ǲ$�`���Գ�:���Ĵ���O������	�[����_���Z�ֺ|��G����\���̾�S��a��q��(������@�d����}���-�r���M�t���R����s���������
�+�K�����������B������R�����������A�����U���4�������"�T�����Z���	�{����V����m�
�_�����:������m�����b��������J�����.�����'��������a�����g�������V������%�I��<�d���������C�w������K�������>�p���&�a�����@��������M��3�h���P������X�����k�	�u���@�~����f����B����W����A���M����J�����R�s����3`�����$g��M�m�%���2b���)C`����	A	�	�	�	
9
�
�
�
�
9q��D��@
Z
�
�
S���(Yf��Fi���R����-g������9q���S��A)y|������������������������������������������	����������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������	=��� Z } � � V!Y!�!"8"�"�"�#�#$X$�$�$�$,&f'�'�'�'X([(^(a(d(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))
)
)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)********** *#*&*)*,*/*2*5*8*;*�*�*�*�*�*�*�*�*�*�*�*�*++++++++++ +#+&+)+,+/+2+5+8+;+>+A+D+G+J+M+P+S+V+Y+\+_+b+e+h+k+n+q+t+w+z+}+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,
,
,,,,,,,",%,(,+,.,1,4,7,:,=,@,C,F,I,L,O,R,U,X,[,^,a,d,g,j,m,p,s,v,y,|,,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,H-K-N-Q-T-W-Z-]-`-c-f-i-l-o-r-u-x-{-~-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-.........�.�.�.// /#/&/)/,///2/5/8/;/>/A/D/G/J/M/P/S/V/Y/\/_/b/�/�/�0�0U2�2�2�2j3�3�3	4)4^4�4�4�4�4505k5�5�5s6�6�6707t7�7�7z8�89�9:�:b;e;h;�;�;g<�<�<�<�<�<�<�<�<�<�<q=�=>w>�>�>A?q?�?�?�?"@e@�@�@"AhA=B�B�B�C�C�C&D)D,D/D2D5D8D;D>DADDDGDJDMDPDSDVDYD\D_DbDeDhDkDnDqDtDwDzD}D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�DEEE
E
EEEEEEE"E%E(E+E.E1E4E7E:E=E@ECEFEIELEOEREUEXEwEzE}E�E�E�E�E�E�E�E�E�E�E�EFFFFFFFFFF F#F&F)F,F/F2F5F8F;F>FAFDFGFJFMFPFSFVFYF\F_FbFeFhFkFnFqFtFwFzF}F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�FGGG
G
GGGGGGG"G%G(G+G.G1G4G7G:G=G@GCGFGIGLGOGRGUGXG[G^GaGdGgGjGmGpGsGvGyG|GG�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�GHHH	HHHHHHHH!H$H'H*H-H0H3H6H�H%IMI�I�I<JlJ�J�J'KXK�K�K�KLLILxL�L�L=MXM}M�M�M�MN>NoN�N�N�N<OgO�O�O�OPGPnP�P1QXQ�Q�QRUR�R�RuS�S�ST(THThT�T�ThU�U�U�UV�V�V#W&W)W,W/W2W5W8W;W>WAW�WXX�X�X�XY)Y{Y�Y�YCZ�[z\�\�\2]�]�^t_�_�_�_�_�_F`la�ac'cEckc�c�c�c�c�c�cddd	dddXd�d�d�d�d�d�de
e4e7e:e=e@eCeFeIeLeOeReUeXe[e^e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�eGfJfdf�f�fRgUgXg[g^gagdgggjgmgpgsgvgyg|gg�g�g�g�g�h;i>iAiDiGi�i�i�i�i2jGj_j�j�jkEk�k�k�k�k�k�k�k�k�k�k�k!lqltl�m�m�m�mSn�n�op0q�q2rsls�s�s�tFu�u�u'vPvw^w�w�w�w�w(xEx`x|x�xyKyvy�y�yLz�z{{X{w{�{�{�{5|n|�|�|z}�}�} ~}~�~#����&�K�l��������7���C���܂�)�N�|����T���ӄ�{����z��������E�����߇�$�G�J���������Ĉǈʈ͈ЈӈO���� �\�ĊP�ʋ0�Y�����������:���:��� �=���א+�d�ȑ���<�j�ɓ��^�����ʔX���@���F��k�ޘX�����1��њ�(�L�s�v��6�O�n�����ߜ��֝ٝ��0�@�P�������C������U�Р�%�]����4�����1�p���$����K����J������l��V���)����t����S����I�p���7�ݭ�b�����b���*�-�_����F�}���߱��v����3�O�d����4�����۴�&�;�c������C����F��� �`�͹3�ӺI�ɻY���ټ1���-���ܾ���7�M���ȿ��C���7�j�����.�i�����P�k��������F�e������M�����!�K�����T�����
�}���V���y������W�����$�T�y�������;����� �x�����9�x���1�"�L�w�������F�����C�w���H�����&�5�������.����)�����,�B�Y����������a����l�������)�����`���-�O�����p���S���)��������8�����E������f�����J���h���Q�T�������,�G�b������������
�
��1�M�P�S�V�Y�\�_�b�e�h�k�n�q�t�w�z�}�������"�y�|�����������>�r���������L����������Z����(���;���4�����V������f����z��5u�'q�e���������� #&),/258;>ADGJMPSV��%X���y�8��_b�T	�	�	�		
v
�
�
�
>��R
�/�Q�
�����S����9h���a�W�q�m�- t � 1!�!R"�"�"�"�#
$P$%�%&�&�'((�(9)�)�*+y+�+,O,�,-.�../�/C0b1�1�1B2�293�374�4N5t5w5�57�7|89�9&:�:�:,;U;�;�;<�<�=�>�?�@DA�A�B:C�C�C4DODcD}D�D�DiE�E�E�EFRFaF�F9G�H�H�H�HEI�I�I�I8J�J�JJK�KL_LCNnN�P4Q�Q�QFR�R�R%T�TUYU�U�U�V�V�V�WlX�X�X)YGYeY�YZZZZ�Z�Z[[^[a[I\�\t]�]�]7^j^�^�^P_�_B`}`�`Ra�a�a�bTcd�d�ejf�f�fJg|g�g�g)hMhqh�h�h�h+iYi(j{j�j"kKk�k�k�kl:ljl�l�l�m~n@o�qft�t�t�t%u�u�u4v�v�v�vhwx�xDy�y�z*{k{�{�{?|P|y|=}@}�}�}~P~�~�~�~$Ex����8�;�U�s���ހ���?����(�d������������1�S����\�ЉP����\����S����*�z�Ӎ�Ď�.���&�)����������s��N���6������� �M����O�����1�d�����ښ.�Z�����%�q�ݜE����i�ɞ�x�����ß֟��1�<�R�u�����&�ѡ=�o���ڢJ�Σ�4�h���|��������@�m�����E�n�֩���(�
�z���B����*�ޮ��d��h�hashchkisamchkNeinJaKann Datei '%-.200s' nicht erzeugen (Fehler: %d - %s)Kann Tabelle '%-.200s' nicht erzeugen (Fehler: %d - %s)Kann Datenbank '%-.192s' nicht erzeugen (Fehler: %d - %s)Kann Datenbank '%-.192s' nicht erzeugen. Datenbank existiert bereitsKann Datenbank '%-.192s' nicht löschen; Datenbank nicht vorhandenFehler beim Löschen der Datenbank ('%-.192s' kann nicht gelöscht werden, Fehler: %d - %s)Fehler beim Löschen der Datenbank (Verzeichnis '%-.192s' kann nicht gelöscht werden, Fehler: %d - %s)Fehler beim Löschen von '%-.192s' (Fehler: %d - %s)Datensatz in der Systemtabelle nicht lesbarKann Status von '%-.200s' nicht ermitteln (Fehler: %d - %s)Kann Arbeitsverzeichnis nicht ermitteln (Fehler: %d - %s)Datei kann nicht gesperrt werden (Fehler: %d - %s)Kann Datei '%-.200s' nicht öffnen (Fehler: %d - %s)Kann Datei '%-.200s' nicht finden (Fehler: %d - %s)Verzeichnis von '%-.192s' nicht lesbar (Fehler: %d - %s)Kann nicht in das Verzeichnis '%-.192s' wechseln (Fehler: %d - %s)Datensatz hat sich seit dem letzten Zugriff auf Tabelle '%-.192s' geändertFestplatte voll (%s). Warte, bis jemand Platz schafft ... (Fehler: %d - %s)Kann nicht speichern, Grund: doppelter Schlüssel in Tabelle '%-.192s'Fehler beim Schließen von '%-.192s' (Fehler: %d - %s)Fehler beim Lesen der Datei '%-.200s' (Fehler: %d - %s)Fehler beim Umbenennen von '%-.210s' in '%-.210s' (Fehler: %d - %s)Fehler beim Speichern der Datei '%-.200s' (Fehler: %d - %s)'%-.192s' ist für Änderungen gesperrtSortiervorgang abgebrochenView '%-.192s' existiert für '%-.192s' nichtFehler %d - '%-.192s' (Speicher-Engine)Diese Option gibt es nicht (Speicher-Engine für '%-.192s')Kann Datensatz in '%-.192s' nicht findenFalsche Information in Datei '%-.200s'Fehlerhafte Index-Datei für Tabelle '%-.200s'; versuche zu reparierenAlte Index-Datei für Tabelle '%-.192s'. Bitte reparierenTabelle '%-.192s' ist nur lesbarKein Speicher vorhanden (%d Bytes benötigt). Bitte Server neu startenKein Speicher zum Sortieren vorhanden. sort_buffer_size sollte im Server erhöht werdenUnerwartetes Ende beim Lesen der Datei '%-.192s' (Fehler: %d - %s)Zu viele VerbindungenKein Speicher mehr vorhanden. Prüfen Sie, ob mysqld oder ein anderer Prozess den gesamten Speicher verbraucht. Wenn nicht, sollten Sie mit 'ulimit' dafür sorgen, dass mysqld mehr Speicher benutzen darf, oder mehr Swap-Speicher einrichtenKann Hostnamen für diese Adresse nicht erhaltenUngültiger HandshakeBenutzer '%-.48s'@'%-.64s' hat keine Zugriffsberechtigung für Datenbank '%-.192s'Benutzer '%-.48s'@'%-.64s' hat keine Zugriffsberechtigung (verwendetes Passwort: %s)Keine Datenbank ausgewähltUnbekannter BefehlFeld '%-.192s' darf nicht NULL seinUnbekannte Datenbank '%-.192s'Tabelle '%-.192s' bereits vorhandenUnbekannte Tabelle '%-.129s'Feld '%-.192s' in %-.192s ist nicht eindeutigDer Server wird heruntergefahrenUnbekanntes Tabellenfeld '%-.192s' in %-.192s'%-.192s' ist nicht in GROUP BY vorhandenGruppierung über '%-.192s' nicht möglichDie Verwendung von Summierungsfunktionen und Spalten im selben Befehl ist nicht erlaubtDie Anzahl der Spalten entspricht nicht der Anzahl der WerteName des Bezeichners '%-.100s' ist zu langDoppelter Spaltenname: '%-.192s'Doppelter Name für Schlüssel vorhanden: '%-.192s'Doppelter Eintrag '%-.192s' für Schlüssel %dFalsche Spezifikation für Feld '%-.192s'%s bei '%-.80s' in Zeile %dLeere AbfrageTabellenname/Alias '%-.192s' nicht eindeutigFehlerhafter Vorgabewert (DEFAULT) für '%-.192s'Mehrere Primärschlüssel (PRIMARY KEY) definiertZu viele Schlüssel definiert. Maximal %d Schlüssel erlaubtZu viele Teilschlüssel definiert. Maximal %d Teilschlüssel erlaubtSchlüssel ist zu lang. Die maximale Schlüssellänge beträgt %dIn der Tabelle gibt es kein Schlüsselfeld '%-.192s'BLOB-Feld '%-.192s' kann beim verwendeten Tabellentyp nicht als Schlüssel verwendet werdenFeldlänge für Feld '%-.192s' zu groß (maximal %lu). BLOB- oder TEXT-Spaltentyp verwenden!Falsche Tabellendefinition. Es darf nur eine AUTO_INCREMENT-Spalte geben, und diese muss als Schlüssel definiert werden%s: Bereit für Verbindungen.
Version: '%s'  Socket: '%s'  Port: %d%s: Normal heruntergefahren
%s: Signal %d erhalten. Abbruch!
%s: Herunterfahren beendet
%s: Thread %ld zwangsweise beendet. Benutzer: '%-.48s'
Kann IP-Socket nicht erzeugenTabelle '%-.192s' besitzt keinen wie den in CREATE INDEX verwendeten Index. Tabelle neu anlegenFeldbegrenzer-Argument ist nicht in der erwarteten Form. Bitte im Handbuch nachlesenEine feste Zeilenlänge kann für BLOB-Felder nicht verwendet werden. Bitte 'fields terminated by' verwendenDatei '%-.128s' muss im Datenbank-Verzeichnis vorhanden oder lesbar für alle seinDatei '%-.200s' bereits vorhandenDatensätze: %ld  Gelöscht: %ld  Ausgelassen: %ld  Warnungen: %ldDatensätze: %ld  Duplikate: %ldFalscher Unterteilschlüssel. Der verwendete Schlüsselteil ist entweder kein String, die verwendete Länge ist länger als der Teilschlüssel oder die Speicher-Engine unterstützt keine UnterteilschlüsselMit ALTER TABLE können nicht alle Felder auf einmal gelöscht werden. Dafür DROP TABLE verwendenKann '%-.192s' nicht löschen. Existiert die Spalte oder der Schlüssel?Datensätze: %ld  Duplikate: %ld  Warnungen: %ldDie Verwendung der zu aktualisierenden Zieltabelle '%-.192s' ist in der FROM-Klausel nicht zulässig.Unbekannte Thread-ID: %luSie sind nicht Eigentümer von Thread %luKeine Tabellen verwendetZu viele Strings für Feld %-.192s und SET angegebenKann keinen eindeutigen Dateinamen für die Logdatei %-.200s(1-999) erzeugen
Tabelle '%-.192s' ist mit Lesesperre versehen und kann nicht aktualisiert werdenTabelle '%-.192s' wurde nicht mit LOCK TABLES gesperrtBLOB/TEXT-Feld '%-.192s' darf keinen Vorgabewert (DEFAULT) habenUnerlaubter Datenbankname '%-.100s'Unerlaubter Tabellenname '%-.100s'Die Ausführung des SELECT würde zu viele Datensätze untersuchen und wahrscheinlich sehr lange dauern. Bitte WHERE-Klausel überprüfen und gegebenenfalls SET SQL_BIG_SELECTS=1 oder SET MAX_JOIN_SIZE=# verwendenUnbekannter FehlerUnbekannte Prozedur '%-.192s'Falsche Parameterzahl für Prozedur '%-.192s'Falsche Parameter für Prozedur '%-.192s'Unbekannte Tabelle '%-.192s' in '%-.32s'Feld '%-.192s' wurde zweimal angegebenFalsche Verwendung einer GruppierungsfunktionTabelle '%-.192s' verwendet eine Erweiterung, die in dieser MySQL-Version nicht verfügbar istEine Tabelle muss mindestens eine Spalte besitzenTabelle '%-.192s' ist vollUnbekannter Zeichensatz: '%-.64s'Zu viele Tabellen. MySQL kann in einem Join maximal %d Tabellen verwendenZu viele FelderZeilenlänge zu groß. Die maximale Zeilenlänge für den verwendeten Tabellentyp (ohne BLOB-Felder) beträgt %ld. Einige Felder müssen in BLOB oder TEXT umgewandelt werdenThread-Stack-Überlauf. Benutzt: %ld von %ld Stack. 'mysqld --thread_stack=#' verwenden, um bei Bedarf einen größeren Stack anzulegenOUTER JOIN enthält fehlerhafte Abhängigkeiten. In ON verwendete Bedingungen überprüfenTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerKann Funktion '%-.192s' nicht ladenKann Funktion '%-.192s' nicht initialisieren: %-.192sKeine Pfade gestattet für Shared LibraryFunktion '%-.192s' existiert schonKann Shared Library '%-.192s' nicht öffnen (Fehler: %d %-.128s)Kann Funktion '%-.128s' in der Library nicht findenFunktion '%-.192s' ist nicht definiertHost '%-.255s' blockiert wegen zu vieler Verbindungsfehler. Aufheben der Blockierung mit 'mysqladmin flush-hosts'Host '%-.255s' hat keine Berechtigung, sich mit diesem MySQL-Server zu verbindenSie benutzen MySQL als anonymer Benutzer und dürfen daher keine Passwörter ändernSie benötigen die Berechtigung zum Aktualisieren von Tabellen in der Datenbank 'mysql', um die Passwörter anderer Benutzer ändern zu könnenKann keinen passenden Datensatz in Tabelle 'user' findenDatensätze gefunden: %ld  Geändert: %ld  Warnungen: %ldKann keinen neuen Thread erzeugen (Fehler: %d). Sollte noch Speicher verfügbar sein, bitte im Handbuch wegen möglicher Fehler im Betriebssystem nachschlagenAnzahl der Felder stimmt nicht mit der Anzahl der Werte in Zeile %ld übereinKann Tabelle'%-.192s' nicht erneut öffnenUnerlaubte Verwendung eines NULL-Wertsregexp lieferte Fehler '%-.64s'Das Vermischen von GROUP-Feldern (MIN(),MAX(),COUNT()...) mit Nicht-GROUP-Feldern ist nicht zulässig, wenn keine GROUP-BY-Klausel vorhanden istFür Benutzer '%-.48s' auf Host '%-.255s' gibt es keine solche Berechtigung%-.128s Befehl nicht erlaubt für Benutzer '%-.48s'@'%-.64s' auf Tabelle '%-.64s'%-.16s Befehl nicht erlaubt für Benutzer '%-.48s'@'%-.64s' und Feld '%-.192s' in Tabelle '%-.192s'Unzulässiger GRANT- oder REVOKE-Befehl. Verfügbare Berechtigungen sind im Handbuch aufgeführtDas Host- oder User-Argument für GRANT ist zu langTabelle '%-.192s.%-.192s' existiert nichtEine solche Berechtigung ist für User '%-.48s' auf Host '%-.255s' an Tabelle '%-.192s' nicht definiertDer verwendete Befehl ist in dieser MySQL-Version nicht zulässigFehler in der SQL-Syntax. Bitte die korrekte Syntax im Handbuch nachschlagenDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAbbruch der Verbindung %ld zur Datenbank '%-.192s'. Benutzer: '%-.48s' (%-.64s)Empfangenes Paket ist größer als 'max_allowed_packet' BytesLese-Fehler bei einer Verbindungs-Pipefcntl() lieferte einen FehlerPakete nicht in der richtigen Reihenfolge empfangenKommunikationspaket lässt sich nicht entpackenFehler beim Lesen eines KommunikationspaketsZeitüberschreitung beim Lesen eines KommunikationspaketsFehler beim Schreiben eines KommunikationspaketsZeitüberschreitung beim Schreiben eines KommunikationspaketsErgebnis-String ist länger als 'max_allowed_packet' BytesDer verwendete Tabellentyp unterstützt keine BLOB- und TEXT-FelderDer verwendete Tabellentyp unterstützt keine AUTO_INCREMENT-FelderINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESFalscher Spaltenname '%-.100s'Die verwendete Speicher-Engine kann die Spalte '%-.192s' nicht indizierenNicht alle Tabellen in der MERGE-Tabelle sind gleich definiertSchreiben in Tabelle '%-.192s' nicht möglich wegen einer Eindeutigkeitsbeschränkung (unique constraint)BLOB- oder TEXT-Spalte '%-.192s' wird in der Schlüsseldefinition ohne Schlüssellängenangabe verwendetAlle Teile eines PRIMARY KEY müssen als NOT NULL definiert sein. Wenn NULL in einem Schlüssel benötigt wird, muss ein UNIQUE-Schlüssel verwendet werdenErgebnis besteht aus mehr als einer ZeileDieser Tabellentyp benötigt einen Primärschlüssel (PRIMARY KEY)Diese MySQL-Version ist nicht mit RAID-Unterstützung kompiliertMySQL läuft im sicheren Aktualisierungsmodus (safe update mode). Sie haben versucht, eine Tabelle zu aktualisieren, ohne in der WHERE-Klausel ein KEY-Feld anzugeben. %sSchlüssel '%-.192s' existiert in der Tabelle '%-.192s' nichtKann Tabelle nicht öffnenDie Speicher-Engine für diese Tabelle unterstützt kein %sSie dürfen diesen Befehl nicht in einer Transaktion ausführenFehler %d - '%-.192s' beim COMMITFehler %d - '%-.192s' beim ROLLBACKFehler %d bei FLUSH_LOGSFehler %d bei CHECKPOINTAbbruch der Verbindung %u zur Datenbank '%-.192s'. Benutzer: '%-.48s', Host: '%-.255s' (%-.64s)Die Speicher-Engine für die Tabelle unterstützt keinen binären Tabellen-DumpBinlog geschlossen. Kann RESET MASTER nicht ausführenNeuerstellung des Index der Dump-Tabelle '%-.192s' fehlgeschlagenFehler vom Master: '%-.64s'Netzfehler beim Lesen vom MasterNetzfehler beim Schreiben zum MasterKann keinen FULLTEXT-Index finden, der der Feldliste entsprichtKann den angegebenen Befehl wegen einer aktiven Tabellensperre oder einer aktiven Transaktion nicht ausführenUnbekannte Systemvariable '%-.64s'Tabelle '%-.192s' ist als defekt markiert und sollte repariert werdenTabelle '%-.192s' ist als defekt markiert und der letzte (automatische?) Reparaturversuch schlug fehlÄnderungen an einigen nicht transaktionalen Tabellen konnten nicht zurückgerollt werdenTransaktionen, die aus mehreren Befehlen bestehen, benötigten mehr als 'max_binlog_cache_size' Bytes an Speicher. Btte vergrössern Sie diese Server-Variable versuchen Sie es noch einmalDiese Operation kann bei einem aktiven Slave nicht durchgeführt werden. Bitte zuerst STOP SLAVE ausführenDiese Operation benötigt einen aktiven Slave. Bitte Slave konfigurieren und mittels START SLAVE aktivierenDer Server ist nicht als Slave konfiguriert. Bitte in der Konfigurationsdatei oder mittels CHANGE MASTER TO behebenKonnte Master-Info-Struktur nicht initialisieren. Weitere Fehlermeldungen können im MySQL-Error-Log eingesehen werdenKonnte Slave-Thread nicht starten. Bitte System-Ressourcen überprüfenBenutzer '%-.64s' hat mehr als 'max_user_connections' aktive VerbindungenBei SET dürfen nur konstante Ausdrücke verwendet werdenBeim Warten auf eine Sperre wurde die zulässige Wartezeit überschritten. Bitte versuchen Sie, die Transaktion neu zu startenDie Gesamtzahl der Sperren überschreitet die Größe der SperrtabelleWährend einer READ-UNCOMMITTED-Transaktion können keine UPDATE-Sperren angefordert werdenDROP DATABASE ist nicht erlaubt, solange der Thread eine globale Lesesperre hältCREATE DATABASE ist nicht erlaubt, solange der Thread eine globale Lesesperre hältFalsche Argumente für %s'%-.48s'@'%-.64s' ist nicht berechtigt, neue Benutzer hinzuzufügenFalsche Tabellendefinition. Alle MERGE-Tabellen müssen sich in derselben Datenbank befindenBeim Versuch, eine Sperre anzufordern, ist ein Deadlock aufgetreten. Versuchen Sie, die Transaktion neu zu startenDer verwendete Tabellentyp unterstützt keine FULLTEXT-IndizesFremdschlüssel-Beschränkung kann nicht hinzugefügt werdenHinzufügen oder Aktualisieren eines Kind-Datensatzes schlug aufgrund einer Fremdschlüssel-Beschränkung fehlLöschen oder Aktualisieren eines Eltern-Datensatzes schlug aufgrund einer Fremdschlüssel-Beschränkung fehlFehler bei der Verbindung zum Master: %-.128sBeim Ausführen einer Abfrage auf dem Master trat ein Fehler auf: %-.128sFehler beim Ausführen des Befehls %s: %-.128sFalsche Verwendung von %s und %sDie verwendeten SELECT-Befehle liefern unterschiedliche Anzahlen von Feldern zurückAugrund eines READ-LOCK-Konflikts kann die Abfrage nicht ausgeführt werdenDie gleichzeitige Verwendung von Tabellen mit und ohne Transaktionsunterstützung ist deaktiviertOption '%s' wird im Befehl zweimal verwendetBenutzer '%-.64s' hat die Ressourcenbeschränkung '%s' überschritten (aktueller Wert: %ld)Kein Zugriff. Hierfür wird die Berechtigung %-.128s benötigtVariable '%-.64s' ist eine lokale Variable und kann nicht mit SET GLOBAL verändert werdenVariable '%-.64s' ist eine globale Variable und muss mit SET GLOBAL verändert werdenVariable '%-.64s' hat keinen VorgabewertVariable '%-.64s' kann nicht auf '%-.200s' gesetzt werdenFalscher Argumenttyp für Variable '%-.64s'Variable '%-.64s' kann nur verändert, nicht gelesen werdenFalsche Verwendung oder Platzierung von '%s'Diese MySQL-Version unterstützt '%s' nichtSchwerer Fehler %d: '%-.512s vom Master beim Lesen des binären LogsSlave-SQL-Thread hat die Abfrage aufgrund von replicate-*-table-Regeln ignoriertVariable '%-.192s' ist eine %s-VariableFalsche Fremdschlüssel-Definition für '%-.192s': %sSchlüssel- und Tabellenverweis passen nicht zusammenOperand sollte %d Spalte(n) enthaltenUnterabfrage lieferte mehr als einen Datensatz zurückUnbekannter Prepared-Statement-Handler (%.*s) für %s angegebenDie Hilfe-Datenbank ist beschädigt oder existiert nichtZyklischer Verweis in UnterabfragenFeld '%s' wird von %s nach %s umgewandeltVerweis '%-.64s' wird nicht unterstützt (%s)Für jede abgeleitete Tabelle muss ein eigener Alias angegeben werdenSelect %u wurde während der Optimierung reduziertTabelle '%-.192s', die in einem der SELECT-Befehle verwendet wurde, kann nicht in %-.32s verwendet werdenClient unterstützt das vom Server erwartete Authentifizierungsprotokoll nicht. Bitte aktualisieren Sie Ihren MySQL-ClientAlle Teile eines SPATIAL-Index müssen als NOT NULL deklariert seinCOLLATION '%s' ist für CHARACTER SET '%s' ungültigSlave läuft bereitsSlave wurde bereits angehaltenUnkomprimierte Daten sind zu groß. Die maximale Größe beträgt %d (wahrscheinlich wurde die Länge der unkomprimierten Daten beschädigt)ZLIB: Nicht genug SpeicherZLIB: Im Ausgabepuffer ist nicht genug Platz vorhanden (wahrscheinlich wurde die Länge der unkomprimierten Daten beschädigt)ZLIB: Eingabedaten beschädigtRow %u was cut by GROUP_CONCAT()Zeile %ld enthält nicht für alle Felder DatenZeile %ld gekürzt, die Zeile enthielt mehr Daten, als es Eingabefelder gibtFeld auf Vorgabewert gesetzt, da NULL für NOT-NULL-Feld '%s' in Zeile %ld angegebenOut of range value for column '%s' at row %ldDaten abgeschnitten für Feld '%s' in Zeile %ldFür Tabelle '%s' wird Speicher-Engine %s benutztUnerlaubte Mischung von Sortierreihenfolgen (%s, %s) und (%s, %s) für Operation '%s'Kann einen oder mehrere der angegebenen Benutzer nicht löschenKann nicht alle Berechtigungen widerrufen, die für einen oder mehrere Benutzer gewährt wurdenUnerlaubte Mischung von Sortierreihenfolgen (%s, %s), (%s, %s), (%s, %s) für Operation '%s'Unerlaubte Mischung von Sortierreihenfolgen für Operation '%s'Variable '%-.64s' ist keine Variablen-Komponente (kann nicht als XXXX.variablen_name verwendet werden)Unbekannte Sortierreihenfolge: '%-.64s'SSL-Parameter in CHANGE MASTER werden ignoriert, weil dieser MySQL-Slave ohne SSL-Unterstützung kompiliert wurde. Sie können aber später verwendet werden, wenn ein MySQL-Slave mit SSL gestartet wirdServer läuft im Modus --secure-auth, aber '%s'@'%s' hat ein Passwort im alten Format. Bitte Passwort ins neue Format ändernFeld oder Verweis '%-.192s%s%-.192s%s%-.192s' im SELECT-Befehl Nr. %d wurde im SELECT-Befehl Nr. %d aufgelöstFalscher Parameter oder falsche Kombination von Parametern für START SLAVE UNTILEs wird empfohlen, mit --skip-replica-start zu starten, wenn mit START SLAVE UNTIL eine Schritt-für-Schritt-Replikation ausgeführt wird. Ansonsten gibt es Probleme, wenn ein Slave-Server unerwartet neu startetSQL-Thread soll nicht gestartet werden. Daher werden UNTIL-Optionen ignoriertFalscher Indexname '%-.100s'Falscher Katalogname '%-.100s'Änderung der Query-Cache-Größe auf %lu fehlgeschlagen; neue Query-Cache-Größe ist %luFeld '%-.192s' kann nicht Teil eines FULLTEXT-Index seinUnbekannter Schlüssel-Cache '%-.100s'MySQL wurde mit --skip-name-resolve gestartet. Diese Option darf nicht verwendet werden, damit diese Rechtevergabe möglich istUnbekannte Speicher-Engine '%s''%s' ist veraltet. Bitte benutzen Sie '%s'Die Zieltabelle %-.100s von %s ist nicht aktualisierbarDas Feature '%s' ist ausgeschaltet, Sie müssen MySQL mit '%s' übersetzen, damit es verfügbar istDer MySQL-Server läuft mit der Option %s und kann diese Anweisung deswegen nicht ausführenFeld '%-.100s' hat doppelten Wert '%-.64s' in %sFalscher %-.64s-Wert gekürzt: '%-.128s'Fehlerhafte Tabellendefinition. Es kann nur eine einzige TIMESTAMP-Spalte mit CURRENT_TIMESTAMP als DEFAULT oder in einer ON-UPDATE-Klausel gebenUngültige ON-UPDATE-Klausel für Spalte '%-.192s'Dieser Befehl wird im Protokoll für vorbereitete Anweisungen noch nicht unterstütztFehler %d '%-.100s' von %sTemporärer Fehler %d '%-.100s' von %sUnbekannte oder falsche Zeitzone: '%-.64s'Ungültiger TIMESTAMP-Wert in Feld '%s', Zeile %ldUngültiger %s-Zeichen-String: '%.64s'Ergebnis von %s() war größer als max_allowed_packet (%ld) Bytes und wurde deshalb gekürztWidersprüchliche Deklarationen: '%s%s' und '%s%s'Kann kein %s innerhalb einer anderen gespeicherten Routine erzeugen%s %s existiert bereits%s %s existiert nichtDROP %s %s ist fehlgeschlagenCREATE %s %s ist fehlgeschlagen%s ohne passende Marke: %sNeudefinition der Marke %sEnde-Marke %s ohne zugehörigen AnfangZugriff auf nichtinitialisierte Variable %sPROCEDURE %s kann im gegebenen Kontext keine Ergebnismenge zurückgebenRETURN ist nur innerhalb einer FUNCTION erlaubt%s ist in gespeicherten Prozeduren nicht erlaubtDas Update-Log ist veraltet und wurde durch das Binär-Log ersetzt. SET SQL_LOG_UPDATE wird ignoriert.Das Update-Log ist veraltet und wurde durch das Binär-Log ersetzt. SET SQL_LOG_UPDATE wurde in SET SQL_LOG_BIN übersetzt.Ausführung der Abfrage wurde unterbrochenFalsche Anzahl von Argumenten für %s %s; erwarte %u, erhalte %uUndefinierte CONDITION: %sKein RETURN in FUNCTION %s gefundenFUNCTION %s endete ohne RETURNCursor-Anweisung muss ein SELECT seinCursor-SELECT darf kein INTO habenUndefinierter CURSOR: %sCursor ist schon geöffnetCursor ist nicht geöffnetNicht deklarierte Variable: %sFalsche Anzahl von FETCH-VariablenKeine Daten - null Zeilen geholt (fetch), ausgewählt oder verarbeitetDoppelter Parameter: %sDoppelte Variable: %sDoppelte Bedingung: %sDoppelter Cursor: %sALTER %s %s fehlgeschlagenSubquery-Wert wird nicht unterstützt%s ist in gespeicherten Funktionen und in Triggern nicht erlaubtDeklaration einer Variablen oder einer Bedingung nach der Deklaration eines Cursors oder eines HandlersDeklaration eines Cursors nach der Deklaration eines HandlersFall für CASE-Anweisung nicht gefundenKonfigurationsdatei '%-.192s' ist zu großNicht wohlgeformter Dateityp-Header in Datei '%-.192s'Unerwartetes Dateiende beim Parsen des Kommentars '%-.200s'Fehler beim Parsen des Parameters '%-.192s' (Zeile: '%-.192s')Unerwartetes Dateiende beim Überspringen des unbekannten Parameters '%-.192s'EXPLAIN/SHOW kann nicht verlangt werden. Rechte für zugrunde liegende Tabelle fehlenDatei '%-.192s' hat unbekannten Typ '%-.64s' im Header'%-.192s.%-.192s' ist nicht %sFeld '%-.192s' ist nicht aktualisierbarSELECT der View enthält eine Subquery in der FROM-KlauselSELECT der View enthält eine '%s'-KlauselSELECT der View enthält eine Variable oder einen ParameterSELECT der View verweist auf eine temporäre Tabelle '%-.192s'SELECT- und Feldliste der Views haben unterschiedliche Anzahlen von SpaltenView-Merge-Algorithmus kann hier momentan nicht verwendet werden (undefinierter Algorithmus wird angenommen)Die aktualisierte View enthält nicht den vollständigen Schlüssel der zugrunde liegenden TabelleView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themKann eine %s nicht von innerhalb einer anderen gespeicherten Routine löschen oder ändernGOTO ist im Handler einer gespeicherten Prozedur nicht erlaubtTrigger existiert bereitsTrigger existiert nicht'%-.192s' des Triggers ist View oder temporäre TabelleAktualisieren einer %s-Zeile ist in einem %s-Trigger nicht erlaubtEs gibt keine %s-Zeile im %s-TriggerFeld '%-.192s' hat keinen VorgabewertDivision durch 0Falscher %-.32s-Wert: '%-.128s' für Feld '%.192s' in Zeile %ldNicht zulässiger %s-Wert '%-.192s' beim Parsen gefundenCHECK OPTION auf nicht-aktualisierbarem View '%-.192s.%-.192s'CHECK OPTION fehlgeschlagen: '%-.192s.%-.192s'Befehl %-.16s nicht zulässig für Benutzer '%-.48s'@'%-.64s' in Routine '%-.192s'Bereinigen alter Relais-Logs fehlgeschlagen: %sPasswort-Hash sollte eine Hexdaezimalzahl mit %d Stellen seinZiel-Log im Binlog-Index nicht gefundenFehler beim Lesen der Log-Index-DateiServer-Konfiguration erlaubt keine Binlog-Bereinigungfseek() fehlgeschlagenSchwerwiegender Fehler bei der Log-BereinigungEin zu bereinigendes Log wird gerade benutzt, daher keine BereinigungUnbekannter Fehler bei Log-BereinigungInitialisierung der Relais-Log-Position fehlgeschlagen: %sSie verwenden keine BinärlogsDie Schreibweise '%-.64s' ist für interne Zwecke des MySQL-Servers reserviertWSAStartup fehlgeschlagenKann Prozeduren mit unterschiedlichen Gruppen noch nicht verarbeitenSELECT muss bei dieser Prozedur ein GROUP BY habenKann bei dieser Prozedur keine ORDER-BY-Klausel verwendenBinärlogs und Replikation verhindern Wechsel des globalen Servers %sKann Datei nicht abbilden: %-.200s, Fehler: %dFalsche magische Zahlen in %-.64sVorbereitete Anweisung enthält zu viele PlatzhalterLänge des Schlüsselteils '%-.192s' kann nicht 0 seinView-Text-Prüfsumme fehlgeschlagenKann nicht mehr als eine Basistabelle über Join-View '%-.192s.%-.192s' ändernKann nicht ohne Feldliste in Join-View '%-.192s.%-.192s' einfügenKann nicht aus Join-View '%-.192s.%-.192s' löschenOperation %s schlug fehl für %.256sXAER_NOTA: Unbekannte XIDXAER_INVAL: Ungültige Argumente (oder nicht unterstützter Befehl)XAER_RMFAIL: DEr Befehl kann nicht ausgeführt werden, wenn die globale Transaktion im Zustand %.64s istXAER_OUTSIDE: Einige Arbeiten werden außerhalb der globalen Transaktion verrichtetXAER_RMERR: Schwerwiegender Fehler im Transaktionszweig - prüfen Sie Ihre Daten auf KonsistenzXA_RBROLLBACK: Transaktionszweig wurde zurückgerolltEs gibt diese Berechtigung für Benutzer '%-.48s' auf Host '%-.255s' für Routine '%-.192s' nichtGewährung von EXECUTE- und ALTER-ROUTINE-Rechten fehlgeschlagenRücknahme aller Rechte für die gelöschte Routine fehlgeschlagenDaten zu lang für Feld '%s' in Zeile %ldUngültiger SQLSTATE: '%s'%s: bereit für Verbindungen. Version: '%s'  Socket: '%s'  Port: %d  %sKann Wert aus Datei mit Zeilen fester Größe nicht in Variable ladenSie dürfen keinen Benutzer mit GRANT anlegenFalscher %-.32s-Wert: '%-.128s' für Funktion %-.32sTabellendefinition wurde geändert, bitte starten Sie die Transaktion neuDoppelter Handler im selben Block deklariertOUT- oder INOUT-Argument %d für Routine %s ist keine VariableRückgabe einer Ergebnismenge aus einer %s ist nicht erlaubtKann kein Geometrieobjekt aus den Daten machen, die Sie dem GEOMETRY-Feld übergeben habenEine Routine, die weder NO SQL noch READS SQL DATA in der Deklaration hat, schlug fehl und Binärlogging ist aktiv. Wenn Nicht-Transaktions-Tabellen aktualisiert wurden, enthält das Binärlog ihre Änderungen nichtDiese Routine hat weder DETERMINISTIC, NO SQL noch READS SQL DATA in der Deklaration und Binärlogging ist aktiv (*vielleicht* sollten Sie die weniger sichere Variable log_bin_trust_function_creators verwenden)Sie haben keine SUPER-Berechtigung und Binärlogging ist aktiv (*vielleicht* sollten Sie die weniger sichere Variable log_bin_trust_function_creators verwenden)Sie können keine vorbereitete Anweisung ausführen, die mit einem geöffneten Cursor verknüpft ist. Setzen Sie die Anweisung zurück, um sie neu auszuführenDie Anweisung (%lu) hat keinen geöffneten CursorExplizites oder implizites Commit ist in gespeicherten Funktionen und in Triggern nicht erlaubtEin Feld der dem View '%-.192s.%-.192s' zugrundeliegenden Tabelle hat keinen VorgabewertRekursive gespeicherte Routinen und Triggers sind nicht erlaubtZu großer Skalierungsfaktor %d für Feld '%-.192s' angegeben. Maximum ist %luZu große Genauigkeit %d für Feld '%-.192s' angegeben. Maximum ist %luFür FLOAT(M,D), DOUBLE(M,D) oder DECIMAL(M,D) muss M >= D sein (Feld '%-.192s')Sie können Schreibsperren auf der Systemtabelle nicht mit anderen Tabellen kombinierenKann nicht mit Fremddatenquelle verbinden: %.64sBei der Verarbeitung der Abfrage ist in der Fremddatenquelle ein Problem aufgetreten. Datenquellenfehlermeldung: %-.64sDie Fremddatenquelle, auf die Sie zugreifen wollen, existiert nicht. Datenquellenfehlermeldung:  %-.64sKann föderierte Tabelle nicht erzeugen. Der Datenquellen-Verbindungsstring '%-.64s' hat kein korrektes FormatDer Datenquellen-Verbindungsstring '%-.64s' hat kein korrektes FormatKann föderierte Tabelle nicht erzeugen. Fremddatenquellenfehlermeldung:  %-.64sTrigger im falschen SchemaThread-Stack-Überlauf: %ld Bytes eines %ld-Byte-Stacks in Verwendung, und %ld Bytes benötigt. Verwenden Sie 'mysqld --thread_stack=#', um einen größeren Stack anzugebenRoutinen-Body für '%-.100s' ist zu langDer vorgabemäßige Schlüssel-Cache kann nicht gelöscht werdenAnzeigebreite außerhalb des zulässigen Bereichs für Spalte '%-.192s' (Maximum: %lu)XAER_DUPID: Die XID existiert bereitsDatetime-Funktion: %-.32s FeldüberlaufKann Tabelle '%-.192s' in gespeicherter Funktion oder Trigger nicht aktualisieren, weil sie bereits von der Anweisung verwendet wird, die diese gespeicherte Funktion oder den Trigger aufriefDie Definition der Tabelle '%-.192s' verhindert die Operation %.192s auf Tabelle '%-.192s'Die vorbereitete Anweisung enthält einen Aufruf einer gespeicherten Routine, die auf eben dieselbe Anweisung verweist. Es ist nicht erlaubt, eine vorbereitete Anweisung in solch rekursiver Weise auszuführenEs ist nicht erlaubt, innerhalb einer gespeicherten Funktion oder eines Triggers AUTOCOMMIT zu setzenDefinierer des View ist nicht vollständig spezifiziertView '%-.192s'.'%-.192s' hat keine Definierer-Information (altes Tabellenformat). Der aktuelle Benutzer wird als Definierer verwendet. Bitte erstellen Sie den View neuSie brauchen die SUPER-Berechtigung, um einen View mit dem Definierer '%-.192s'@'%-.192s' zu erzeugenDer als Definierer angegebene Benutzer ('%-.64s'@'%-.64s') existiert nichtWechsel des Schemas von '%-.192s' auf '%-.192s' ist nicht erlaubtKann Eltern-Zeile nicht löschen oder aktualisieren: eine Fremdschlüsselbedingung schlägt fehl (%.192s)Kann Kind-Zeile nicht hinzufügen oder aktualisieren: eine Fremdschlüsselbedingung schlägt fehl (%.192s)Variable '%-.64s' muss mit `...` geschützt oder aber umbenannt werdenNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' hat altes Format, Sie sollten die '%s'-Objekt(e) neu erzeugenRekursionsgrenze %d (durch Variable max_sp_recursion_depth gegeben) wurde für Routine %.192s überschrittenRoutine %-.192s konnte nicht geladen werden. Die data dictionary Tabelle fehlt, ist beschädigt, oder enthält fehlerhaften Daten (interner Code: %d)Ungültiger Routinenname '%-.192s'Tabellenaktualisierung erforderlich. Bitte zum Reparieren "REPAIR TABLE `%-.64s`" eingeben!AGGREGATE wird bei gespeicherten Funktionen nicht unterstütztKann nicht mehr Anweisungen als max_prepared_stmt_count erzeugen (aktueller Wert: %lu)`%-.192s`.`%-.192s` enthält View-RekursionIn der %-.192s-Klausel wird das die Nicht-Gruppierungsspalte '%-.64s' verwendetDer verwendete Tabellentyp unterstützt keine SPATIAL-IndizesTrigger können nicht auf Systemtabellen erzeugt werdenFührende Leerzeichen werden aus dem Namen '%s' entferntLesen des Autoincrement-Werts von der Speicher-Engine fehlgeschlagenBenutzernameHostnameString '%-.70s' ist zu lang für %s (sollte nicht länger sein als %d)Die Zieltabelle %-.100s von %s ist nicht einfügbarTabelle '%-.64s' ist unterschiedlich definiert, nicht vom Typ MyISAM oder existiert nichtZu tief verschachtelte SELECT-AnweisungenName '%-.64s' wurde zu ''Das erste Zeichen der Zeichenkette FIELDS TERMINATED ist mehrdeutig; bitte benutzen Sie nicht optionale und nicht leere FIELDS ENCLOSED BYDer entfernte Server %s, den Sie versuchen zu erzeugen, existiert schon.Die externe Verbindung, auf die Sie zugreifen wollen, existiert nicht. Datenquellenfehlermeldung:  %-.64sSpeicher-Engine '%-.64s' der Tabelle unterstützt die Option '%.64s' nichtFehler in der SQL-Syntax: %-.64s-PARTITIONierung erfordert Definition von VALUES %-.64s für jede PartitionNur %-.64s-PARTITIONierung kann VALUES %-.64s in der Partitionsdefinition verwendenMAXVALUE kann nur für die Definition der letzten Partition verwendet werdenUnterpartitionen dürfen nur HASH- oder KEY-Partitionen seinWenn Sie Unterpartitionen auf einer Partition definieren, müssen Sie das für alle Partitionen tunFalsche Anzahl von Partitionen definiert, stimmt nicht mit vorherigen Einstellungen übereinFalsche Anzahl von Unterpartitionen definiert, stimmt nicht mit vorherigen Einstellungen übereinKonstante oder Random-Ausdrücke in (Unter-)Partitionsfunktionen sind nicht erlaubtAusdrücke in RANGE/LIST VALUES müssen konstant seinFelder in der Feldliste der Partitionierungsfunktion wurden in der Tabelle nicht gefundenEine Feldliste ist nur in KEY-Partitionen erlaubtDie Partitionierungsinformationen in der frm-Datei stimmen nicht mit dem überein, was in die frm-Datei geschrieben werden kannDie %-.192s-Funktion gibt einen falschen Typ zurückFür %-.64s-Partitionen muss jede Partition definiert seinWerte in VALUES LESS THAN müssen für jede Partition strikt aufsteigend seinVALUES-Werte müssen vom selben Typ wie die Partitionierungsfunktion seinMehrfachdefinition derselben Konstante bei Listen-PartitionierungPartitionierung kann in einer Abfrage nicht alleinstehend benutzt werdenDas Vermischen von Handlern in Partitionen ist in dieser Version von MySQL nicht erlaubtFür die partitionierte Engine müssen alle %-.64s definiert seinEs wurden zu vielen Partitionen (einschließlich Unterpartitionen) definiertRANGE/LIST-Partitionierung kann bei Unterpartitionen nur zusammen mit HASH/KEY-Partitionierung verwendet werdenErzeugen einer spezifischen Handler-Datei fehlgeschlagenIn der Partitionierungsfunktion sind BLOB-Spalten nicht erlaubtA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Eine Anzahl von %-.64s = 0 ist kein erlaubter WertPartitionsverwaltung einer nicht partitionierten Tabelle ist nicht möglichFremdschlüssel-Beschränkungen sind im Zusammenhang mit Partitionierung nicht zulässigFehler in der Partitionsliste bei %-.64sEs lassen sich nicht sämtliche Partitionen löschen, benutzen Sie statt dessen DROP TABLECOALESCE PARTITION kann nur auf HASH- oder KEY-Partitionen benutzt werdenREORGANIZE PARTITION kann nur zur Reorganisation von Partitionen verwendet werden, nicht, um ihre Nummern zu ändernREORGANIZE PARTITION ohne Parameter kann nur für auto-partitionierte Tabellen verwendet werden, die HASH-Partitionierung benutzen%-.64s PARTITION kann nur für RANGE- oder LIST-Partitionen verwendet werdenEs wurde versucht, eine oder mehrere Partitionen mit der falschen Anzahl von Unterpartitionen hinzuzufügenEs muss zumindest eine Partition hinzugefügt werdenZumindest eine Partition muss mit COALESCE PARTITION zusammengefügt werdenEs wurde versucht, mehr Partitionen als vorhanden zu reorganisierenDoppelter Partitionsname: %-.192sEs es nicht erlaubt, bei diesem Befehl binlog abzuschaltenBei der Reorganisation eines Satzes von Partitionen müssen diese in geordneter Reihenfolge vorliegenDie Reorganisation von RANGE-Partitionen kann Gesamtbereiche nicht verändern, mit Ausnahme der letzten Partition, die den Bereich erweitern kannPartitionsfunktion in dieser Version dieses Handlers nicht unterstütztPartitionszustand kann nicht von CREATE oder ALTER TABLE aus definiert werdenDer Handler %-.64s unterstützt in VALUES nur 32-Bit-IntegersPlugin '%-.192s' ist nicht geladenFalscher %-.32s-Wert: '%-.128s'Tabelle hat für den Wert %-.64s keine Partition%s darf nicht mehr als einmal angegegeben werdenAnlegen von %s fehlgeschlagenLöschen von %s fehlgeschlagenDer Handler unterstützt keine automatische Erweiterung (Autoextend) von TablespacesEin Größen-Parameter wurde unkorrekt angegeben, muss entweder Zahl sein oder im Format 10MDie Zahl für die Größe war korrekt, aber der Zahlanteil darf nicht größer als 2 Milliarden seinÄnderung von %s fehlgeschlagenSchreiben einer Zeilen ins zeilenbasierte Binärlog fehlgeschlagenTabellendefinition auf Master und Slave stimmt nicht überein: %sSlave, die mit --log-replica-updates laufen, müssen zeilenbasiertes Loggen verwenden, um zeilenbasierte Binärlog-Ereignisse loggen zu könnenEvent '%-.192s' existiert bereitsSpeichern von Event %s fehlgeschlagen. Fehlercode der Speicher-Engine: %dUnbekanntes Event '%-.192s'Ändern des Events '%-.192s' fehlgeschlagenLöschen von %s fehlgeschlagenINTERVAL ist entweder nicht positiv oder zu großENDS ist entweder ungültig oder liegt vor STARTSAusführungszeit des Events liegt in der Vergangenheit. Event wurde deaktiviertÖffnen von mysql.event fehlgeschlagenKein DATETIME-Ausdruck angegebenSpaltenanzahl von mysql.%s falsch. %d erwartet, aber %d gefunden. Tabelle ist wahrscheinlich beschädigtKann mysql.%s nicht einlesen. Tabelle ist wahrscheinlich beschädigtLöschen des Events aus mysql.event fehlgeschlagenFehler beim Kompilieren des Event-BodysAlter und neuer Event-Name sind gleichDaten der Spalte '%s' zu langKann Index '%-.192s' nicht löschen: wird für eine Fremdschlüsselbeschränkung benötigtDie Syntax '%s' ist veraltet und wird in MySQL %s entfernt. Bitte benutzen Sie statt dessen %sEine Log-Tabelle kann nicht schreibgesperrt werden. Es ist ohnehin nur Lesezugriff möglichLog-Tabellen können nicht gesperrt werden.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entrySpaltenanzahl von mysql.%s falsch. %d erwartet, aber %d erhalten. Erzeugt mit MySQL %d, jetzt unter %d. Bitte verwenden Sie die MySQL-Upgrade-Prozedur, um den Fehler zu beheben.Kann nicht aus dem zeilenbasierten Binärlog-Format herauswechseln, wenn die Sitzung offene temporäre Tabellen hatDas Binärlog-Format kann innerhalb einer gespeicherten Funktion oder eines Triggers nicht geändert werdenDie Speicher-Engine NDB Cluster unterstützt das Ändern des Binärlog-Formats zur Laufzeit noch nichtAnlegen temporärer Tabellen mit Partitionen nicht möglichPartitionskonstante liegt außerhalb der PartitionsfunktionsdomäneDiese Partitionierungsfunktion ist nicht erlaubtFehler im DDL-LogIn VALUES LESS THAN dürfen keine NULL-Werte verwendet werdenFalscher PartitionsnameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE führt zur Neusequenzierung von auto_increment, wodurch der doppelte Eintrag '%-.192s' für Schlüssel '%-.192s' auftrittInterner Scheduler-Fehler %dFehler während des Startens oder Anhalten des Schedulers. Fehlercode %uEngine kann in partitionierten Tabellen nicht verwendet werdenKann Logdatei '%-.64s' nicht aktivierenDer Server wurde nicht mit zeilenbasierter Replikation gebautDer Server hat keine zeilenbasierte ReplikationRekursivität von EVENT-DDL-Anweisungen ist unzulässig wenn ein Hauptteil (Body) existiertKann nicht weitermachen, weil die Tabellen, die von Events verwendet werden, beim Serverstart als beschädigt markiert wurdenAn dieser Stelle sind nur Ganzzahlen zulässigDiese Speicher-Engine kann für Logtabellen nicht verwendet werdenSie können eine Logtabelle nicht '%s', wenn Loggen angeschaltet istKann '%s' nicht umbenennen. Wenn Loggen angeschaltet ist, müssen zwei Tabellen umbenannt werden: die Logtabelle zu einer Archivtabelle, und eine weitere Tabelle zu '%s'Falsche Anzahl von Parametern beim Aufruf der nativen Funktion '%-.192s'Falscher Parameter beim Aufruf der nativen Funktion '%-.192s'Falsche Parameter beim Aufruf der gespeicherten Funktion %-.192sDie Funktion '%-.192s' hat denselben Namen wie eine native FunktionDoppelter Eintrag '%-.64s' für Schlüssel '%-.385s'Zu viele offene Dateien, bitte führen Sie den Befehl noch einmal ausAusführungszeit des Events liegt in der Vergangenheit, und es wurde ON COMPLETION NOT PRESERVE gesetzt. Das Event wurde unmittelbar nach Erzeugung gelöscht.Execution Zeitpunkt des Ereignisses in der Vergangenheit liegt, und es war NACH ABSCHLUSS Set nicht erhalten. Die Veranstaltung wurde nicht verändert. Geben Sie einen Zeitpunkt in der Zukunft.Der Vorfall %s passierte auf dem Master. Meldung: %sTabelle hat für einige bestehende Werte keine PartitionUnsichere Anweisung ins Binärlog geschrieben, weil Anweisungsformat BINLOG_FORMAT = STATEMENT. %sFataler Fehler: %sRelaylog-Lesefehler: %sRelaylog-Schreibfehler: %sErzeugen von %s fehlgeschlagenMaster-Befehl %s fehlgeschlagen: %sBinärlogging nicht möglich. Meldung: %sView `%-.64s`.`%-.64s` hat keinen ErzeugungskontextErzeugungskontext des Views`%-.64s`.`%-.64s' ist ungültigErzeugungskontext der gespeicherten Routine`%-.64s`.`%-.64s` ist ungültigBeschädigte TRG-Datei für Tabelle `%-.64s`.`%-.64s`Trigger für Tabelle `%-.64s`.`%-.64s` haben keinen ErzeugungskontextTrigger-Erzeugungskontext der Tabelle `%-.64s`.`%-.64s` ist ungültigErzeugungskontext des Events `%-.64s`.`%-.64s` ist ungültigKann Tabelle für den Trigger `%-.64s`.`%-.64s` nicht öffnenKann gespeicherte Routine `%-.64s` nicht erzeugen. Beachten Sie die WarnungenMehrdeutige Kombination von Slave-Modi. %sDer BINLOG-Anweisung vom Typ `%s` ging keine BINLOG-Anweisung zur Formatbeschreibung voran.Beschädigtes Replikationsereignis entdecktUngültige Spaltenreferenz (%-.64s) bei LOAD DATAZu bereinigende Logdatei %s wurde nicht gefundenXA_RBTIMEOUT: Transaktionszweig wurde zurückgerollt: ZeitüberschreitungXA_RBDEADLOCK: Transaktionszweig wurde zurückgerollt: Deadlock entdecktVorbereitete Anweisungen müssen noch einmal vorbereitet werdenDie DELAYED-Option wird für Tabelle '%-.192s' nicht unterstütztDie Master-Info-Struktur existiert nichtOption <%-.64s> ignoriertEingebaute Plugins können nicht gelöscht werdenPlugin wird verwendet und wird erst beim Herunterfahren deinstalliert%s Variable '%s' ist nur lesbar. Benutzen Sie SET %s, um einen Wert zuzuweisenSpeicher-Engine %s unterstützt für diese Anweisung kein Rollback. Transaktion wurde zurückgerollt und muss neu gestartet werdenUnerwartete Daten vom Heartbeat des Masters: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Fehlerhaftes Schema für mysql.ndb_replication table. Meldung: %-.64sFehler beim Parsen einer Konflikt-Funktion. Meldung: %-.64sSchreiben in Ausnahme-Tabelle fehlgeschlagen. Meldung: %-.128sKommentar für Tabelle '%-.64s' ist zu lang (max = %lu)Kommentar für Feld '%-.64s' ist zu lang (max = %lu)FUNCTION %s existiert nicht. Erläuterungen im Abschnitt 'Function Name Parsing and Resolution' im ReferenzhandbuchDatenbankTabellePartitionUnterpartitionTemporärUmbenanntZu viele aktive simultane TransaktionenNicht-ASCII-Trennargumente werden nicht vollständig unterstütztDebug Sync Point Wartezeit überschrittenDebug Sync Point Hit Limit erreichtInformationselement '%s' für DuplikatbedingungUnbehandelte benutzerdefinierte WarnbedingungUnbehandelte benutzerdefinierte Nicht-gefunden-BedingungUnbehandelte benutzerdefinierte AusnahmebedingungRESIGNAL bei nicht aktivem HandlerSIGNAL/RESIGNAL kann nur mit einer Bedingung (CONDITION) benutzt werden, die bei SQLSTATE definiert wurdeDaten gekürzt für Bedingungselement '%s'Daten zu lang für Bedingungselement '%s'Unbekannte Locale: '%-.64s'Die angeforderte Server-ID %d steht im Konflikt mit der Startoption --replicate-same-server-id für den SlaveAbfragen-Cache ist deaktiviert. Starten Sie den Server neu mit query_cache_type=1, um ihn zu aktivierenPartitionsfeld '%-.192s' ist ein DuplikatInkonsistenz bei der Benutzung von Spaltenlisten für PartitionierungPartitionsspaltenwerte sind vom falschen TypZu viele Felder in '%-.192s'MAXVALUE kann nicht als Wert in VALUES IN verwendet werdenFür den Partionierungstyp %-.64s darf es nicht mehr als einen Wert gebenZeilenausdrücke in VALUES IN sind nur für Mehrfeld-Spaltenpartionierung erlaubtFeld '%-.192s' ist für diese Art von Partitionierung von einem nicht zulässigen TypDie Gesamtlänge der Partitionsfelder ist zu großCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' ist veraltet und wird in einer zukünftigen Version entfernt werden.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerEin raumbezogener Index (SPATIAL) darf nur Spalten geometrischen Typs enthaltenComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTBenutzer '%-.48s'@'%-.64s' hat keine ZugriffsberechtigungSET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Kann %s.%s nicht einlesen. Tabelle ist wahrscheinlich beschädigtThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setDie partition '%-.64s' existiert nichtFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Fremdschlüssel-Beschränkung für Tabelle '%.192s', Datensatz '%-.192s' würde zu einem doppelten Eintrag in Tabelle '%.192s', Schlüssel '%.192s' führenFremdschlüssel-Beschränkung für Tabelle '%.192s', Datensatz '%-.192s' würde zu einem doppelten Eintrag in einer Kind-Tabelle führenSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Spaltenanzahl von %s.%s falsch. %d erwartet, aber %d gefunden. Tabelle ist wahrscheinlich beschädigtReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Kann Spalte '%-.192s' nicht löschen: wird für eine Fremdschlüsselbeschränkung '%-.192s' benötigtKann Spalte '%-.192s' nicht löschen: wird für eine Fremdschlüsselbeschränkung '%-.192s' der Tabelle '%-.192s' benötigtSpalte '%-.192s' kann nicht NOT NULL sein: wird für eine Fremdschlüsselbeschränkung '%-.192s' SET NULL benötigtDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDoppelter Eintrag für Schlüssel '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.Spaltenanzahl von %s.%s falsch. %d erwartet, aber %d erhalten. Erzeugt mit MySQL %d, jetzt unter %d. Bitte verwenden Sie die MySQL-Upgrade-Prozedur, um den Fehler zu beheben.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.Der Logfilter "%s" wunderte sich ueber "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�̦�greek/errmsg.sysnu�[���������u�N+���]�0�5�{	�	l
�
q�'i�
�
�
�0n#�y�M����%Z��n��3��Gm��$f�E��p�b�n��W���| � � Y!�!/"�"R#�#�#$5$l$�$�${%�%J&�&�&�'(@(�(�()W)�)*z*�*�*w+�+�,~-.�.�.C/~/�/10�0�0�1 2�2�334b4�45;5U5t5�5)6m6�6"7Q7w7�78*8n8�8�89,9F9_9�9�9�9:2:j:�:�:3;S;�;�;)<n<�<�<=N=�=�=�=%>b>�>�>�>�>??�?�?�?�?@2@e@�@�@!AjA�A-BB�B2C�C�C"DQD�D�DEGE�E�E�E%FhF�F�F�F1GUG|G�G�GHAH�H�H�H>I�I�IJ9JfJ�J�J�J/KwK�K�K�K LALwL�L�L�LM8MbM�MN6NiN�N�NO,O�O�O�O�OBP�P�P�PQPQQ�Q	R6R�R�RWS�S5T~T=UzU�U�U�U,VHV�V�V#WWW�W�W/X[X�XYGYfY�Y�Y�YZSZZ�Z�Z�Z�Z
[([<[W[~[�[�[\h\�\]=]U]t]�]�]�]�]^^/^S^�^�^�^�^�^�^_F_�_�_�_`0`g`�`�`+aba~a�a�a�a)b]b�b+csc�c1dcdzd�d�d�de=eKe�e�e�ef]ff�f�f�f-g?g\g�g�g�g�g;hMhh�h�hi>iTi�i�i�ijXj�j�j�j�jPk�k�klrl�l�lmm[m�m�m�m4nan�n�n5o�o�pKq�q�q7r�r�r�r=s�s�stmt�t2uzu�u�u[v�v�v�v�v'w�wx�x�xy�y�yzZz�z�z*{�{�{;|�|�|$}T}�}�}~9~f~�~�~�~�~W���\�����E�����R���Ղ�|���� ������'�_���˅�Y������O����+�o���ʈ�`�ʉ�C�h���Ɋ��g�ً�U�����ь��(�<�N���э)�=�p���+�J�������я��$�a�|�����1�]��������U�����'����d�����B�S������W�s���ޖ��/�P�����K�}��\���֙�[������ț��^�n�������֜��.�d���ӝ�P�������r���ʟ�,�u���Ѡ��=�p����C���� �S�����&�/�5�?�L�V�^�����ܤ��)�R�}���ɥ�/�U�n�̦�F�~���ŧ�4���ɨ���4�ߪ��6���>���@�����H���5�F���ݱ�B�~���ײ6���Գ�B�}���մ ���˵
�/�f����O���ӷm������W���պ
�>�T�p�C�*���˾��Y����/�/�������N�����1�m������H�j�������� �k���S��������P��������[�^�����������b�����8�����/������-�T���M���'�^����d��������5�#������������V�����O�f�}�!����_��������8�U�y��������0�Y�����W�����(�������;�����r�������������� �k����>���	�2�Q��������l�����!�B�j�D�����-�����D�}����M����R��������S�����5������?���o���2��&�V����F����A�����Q�{����L�_�~������2��Z���j��.W��:���4d���	+	R	}	�	
}
�
O�����!
�
�
�
b��U�R��L��3���k�L�^��4}��:��L��f�z�>��( L o � � � � :!g!�!�!\"�"�"%#I#�#G${$�$%M%�%�%&[&�&�&Q'l'�'I(�(�()M)�)�)*D*v*�*8+v+�+�+�+,L,�,�,�,�,-�-�-@.�.�/�/�/ 0Q0�0�0�011�1�1�2'3T3�3�344�4V5�5R6q6
77F7�7�7�7�7�7�8	9x9�9:D:n:�:�:�:
;5;8;U;k;�;�;�;<�<U=�=�=.>�>[?�?�?9@�@�A�A5B�B�B
C<CnC�C�C�CDADvD�D�DGEdE�E�EWF�FG�G�G�GH2HNH}H�HIEIpI�I�I%JuJ�J�J<KzK�K+L�L�LGM�M�M�M*NWN�N�N�N,OWOmOzO�O�O�O:P�P�P2QeQ�Q�QUR�R�RS|S�ST�TU�UWV�V�V�V%WtW�W�W)XsX�XVY�Y�YZvZ�Z[U[�[�[,\�\�\]F]~]�]%^Q^�^�^
_G_�_�_`3`g`�`aQaza�a�ab\b�b�bHc�cCd{d�d�d efe�e�edf�f�frg�g�g=hi�iQj�j�k�kl>lglyl�l�l	m$mCmcm�m�m�mn:nsn�n�no[o�o�o%p�p�pZq�q�q�qxr�r�r�s�slt�t�t�t.uku�u�u(vWv�v�vwFw�w�w�w=x�x"y0y�y�yz6zVz|z�z({b{�{�{E|�|�|�|�}Y~�~�~3Qc��O���������C���.�݄�o����5�a�Æ#�ɇ��F��q�̋�;���Ԍ]�����9�e���ʎ!�i�����[���K���ߑ$�s����F���l��?�������_�З��,�������4�m����h����w�֛�P�r����/���	��Šݡ	�V����-������+�o���ХR���ئ>��� ���)�a���Щ�$�����e���ʫ
�U�����W���ޭ:�[�}���ڮ�J���>��� ���������5�r�����Q�t�����+�x������`����+�������������"�c���
�Q����}�лI�k���*�Q���̽%�������G�d��������W����3�|����(�_���I������R������������R���-�R��r����g���$�}�����1�o��������:�r���7�������v����R���W���3������x���/������<�k���o���h�����������W�'�I��������I�������w�����+�^�������L�x��x�������G�����r������;����������9����5�h���)���t���w���������&���!�r�������t��m��a�����u�Z�Q�0���Ah���"~��"���4		�	R
�
��j�n
�
L�S�V�]��L��N��t�Z}���3�8Vz��>V��8���,���I � � 9!�!�!"^"�"�"�#$8$q$�$n%�%k&K'�'�'�'(C(R(d(�(�()2)w)�)*a*{*+S+{+�+,_,�,�,�,�,J-r-�-�-�- .C.r./�/�/�/030a0�0�0�0191f1j1�1�1�1R2�2�23v3�3�34c4�4�4�45g5�5�5�56F6h6�6�6V7�7�7n8�8�9�9:P:�:;O;�;*<�<=@=l=�=�=�=>2>n>�>T?�?S@�@A�A�ABBBzB�B�BXC}C�C�CVD�D�D	E0ENE|E�E�E�E�ERF�FG&G1G>GKGVG�G�GH*HKH]H�H�H�H%IZI�I�IJ2J�J�J�JK$K�K�K�K*L\L�L�L3N�N$OOO�OqPQ�Q�Q�Q�QRORwR�R�RS>S>T�T�TU2UdU�U�UV^V�V�V�V{W|X�X�X$Y�Y�YZ*ZVZ�Z�Z?[i[�[�[<\�\�\�\]7]\]�]�]�]0^M^�^�^
_6_c_�_�_`2`@`N`^`|`a0bLb�b�b�cyd�d�de2ete�e�e�e+f[f}f�f�fg+gZgmg�g�g�ghNh�h�hi.iMihi�i�i�ij8jej�j�j�jkHkkk�k�k�k-l`l�l�l�lm.mrm�mnLnn�n�n	o.oMoto�o�o�op7p�p�p"qrq�q*rpr�r�rgs�sgt�t%u�uvQv�v�xyKyz`z�z�z{:{~{�{|[|�|�|-}Q}�}r~@a��������^�u������B�`���ӂ�k�����9���"�w�݅E�������A�x����U����v����P�|�Ҋ�\���ԋ�:�$��������� �?�X�o�͐ؐې�d����D���6�����4�\���ƕ�)�`����������5�l���ڙT���К�=����A�s���ܜ.�u�ǝ�R���۞����{���٠�9�o�ȡ�;�����͢N�t�����8�b������U�����
�]���ݦ�d�����E���Ʃ��+�N�������C�x���ƫ	�G���Ȭ��b������
�9�~�Į)�A�f�����ί�5���S�q���Ʊ�a����E���״�7�������K�H�~���и�<������H�ƻD�Ƽ�*�1�k�ο��^�����	�����7�v���O�e������B�}���
�y�c�����n��Y���	����n�������������(�Z�������^�������V�������
�0�X��������C�r�����Y�������8�y���-�������A�q�����!��������p���I�v����B�{������6�����+����j������
�
�H�f��������=�����^����D�������>�`�������W����������h��������.�b������_����������=�]�������$�O�z�����?�����e�������
�1������.�W�������"�O����"�[�z��������8�n��������S�j���������/�b��������?�h������a������e�������m�����4�}������$�Z�������	�1�D����2�_��
�4����&�s����<���
��.��!W�I�n�>Y��$Q���8q��"u��C��/	i	�	�	
"
n
�
��Bd/
�
�
�
�
�
=��3��|�Mf��D�K�&�Y��Mm���O�U�%S��������,� 1 � !<!e!�!�!H"�"�"�"�"#�#$7$�$%=%%�%�%
&5&e&�&�&�&�&&'Q'	(U(�(�(%*`*d*�*�*�*/+�+$,�,�,-Q-�-�-.?.c.�.�./B/�/�/#0U0�0�01h1�1�1�12r2�23q3�3�3�3%4Y4�4�4�4
5C5�5�56t6�6�6 7E7i7�7�7E8e8�8�8�89W9�9�9�9,:2:�:�:�;�;n<�<V=u=�=�=>�>�>Z?�?�?0@{@�@�@IAaA�ACB�BuCDbD�D�D�D�D�D�D�D�D�DEJEME`E�EFAFDFnF�F�F�F�FGyGHLH�H
I=IWIuI�IJ9JbJ�J�J5K�K�KLDLyL�LJM�M�N.OkO�O�O�P�P)Q[QQ�Q�Q�Q!R<R}R�R�R�R SJSrS�S�S�S�S�STTMT�T�T�TU#URU{U�U�U
VVKV�V�V�VW0WRWwW�W�W�WLX�X�X�XFYtY�Y�Y-Z^ZxZ�Z�Z[G[e[�[�[\3\^\�\�\]]Z]�]�]�]$^M^�^�^_/_U_�_�_�_`3`M`e`�`�`(a�aXb�b�bcIc�c�c�cdGdud�d�d�dCe�e�e�ef=fXfxf�f�f�f�f6geg�g�g�gh?hch�h�h�h�h�hi,iWi�i�i&j)j�jkFkk�k�k�k�k�k�k%l�l�l�l;m~m�n6oso p�p�q rgr�r�r�r:s[sjs�s�s�s%tWt�t�t�tuGu�u�u�uvvMv�v�vwyw�w�w�wxxx=xsx�x�x�x1yYy�y�y
zJz}z�z�z{<{}{�{�{�{|?|c|�|�| }L}r}�}�}�}�}~1~[~u~�~�~�~.o����6�b���Ѐ-�>�h���9�����׃�&�X����I�|���Å4�7�{���Ć��&�����
��H���Ή�4�b�����Ŋފ�8�Q�m���֋�.�H�l�����Ռ=�o�Í��d�ߎj���܏Đ�v�
����U���� �K�E�˕U�v���ؖ'�Q������<�u����?�v����!�o���Ț1���ɛ:������՝'���О�e�˟'���
�s��b�٢����P���8�Y���!���Ǧ��Q�x����1�r�����W����`�����Ы:�ۭe���ͮ�S�~����Q���Ű�+�y������@����z���L�{�ڵP��K�Ƿm��8����M������D�ҼR��b�¾���ҿ��1�U���	�n���c���>�e���C�����d���s��������<�r������{���3������C�������}���2�����F���%��������E�z���K�����l����G�����^���P�����+�z����^�����S���
�����;������q������������R�����X�������G��������:���-�U����v�����4�h������<�r�����/�a����R�����1�y������>���$�Y���A�������I�����\���f���1�o����W�����3�|��H����2���>���z�;�����C�d����$�Q���	������X��>z^�u��#S���4Qx���2z��*����*b��	5	�	�	1
K
}
�
�
D���JW��
7
Z
�
�
�
Cqt��X����v��p�*b���Dp��2jmpsvy|������������������������������������������	x{~������������������������������ #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

qtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|��.x��Kn��GJ��)}�q � 
!I!�!�!�!#W$�$�$�$I%L%O%R%U%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&'''''''''' '#'&')','}'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'(((((((((( (#(&()(,(/(2(5(8(;(>(A(D(G(J(M(P(S(V(Y(\(_(b(e(h(k(n(q(t(w(z(}(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))
)
)))))))")%)()+).)1)4)7):)=)@)C)F)I)L)O)R)U)X)[)^)a)d)g)j)m)p)s)v)y)|))�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)9*<*?*B*E*H*K*N*Q*T*W*Z*]*`*c*f*i*l*o*r*u*x*{*~*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*++++�+�+�+,,,,,,, ,#,&,),,,/,2,5,8,;,>,A,D,G,J,M,P,S,�,�,�-�-F/�/�/�/[0�0�0�01O1�1�1�1�1�1!2\2�2�2d3�3�3�3!4e4�4�4k5�5�5�67�7S8V8Y8�8�8X9�9�9�9�9�9�9�9�9�9�9b:�:;h;�;�;2<b<�<�<�<=V=�=�=>Y>.?�?�?~@�@�@AAA A#A&A)A,A/A2A5A8A;A>AAADAGAJAMAPASAVAYA\A_AbAeAhAkAnAqAtAwAzA}A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�A�ABBB
B
BBBBBBB"B%B(B+B.B1B4B7B:B=B@BCBFBIBhBkBnB�B�B�B�B�B�B�B�B�B�B�B�B�B�B�B�BCCCCCCCCCC C#C&C)C,C/C2C5C8C;C>CACDCGCJCMCPCSCVCYC\C_CbCeChCkCnCqCtCwCzC}C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�CDDD
D
DDDDDDD"D%D(D+D.D1D4D7D:D=D@DCDFDIDLDODRDUDXD[D^DaDdDgDjDmDpDsDvDyD|DD�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�D�DEEE	EEEEEEEE!E$E'E�EF>F�F�F-G]G�G�GHIHyH�H�H�H	I:IiI�I�I.JIJnJ�J�J�JK/K`K�K�K�K-LXL�L�L�LM8M_M�M"NIN�N�NOFO�O�OfP�P�P�PQ9QYQ�Q�QYR�R�R�R�R�S�STTTT T#T&T)T,T/T2T�T�T�T�U�U�U�UVlV�V�V4W�XkY�Y�Y#Z�Z�[e\�\�\�\�\�\7]]^�^�_`6`\`�`�`�`�`�`�`�`�`�`�`�`aIasava�a�a�a�a�a�a%b(b+b.b1b4b7b:b=b@bCbFbIbLbObb�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b8c;cUcxc{cCdFdIdLdOdRdUdXd[d^dadddgdjdmdpdsdvd�d�d�e,f/f2f5f8ftf�f�f�f#g8gPg�g�g�g6h�h�h�h�h�h�h�h�h�h�h�hibieiqjtjwj�jDk�k�lm!n�n#o
p]prp�p�q7r�r�rsAstOt�t�t�t�tu6uQumu�uv<vgvuv�v=w�w�wxIxhx�x�x�x&y_y�y�ykz�z�z{n{�{|x|�|�|�|}<}]}z}�}�}~(~�~4����?�m����E���ā�l����k�����у��6����Є���8�;�x�����������������ą@�{�܆�M���A���!�J�����݉����+���+����.�u�ȍ�U��������-�[����O�w�����I���1���7�۔\�ϕI�~���"�p����=�d�g�ޘ'�@�_�����Й��ǚʚ�!�1�A�}����4�y���F���۝�N���ڞ%����"�a������ԡ<����;�r����]�ܤG�������e����D����:�a�ҩ
�(�Ϊ�S���ݫ�S�����P����7�n���Ю��g����$�@�U����%�s���̱��,�T�|����4�{��7����Q���$�ķ:���J�{�ʹ"����r�ͻ��(�>��������4����(�[������Z���ԿA�\�������7�V�������>������<�����E�������n���G���j�������H������E�j�������,�{����i�����*�i���"��=�h������7��������4�h���9�|����&�p�
���������������3�J����������R�u���]������������Q����@�����a���D��������}���)�����6����
�W�u���;���Y���B�E��������8�S�����~������������"�>�A�D�G�J�M�P�S�V�Y�\�_�b�e�h�k�n�q������j�m�p�s�v�y���
�/�c�����������=�v�����q�t�K�������,���%����G�������W����k��&�f����b����V��������������������� #&),/258;>ADG��I���j�)��PS�Ey���g���/��	C
�
�� 
�
B�������D�z��*Y����
R�Htb�^�e�"�C���� � A!"�"�"�#�$%�%*&�&�'
(j(�(
)@)�)*�*�+,�,4-S.�.�.3/�/*0�0(1�1?2e2h2�24�4m5
6|67�7�78F8|8�8�8�9�:�;�<�=5>�>t?+@�@�@%A@ATAnA�A�AZB�B�B�BCCCRCsC*D�E�E�E�E6FqF�F�F)G~G�G;H�H�HPI4K_KsM%N�N�N7O�O�OQ�Q�QJR�R�RyS�S�S�T]U�U�UV8VVV�V�V�V�VW�W�WLXOXRX:Y�YeZ�Z�Z([[[�[�[A\�\3]n]�]C^�^�^�_E`�`�a�b[c�c�c;dmd�d�de>ebe�e�e�efJfglg�gh<h�h�h�hi+i[i�i�i�jok1l�nWq�q�q�qrxr�r%s�s�s�sYt�t�u5v�v�wx\x�x�x0yAyjy.z1zz�z�zA{�{�{�{|6|i|�|�|�|})},}F}d}w}�}}~�~0���U�����������"�D�t�څM���A�����M����D���ۉ�k�Ċ����������u�����p��s�Ӑd��?���'�������>���
�@�z��"�U�~���˗�K�w����b�Ι6�����Z����i�������ǜߜ�"�-�C�f������.�`���˟;����%�Y��m�����ݣ�1�^�
����6�_�Ǧ������k�ө֩3���۪�ϫx�U��Y�hashchkisamchkΟΧΙΝΑΙΑδύνατη η δημιουργία του αρχείου '%-.200s' (κωδικός λάθους: %d - %s)Αδύνατη η δημιουργία του πίνακα '%-.200s' (κωδικός λάθους: %d - %s)Αδύνατη η δημιουργία της βάσης δεδομένων '%-.192s' (κωδικός λάθους: %d - %s)Αδύνατη η δημιουργία της βάσης δεδομένων '%-.192s'; Η βάση δεδομένων υπάρχει ήδηΑδύνατη η διαγραφή της βάσης δεδομένων '%-.192s'. Η βάση δεδομένων δεν υπάρχειΠαρουσιάστηκε πρόβλημα κατά τη διαγραφή της βάσης δεδομένων (αδύνατη η διαγραφή '%-.192s', κωδικός λάθους: %d - %s)Παρουσιάστηκε πρόβλημα κατά τη διαγραφή της βάσης δεδομένων (αδύνατη η διαγραφή του φακέλλου '%-.192s', κωδικός λάθους: %d - %s)Παρουσιάστηκε πρόβλημα κατά τη διαγραφή '%-.192s' (κωδικός λάθους: %d - %s)Αδύνατη η ανάγνωση εγγραφής από πίνακα του συστήματοςΑδύνατη η λήψη πληροφοριών για την κατάσταση του '%-.200s' (κωδικός λάθους: %d - %s)Ο φάκελλος εργασίας δεν βρέθηκε (κωδικός λάθους: %d - %s)Το αρχείο δεν μπορεί να κλειδωθεί (κωδικός λάθους: %d - %s)Δεν είναι δυνατό να ανοιχτεί το αρχείο: '%-.200s' (κωδικός λάθους: %d - %s)Δεν βρέθηκε το αρχείο: '%-.200s' (κωδικός λάθους: %d - %s)Δεν είναι δυνατό να διαβαστεί ο φάκελλος του '%-.192s' (κωδικός λάθους: %d - %s)Αδύνατη η αλλαγή του τρέχοντος καταλόγου σε '%-.192s' (κωδικός λάθους: %d - %s)Η εγγραφή έχει αλλάξει από την τελευταία φορά που ανασύρθηκε από τον πίνακα '%-.192s'Δεν υπάρχει χώρος στο δίσκο (%s). Παρακαλώ, περιμένετε να ελευθερωθεί χώρος... (κωδικός λάθους: %d - %s)Δεν είναι δυνατή η καταχώρηση, η τιμή υπάρχει ήδη στον πίνακα '%-.192s'Παρουσιάστηκε πρόβλημα κλείνοντας το '%-.192s' (κωδικός λάθους: %d - %s)Πρόβλημα κατά την ανάγνωση του αρχείου '%-.200s' (κωδικός λάθους: %d - %s)Πρόβλημα κατά την μετονομασία του αρχείου '%-.210s' to '%-.210s' (κωδικός λάθους: %d - %s)Πρόβλημα κατά την αποθήκευση του αρχείου '%-.200s' (κωδικός λάθους: %d - %s)'%-.192s' δεν επιτρέπονται αλλαγέςΗ διαδικασία ταξινόμισης ακυρώθηκεΤο View '%-.192s' δεν υπάρχει για '%-.192s'Ελήφθη μήνυμα λάθους %d - '%-.192s' από τον χειριστή πίνακα (table handler)Ο χειριστής πίνακα (table handler) για '%-.192s' δεν διαθέτει αυτή την επιλογήΑδύνατη η ανεύρεση εγγραφής στο '%-.192s'Λάθος πληροφορίες στο αρχείο: '%-.200s'Λάθος αρχείο ταξινόμισης (key file) για τον πίνακα: '%-.200s'; Παρακαλώ, διορθώστε το!Παλαιό αρχείο ταξινόμισης (key file) για τον πίνακα '%-.192s'; Παρακαλώ, διορθώστε το!'%-.192s' επιτρέπεται μόνο η ανάγνωσηΔεν υπάρχει διαθέσιμη μνήμη. Προσπαθήστε πάλι, επανεκινώντας τη διαδικασία (demon) (χρειάζονται %d bytes)Δεν υπάρχει διαθέσιμη μνήμη για ταξινόμιση. Αυξήστε το sort buffer size για τη διαδικασία (demon)Κατά τη διάρκεια της ανάγνωσης, βρέθηκε απροσδόκητα το τέλος του αρχείου '%-.192s' (κωδικός λάθους: %d - %s)Υπάρχουν πολλές συνδέσεις...Πρόβλημα με τη διαθέσιμη μνήμη (Out of thread space/memory)Δεν έγινε γνωστό το hostname για την address σαςΗ αναγνώριση (handshake) δεν έγινε σωστάΔεν επιτέρεται η πρόσβαση στο χρήστη: '%-.48s'@'%-.64s' στη βάση δεδομένων '%-.192s'Δεν επιτέρεται η πρόσβαση στο χρήστη: '%-.48s'@'%-.64s' (χρήση password: %s)Δεν επιλέχθηκε βάση δεδομένωνΑγνωστη εντολήΤο πεδίο '%-.192s' δεν μπορεί να είναι κενό (null)Αγνωστη βάση δεδομένων '%-.192s'Ο πίνακας '%-.192s' υπάρχει ήδηΑγνωστος πίνακας '%-.129s'Το πεδίο: '%-.192s' σε %-.192s δεν έχει καθοριστείΕναρξη διαδικασίας αποσύνδεσης του εξυπηρετητή (server shutdown)Αγνωστο πεδίο '%-.192s' σε '%-.192s'Χρησιμοποιήθηκε '%-.192s' που δεν υπήρχε στο group byΑδύνατη η ομαδοποίηση (group on) '%-.192s'Η διατύπωση περιέχει sum functions και columns στην ίδια διατύπωσηΤο Column count δεν ταιριάζει με το value countΤο identifier name '%-.100s' είναι πολύ μεγάλοΕπανάληψη column name '%-.192s'Επανάληψη key name '%-.192s'Διπλή εγγραφή '%-.192s' για το κλειδί %dΕσφαλμένο column specifier για το πεδίο '%-.192s'%s πλησίον '%-.80s' στη γραμμή %dΤο ερώτημα (query) που θέσατε ήταν κενόΑδύνατη η ανεύρεση unique table/alias: '%-.192s'Εσφαλμένη προκαθορισμένη τιμή (default value) για '%-.192s'Περισσότερα από ένα primary key ορίστηκανΠάρα πολλά key ορίσθηκαν. Το πολύ %d επιτρέπονταιΠάρα πολλά key parts ορίσθηκαν. Το πολύ %d επιτρέπονταιΤο κλειδί που ορίσθηκε είναι πολύ μεγάλο. Το μέγιστο μήκος είναι %dΤο πεδίο κλειδί '%-.192s' δεν υπάρχει στον πίνακαΠεδίο τύπου Blob '%-.192s' δεν μπορεί να χρησιμοποιηθεί στον ορισμό ενός κλειδιού (key specification)Πολύ μεγάλο μήκος για το πεδίο '%-.192s' (max = %lu). Παρακαλώ χρησιμοποιείστε τον τύπο BLOBΜπορεί να υπάρχει μόνο ένα auto field και πρέπει να έχει ορισθεί σαν key%s: σε αναμονή συνδέσεων
Version: '%s'  socket: '%s'  port: %d%s: Φυσιολογική διαδικασία shutdown
%s: Ελήφθη το μήνυμα %d. Η διαδικασία εγκαταλείπεται!
%s: Η διαδικασία Shutdown ολοκληρώθηκε
%s: Το thread θα κλείσει %ld  user: '%-.48s'
Δεν είναι δυνατή η δημιουργία IP socketΟ πίνακας '%-.192s' δεν έχει ευρετήριο (index) σαν αυτό που χρησιμοποιείτε στην CREATE INDEX. Παρακαλώ, ξαναδημιουργήστε τον πίνακαΟ διαχωριστής πεδίων δεν είναι αυτός που αναμενόταν. Παρακαλώ ανατρέξτε στο manualΔεν μπορείτε να χρησιμοποιήσετε fixed rowlength σε BLOBs. Παρακαλώ χρησιμοποιείστε 'fields terminated by'.Το αρχείο '%-.128s' πρέπει να υπάρχει στο database directory ή να μπορεί να διαβαστεί από όλουςΤο αρχείο '%-.200s' υπάρχει ήδηΕγγραφές: %ld  Διαγραφές: %ld  Παρεκάμφθησαν: %ld  Προειδοποιήσεις: %ldΕγγραφές: %ld  Επαναλήψεις: %ldΕσφαλμένο sub part key. Το χρησιμοποιούμενο key part δεν είναι string ή το μήκος του είναι μεγαλύτεροΔεν είναι δυνατή η διαγραφή όλων των πεδίων με ALTER TABLE. Παρακαλώ χρησιμοποιείστε DROP TABLEΑδύνατη η διαγραφή (DROP) '%-.192s'. Παρακαλώ ελέγξτε αν το πεδίο/κλειδί υπάρχειΕγγραφές: %ld  Επαναλήψεις: %ld  Προειδοποιήσεις: %ldYou can't specify target table '%-.192s' for update in FROM clauseΑγνωστο thread id: %luΔεν είσθε owner του thread %luΔεν χρησιμοποιήθηκαν πίνακεςΠάρα πολλά strings για το πεδίο %-.192s και SETΑδύνατη η δημιουργία unique log-filename %-.200s.(1-999)
Ο πίνακας '%-.192s' έχει κλειδωθεί με READ lock και δεν επιτρέπονται αλλαγέςΟ πίνακας '%-.192s' δεν έχει κλειδωθεί με LOCK TABLESΤα Blob πεδία '%-.192s' δεν μπορούν να έχουν προκαθορισμένες τιμές (default value)Λάθος όνομα βάσης δεδομένων '%-.100s'Λάθος όνομα πίνακα '%-.100s'Το SELECT θα εξετάσει μεγάλο αριθμό εγγραφών και πιθανώς θα καθυστερήσει. Παρακαλώ εξετάστε τις παραμέτρους του WHERE και χρησιμοποιείστε SET SQL_BIG_SELECTS=1 αν το SELECT είναι σωστόΠροέκυψε άγνωστο λάθοςΑγνωστη διαδικασία '%-.192s'Λάθος αριθμός παραμέτρων στη διαδικασία '%-.192s'Λάθος παράμετροι στην διαδικασία '%-.192s'Αγνωστος πίνακας '%-.192s' σε %-.32sΤο πεδίο '%-.192s' έχει ορισθεί δύο φορέςΕσφαλμένη χρήση της group functionΟ πίνακς '%-.192s' χρησιμοποιεί κάποιο extension που δεν υπάρχει στην έκδοση αυτή της MySQLΕνας πίνακας πρέπει να έχει τουλάχιστον ένα πεδίοΟ πίνακας '%-.192s' είναι γεμάτοςΑγνωστο character set: '%-.64s'Πολύ μεγάλος αριθμός πινάκων. Η MySQL μπορεί να χρησιμοποιήσει %d πίνακες σε διαδικασία joinΠολύ μεγάλος αριθμός πεδίωνΠολύ μεγάλο μέγεθος εγγραφής. Το μέγιστο μέγεθος εγγραφής, χωρίς να υπολογίζονται τα blobs, είναι %ld. Πρέπει να ορίσετε κάποια πεδία σαν blobsStack overrun στο thread:  Used: %ld of a %ld stack.  Παρακαλώ χρησιμοποιείστε 'mysqld --thread_stack=#' για να ορίσετε ένα μεγαλύτερο stack αν χρειάζεταιCross dependency βρέθηκε σε OUTER JOIN.  Παρακαλώ εξετάστε τις συνθήκες που θέσατε στο ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerΔεν είναι δυνατή η διαδικασία load για τη συνάρτηση '%-.192s'Δεν είναι δυνατή η έναρξη της συνάρτησης '%-.192s'; %-.192sΔεν βρέθηκαν paths για την shared libraryΗ συνάρτηση '%-.192s' υπάρχει ήδηΔεν είναι δυνατή η ανάγνωση της shared library '%-.192s' (κωδικός λάθους: %d %-.128s)Δεν είναι δυνατή η ανεύρεση της συνάρτησης '%-.128s' στην βιβλιοθήκηΗ συνάρτηση '%-.192s' δεν έχει ορισθείΟ υπολογιστής '%-.255s' έχει αποκλεισθεί λόγω πολλαπλών λαθών σύνδεσης. Προσπαθήστε να διορώσετε με 'mysqladmin flush-hosts'Ο υπολογιστής '%-.255s' δεν έχει δικαίωμα σύνδεσης με τον MySQL serverΧρησιμοποιείτε την MySQL σαν anonymous user και έτσι δεν μπορείτε να αλλάξετε τα passwords άλλων χρηστώνΠρέπει να έχετε δικαίωμα διόρθωσης πινάκων (update) στη βάση δεδομένων mysql για να μπορείτε να αλλάξετε τα passwords άλλων χρηστώνΔεν είναι δυνατή η ανεύρεση της αντίστοιχης εγγραφής στον πίνακα των χρηστώνRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192s'Invalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used.The host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionYou have an error in your SQL syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't existCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add a child row: a foreign key constraint failsCannot delete a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionΔιπλή εγγραφή '%-.64s' για το κλειδί '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTΔεν επιτέρεται η πρόσβαση στο χρήστη: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionΔιπλή εγγραφή για το κλειδί '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�YZ��hungarian/errmsg.sysnu�[�������	O��K��6u��
?y�	2d��
@fz��0W���:����G��
	!	N	o	�	�	�	�	+
R
u
�
�
9]����
'O~��'
Y
�
�
'=Zp��,��*H���K��(K`���2s��L\z���&M���Wd�L�
2g��:]�i��-�Ki�
I�z��F����O � � � !6!g!�!�!�!G"�"�"#=#z#�#�#2$�$�$%V%�%�%�%)&p&�&�&�&"'q'�'�'(*(H(d(�(�()S)�)�)_*�*+d+�+,T,�,�,�,6-y-�-�-
.W.�.�.�.(/c/�/�/�/�/20s0�0�01p1�1222k2�2�2�23a3�3�34.4R4s4�4�4�45>5j5�5�5:6h6�6�6�6F7^7�7�7�7(8t8�8�89A9�9�9�9;:h:�:�:�;<g<�<o=�=�=�=,>^>z>�>?U?�?�?,@a@�@A4AyA�A�A�ABAB�B�B�B�BC%C<CZCnC�C�C�CD8D�DE2EoE�E�E�E�E
FF6FIFaF�F�F�F�FGG+GHGxG�G�G
H5HbH�H�HI]I�I�I�IJ,J[J�JK]K�K'LcL�L�L�L�L!MBMoM}M�M�M#NIN�N�N�NO-O_OqO�O�O�OP#PmPP�P�P	QMQpQ�Q�Q�Q�QFR�R�R�R�R'S�S�STLT�T�TU5UHU�U�U�U/VfV�V�V#WgW%X�X}Y�YZiZ�Z�Z1[o[�[\@\�\�\d]�]�]^�^�^�^
_0_Y_�_5`�`a:a�a
bPb�b�b$c\c�c
dmd�deVe�e�ef7fkf�f�f�fggOg�g�g�gh�h�h.iwi�ijOj�j�jkMk�k�k!lRl�l�lmYm�m�m�mKn�n�n(oOo�o�op]p�p�p�p7q�q�q7rur�r�r�rsQs�stMt�t�t�tu+uZunu�u�uv[vov�v�v]w|w�w�w�wx.xVx�x�x�x(ycy�y�y�y�y2z�z�z�zY{�{J|�|�|}M}t}�}�}�} ~�~�~�~-a��&�K�}���K���́�G����4�����������Ʉ݄��#�R���ȅ��5�t���ۆ�9�������P���Ĉ��&�>�a���҉@�g�Ԋ�D�w���݋J�S�Y�c�p�z�������#�M�v���̍�,�S�y����A�j���̏��X����&���X����Z�֔b�ߕd�
����l�ԘY�j�Ǚ�<�f���ٚ��Z�����3�f�����D����1�S���Ş�W���۟u�����_���ݢ�F�\�x�K�2��Ӧ��a�ƨ'�7�7������V���Ѭ9�u����#�P�r���&���ͯ
�(�s���[���Ǳ���X����"���c�f�����������j����@�����7�����5�\�պU���/�f�ϼ�l�ƽ��߾�=�+�	�������"���'�^�����W�n���)����g�������$�@�]���������&�8�a�����_����0�������C�����z���#�����������(�s����F����:�Y��������t�����)�J�r�L�{���'�����>�w���
�G�����L��������M�����/������9�����i�����,��� �P�����@�{�	�;������K�u����F�Y�x����������,�����T�������d�������(�Q�����4��������.�^��������%�L�w�����w���I������������������
�\�����O����L����F����-������e�����F���X��.w��4��F���`�t�8��"Fi����4	a	�	�	V
�
�
C�Au�
G
�
�
U��Kf�C|�G��>p�2p���F������:����K���y���!N��.�P�Lk@~����� !r!�!�!>"h"~"�"�"#/#2#O#e#�#�#�#	$�$O%~%�%(&�&U'�'�'3(�(�)�)/*�*�*+6+h+�+�+�+,;,p,�,�,A-^-�-�-Q.�./�/�/�/0,0H0w0�0
1?1j1�1�12o2�2�263t3�3%4�4�4A5�5�5�5$6Q6�6�6�6&7Q7g7t7z7�7�748�8�8,9_9�9�9O:{:�:;v;�;<�<=�=Q>�>�>�>?n?�?�?#@m@�@PA�A�ABpB�BCOC�C�C&D�D�DE@ExE�EFKF�F�FGAG�G�GH-HaH�H�HKItI�I�IJVJ�J�JBK�K=LuL�L�LM`M�M�M^N�N�NlO�O�O7PQ�QKR�R�S�ST8TaTsT�T�TUU=U]U{U�U�UV4VmV�V�V
WUW�W�WX�X�XTY�Y�Y�YrZ�Z�Zz[�[f\�\�\�\(]e]�]�]"^Q^�^�^_@_�_�_�_7`�`a*aza�ab0bPbvb�b"c\c�c�c?d�d�d�d�eSf�f�f-gKg]h�hIi}i�i
j�j�j=k�k(l�lmim�mn/n[n�no�o�p@qrkr�s�s5t�t�tWu�u�u3v_v�v�vwcw�w�wUx�xEy�y�yzmz�z�z@{�{f|�|9}�}~�~Y��&�������.�g����b����q�Ѓ�J�l����)��������׉�P���ۋ'�������%�i���ʍL���Ҏ8������#�[���ʑޑ����_���ē�O����Q���ؕ4�U�w���Ԗ�D���8�����������ݚ/�l����K�n�����%�r����
��Z����%���������������]����K���
�w�ʣC�e���$�K���ƥ�{�����A�^�������Q���ש-�v�����"�Y���C������L�y���������L�ð'�L���l�ǲ�a�ǳ�w�ݴ�+�i��������4�l�ɷ1������p�ջ�L�z�Q���-���y���r���)������6�e���i���b�����������Q�!�C��������C�������q�����%�X�������F�r���r�������A�����l�������5����������3�y���/�b���#���n���q����������� ����l��������n���g���[������o���T���K���*�������;�b������}��x��������������.�y���L�������d���h���F����M���P���
�W����F�����H�����n�Tw���-�2Pt��8Py��2���&���C��3	�	�	
X
�
�
�2k�h
�
eE���	=L^��,q�[u	Mu�Y����Dl���=l����-[���3`d���L��
p���]���a}��@b��P��h � �!�!"J"�"#I#�#$$$%:%f%�%�%�%&,&h&�&N'�'M(�()�)�)*<*t*�*�*R+w+�+�+P,�,�,-*-H-v--�-�-�-L.�./ /+/8/E/P/�/�/0$0E0W0|0�0�01T1�1�12,2�2�2�2	33�3�3�3$4V4�4�4-6}67I7�7k89�9�9�9�9:I:q:�:�:;8;8<~<�<
=,=^=�=�=	>X>�>�>�>u?v@�@�@A{A�AB$BPB}B�B9CcC�C�C6D|D�D�DE1EVE�E�E�E*FGF�F�FG0G]G�G�G
H,H:HHHXHvH	I*JFJ}J�J�KsL�L�LM,MnM�M�M�M%NUNwN�N�NO%OTOgO~O�O�OPHPP�P�P(QGQbQ�Q�Q�Q
R2R_R�R�R�RSBSeS�S�S�S'TZT{T�T�TU(UlU�UVFVyV�V�VW(WGWnW�W�W�W
X1X�X�XYlY�Y$ZjZ�Z�Za[�[a\�\]�]^K^�^�`
aEa�aZb�b�bc4cxc�cdUd|d�d'eKe�elfg:g[g�gh�h�h�hiXioi�i�i�i<jZj�j�jkek�k�k
l3l�lmqm�m?n�n�n�no;oro�o�oOp�p�ppq�q
rJrvr�rsVs�s�s�s4tu�u�v{w�w�wx9xRxix�x�x�xy^y�yz>z�z0{�{�{.|V|�|�}�}#~Z~�~�~�~����/�f���ԁN���ʂ�7���	�;�m���ք(�o�����L���Ն����u���ӈ�3�i��5�����ǊH�n���܋��2�\�����	�O�~����W���׎
�^�ߏ���?�������%�H�������=�r������A�����\�������3�x���#�;�`�{���ȗ�/���M�k�������[����?���ќ�1���	����E�B�x���ʠ�6������B���>����$�+�e�ȧ�X����������1�p���I�_����
�<�w����s�]�����h��S�������h�����������"�T�����Ƕ�X������P���¸ָ�*�R�������=�l����S������2�s�̼'���ʽ��;�k�����z���Կ�j��C�p���<�u������0�����%����d��������B�`��������7�����X���	�>�������8�Z�������Q����������b�������
�(�\�������Y����������7�W��������I�t�����9�����_�|������+������(�Q��������I�y����U�t���������2�h��������M�d�{�������)�\��������9�b������[������_���������g�������.�w������	��T�~��������+�>�����,�Y����.����� �m�����6�������(������Q���C����h���	�8�S������K�������2�k������o�����=�����)�c��������h����|���<�^�)����������7�����-����
�v���G�`����>���E���� ���S�{��G�g����I�O�M{�������&y��+�	6	_	�	�	B

�
�
�
	��1�
7
y
�
�
/_���� KO��Z^���)�{�	K��9]��<��O��b���l�
k���S���=��n��?c��? _ � � � !Q!�!�!�!&","�"�"�#�#h$�$P%o%�%�%&|&�&T'�'�'*(u(�(�(C)[)�)=*�*o+�+\,�,�,�,�,�,�,�,�,�,-D-G-Z-�-�-;.>.h.�.�.�.�./s/0F0�0171Q1o1�1232\2�2�2/3�3�34>4s4�4D5�5�6(7e7�7�7�8�8#9U9y9�9�9�9:6:w:�:�:�:;D;l;�;�;�;�;�;<<G<~<�<�<==L=u=�=�=>>E>>�>�>
?*?L?q?�?�?�?F@�@�@�@@AnA�A�A'BXBrB�B�BCAC_C�C�CD-DXD�D�DEETE�E�E�EFGF�F�FG)GOG|G�G�GH-HGH_HzH}H"I�IRJ�J�J�JCK�K�K�KLALoL�L�L�L=M�M�M�MN7NRNrN�N�N�N�N0O_O}O�O�O	P9P]P�P�P�P�P�P�P&QQQ�Q�Q R#R�RS@SyS�S�S�S�S�S�ST�T�T�T5UxU�V0WmWX�X�YZaZZ�Z�Z4[U[d[�[�[�[\Q\�\�\�\	]A]z]�]�]^^G^�^�^_s_�_�_�_�_``7`m`�`�`�`+aSa�a�abDbwb�b�bc6cwc�c�c�cd9d]d�d�deFele�e�e�e�ef+fUfof�f�f�f(gig�g�g�gh0h\h�h�h'i8ibi�i�j3k�k�k�k	l lRl�l�lCmvm�m�m.n1nun�n�n�n o�o�pqqBq�q�q	r.r\r{r�r�r�rs2sKsgs�s�st(tBtft�t�t�t7uiu�u�u^v�vdw�w�w�xypyz�z�zO{�{�{|E|?}�}O~p~�~�~!K���6�o�|���9�p�����i���+���Ã4������υ!�{�ʆ��_�Ň!����m��\�ӊ�����J���2�S�{��������K�r�����+�l�����Q���
�Z�����ʓ4�Օ_���ǖ�M�x����K�|�����%�s������:����t��F�u�ԝJ��E���g���2���	�G�}����>�̤L�ۥ\������̧�+�O����h�©�]�ɪ8�_�̫=����^���m���خ���6�l�������u��-�y����=����ٳw�д,�~���@�������Ը
�?�t�ӹE����f�ѻ�A����X���J�����%�t����X����M��������5������k������������L�����R�|�����A��������4���'�O�|���p�����.�b�������6�l�����)�[����L�����+�s������8����S���;�������C�}���V���`���+�i�����Q�����-�v���B�����,���8���t�5�����	�=�^������K����y��������R������8�t�����X����o������M����������.�K�r���������,�t�������$��������$�\�������/�����+�E�w�����>�~������D�Q�������1�T������=�k�n�������R�|�����p����j��$�\������
�>�j���	�,��d�g�j�m�p�s�v�y�|������������������������������������������������������������������������r�u�x�{�~��������������������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

knqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy��(r����Eh��AD��#w�k�	C	�	�	�	Q���C
F
I
L
O
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
����������������������� #&w������������������ #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������369<?BEHKNQTWZ]`cfilorux{~�������������������������������������������{~� #&),/258;>ADGJM����@z��U���I�����V��^���_��e����M P S � � R!�!�!�!�!�!�!�!�!�!�!\"�"#b#�#�#,$\$�$�$�$
%P%�%�%
&S&('�'�'x(�(�())))) )#)&))),)/)2)5)8);)>)A)D)G)J)M)P)S)V)Y)\)_)b)e)h)k)n)q)t)w)z)})�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)***
*
*******"*%*(*+*.*1*4*7*:*=*@*C*b*e*h*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*++++++++++ +#+&+)+,+/+2+5+8+;+>+A+D+G+J+M+P+S+V+Y+\+_+b+e+h+k+n+q+t+w+z+}+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,
,
,,,,,,,",%,(,+,.,1,4,7,:,=,@,C,F,I,L,O,R,U,X,[,^,a,d,g,j,m,p,s,v,y,|,,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---	--------!-�-.8.�.�.'/W/�/�/0C0s0�0�0�0141c1�1�1(2C2h2�2�2�23)3Z3�3�3�3'4R4�4�4�4525Y5�56C66�6
7@7�7�7`8�8�8�8939S9�9�9S:�:�:�:�:�;�;<<<<<< <#<&<)<,<�<�<�<�=�=�=�=>f>�>�>.?�@eA�A�AB�B�C_DzD�D�D�D�D1EWF�F�GH0HVH�H�H�H�H�H�H�H�H�H�H�H�HCImIpI�I�I�I�I�I�IJ"J%J(J+J.J1J4J7J:J=J@JCJFJIJyJ|JJ�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J2K5KOKrKuK=L@LCLFLILLLOLRLULXL[L^LaLdLgLjLmLpL�L�L�M&N)N,N/N2NnN�N�N�NO2OJO�O�O�O0P�P�P�P�P�P�P�P�P�P�P�PQ\Q_QkRnRqR�R>S�S�T�TV�VWXWXlX�X�Y1Z�Z�Z[;[�[I\�\�\�\�\]0]K]g]�]^6^a^o^�^7_�_�_`C`b`�`�`�` aYa�a�aeb�b�bchc�cdrd�d�d�de6eWete�e�e�e"f�f.g�g�g�gh9hgh�h�h?i�i�i�ifj�jkek�k�k�k�k�k0lyl�l�l�lm2m5mrm�m�m�m�m�m�m�m�m�m:nun�noGo�o;p�pqDq~q�q�q
r�r�r%s�s%t�tu(uou�uvOv�v�w�w�w'xUx�x�xIyqy�y�yCz{z+{�{1|�|V}�}C~x~�~j���7�^�a�؀!�:�Y�{���ʁ����Ă��+�;�w����.�s��	�@���Յ�H���Ԇ�|���[������Ή6�����5�l����W�֌A��������_�����>����4�[�̑�"�Ȓ�M���ד	�M�����J���ޕ1�h���ʖ���a�����:�O���ߘ�m���ƙ���&�N�v���ܚ.�u��1����K������4���D�u�ġ����l�ǣ��"�8�����ܤ��.�����"�U������T���Χ;�V�ƨ|�����1�P������8�}�ϫ�6����?���ݭ��h�ɮA���d������B���ڱ�?�d�����Ĳ&�u�³�c����$�c����
�7�b�y���ݷ1��������.�b���3�v���� �j����Ƚ������~�ֿ�-�D����������L�o���W������������K����:�����[���>����{���w���#�|���0�y����Q�o���5���S���<�?��������2�M�����x��������������8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b�e�h�k�����
�d�g�j�m�p�s����)�]����������7�p�����k�n�E��������&��������A�������Q����e��� �`����\�����P��������������������������������������������� �#�&�)�,�/�2�5�8�;�>�A�~����C��������d���#�����J�M���?��s�������a��������)�����=����������<�����	�����������>��t�����$S����L��Bn\��X�_��=�����;	
�
�
��
�
$��d�:����.M��-�$�"�9_b��gv�� @ v � � �!�"�#�$�%/&�&n'%(�(�():)N)h)�)�)T*�*�*�*+=+L+m+$,z-�-�-�-0.k.�.�.#/x/�/50�0�0J1.3Y3m56�6�617�7�79�9�9D:�:�:s;�;�;�<W=�=�=>2>P>�>�>�>�>�>�?�?F@I@L@4A�A_B�B�B"CUC�C�C;D�D-EhE�E=F�F�F�G?H�H�I�JUK�K�K5LgL�L�LM8M\M�M�M�MNDNOfO�O
P6P|P�P�P�P%QUQ�Q�Q�RiS+T�VQYzY�Y�YZrZ�Z[[�[�[S\�\�]/^�^{_`V`�`�`*a;ada(b+byb�b�b;c�c�c�cd0dcd�d�d�d�d#e&e@e^eqe�ewf�f*g}g�giOj�jyl�l�l�l�lm>mnm�mGn�n;o�o�oGp�p�p>q�q�qrer�r�r�s�su�uvvov�v�vjw�wmx�x^y�y9z~z!{�{�{�|}8}�}~:~t~�~Ox���E�q����\�ȁ0����T����c���������ل���'�=�`��������(�Z���Ň5�����S��g��y���׋��+�X������0�Y����������e�͑Б-���Ւ�ɓr�O��S�hashchkisamchkNEMIGENA '%-.200s' file nem hozhato letre (hibakod: %d - %s)A '%-.200s' tabla nem hozhato letre (hibakod: %d - %s)Az '%-.192s' adatbazis nem hozhato letre (hibakod: %d - %s)Az '%-.192s' adatbazis nem hozhato letre Az adatbazis mar letezikA(z) '%-.192s' adatbazis nem szuntetheto meg. Az adatbazis nem letezikAdatbazis megszuntetesi hiba ('%-.192s' nem torolheto, hibakod: %d - %s)Adatbazis megszuntetesi hiba ('%-.192s' nem szuntetheto meg, hibakod: %d - %s)Torlesi hiba: '%-.192s' (hibakod: %d - %s)Nem olvashato rekord a rendszertablabanA(z) '%-.200s' statusza nem allapithato meg (hibakod: %d - %s)A munkakonyvtar nem allapithato meg (hibakod: %d - %s)A file nem zarolhato. (hibakod: %d - %s)A '%-.200s' file nem nyithato meg (hibakod: %d - %s)A(z) '%-.200s' file nem talalhato (hibakod: %d - %s)A(z) '%-.192s' konyvtar nem olvashato. (hibakod: %d - %s)Konyvtarvaltas nem lehetseges a(z) '%-.192s'-ba. (hibakod: %d - %s)A(z) '%-.192s' tablaban talalhato rekord megvaltozott az utolso olvasas otaA lemez megtelt (%s). (hibakod: %d - %s)Irasi hiba, duplikalt kulcs a '%-.192s' tablaban.Hiba a(z) '%-.192s' zarasakor. (hibakod: %d - %s)Hiba a '%-.200s'file olvasasakor. (hibakod: %d - %s)Hiba a '%-.210s' file atnevezesekor '%-.210s'. (hibakod: %d - %s)Hiba a '%-.200s' file irasakor. (hibakod: %d - %s)'%-.192s' a valtoztatas ellen zarolvaSikertelen rendezesA(z) '%-.192s' nezet nem letezik a(z) '%-.192s'-hoz%d - '%-.192s' hibajelzes a tablakezelotolA(z) '%-.192s' tablakezelonek nincs ilyen opciojaNem talalhato a rekord '%-.192s'-benErvenytelen info a file-ban: '%-.200s'Ervenytelen kulcsfile a tablahoz: '%-.200s'; probalja kijavitani!Regi kulcsfile a '%-.192s'tablahoz; probalja kijavitani!'%-.192s' irasvedettNincs eleg memoria. Inditsa ujra a demont, es probalja ismet. (%d byte szukseges.)Nincs eleg memoria a rendezeshez. Novelje a rendezo demon puffermeretetVaratlan filevege-jel a '%-.192s'olvasasakor. (hibakod: %d - %s)Tul sok kapcsolatElfogyott a thread-memoriaA gepnev nem allapithato meg a cimbolA kapcsolatfelvetel nem sikerult (Bad handshake)A(z) '%-.48s'@'%-.64s' felhasznalo szamara tiltott eleres az '%-.192s' adabazishoz.A(z) '%-.48s'@'%-.64s' felhasznalo szamara tiltott eleres. (Hasznalja a jelszot: %s)Nincs kivalasztott adatbazisErvenytelen parancsA(z) '%-.192s' oszlop erteke nem lehet nullaErvenytelen adatbazis: '%-.192s'A(z) '%-.192s' tabla mar letezikErvenytelen tabla: '%-.129s'A(z) '%-.192s' oszlop %-.192s-ben ketertelmuA szerver leallitasa folyamatbanA(z) '%-.192s' oszlop ervenytelen '%-.192s'-benUsed '%-.192s' with wasn't in group byA group nem hasznalhato: '%-.192s'Statement has sum functions and columns in same statementAz oszlopban levo ertek nem egyezik meg a szamitott ertekkelA(z) '%-.100s' azonositonev tul hosszu.Duplikalt oszlopazonosito: '%-.192s'Duplikalt kulcsazonosito: '%-.192s'Duplikalt bejegyzes '%-.192s' a %d kulcs szerint.Rossz oszlopazonosito: '%-.192s'A %s a '%-.80s'-hez kozeli a %d sorbanUres lekerdezes.Nem egyedi tabla/alias: '%-.192s'Ervenytelen ertek: '%-.192s'Tobbszoros elsodleges kulcs definialas.Tul sok kulcs. Maximum %d kulcs engedelyezett.Tul sok kulcsdarabot definialt. Maximum %d resz engedelyezettA megadott kulcs tul hosszu. Maximalis kulcshosszusag: %dA(z) '%-.192s'kulcsoszlop nem letezik a tablabanBlob objektum '%-.192s' nem hasznalhato kulcskentA(z) '%-.192s' oszlop tul hosszu. (maximum = %lu). Hasznaljon BLOB tipust inkabb.Csak egy auto mezo lehetseges, es azt kulcskent kell definialni.%s: kapcsolatra kesz
Version: '%s'  socket: '%s'  port: %d%s: Normal leallitas
%s: %d jelzes. Megszakitva!
%s: A leallitas kesz
%s: A(z) %ld thread kenyszeritett zarasa. Felhasznalo: '%-.48s'
Az IP socket nem hozhato letreA(z) '%-.192s' tablahoz nincs meg a CREATE INDEX altal hasznalt index. Alakitsa at a tablatA mezoelvalaszto argumentumok nem egyeznek meg a varttal. Nezze meg a kezikonyvben!Fix hosszusagu BLOB-ok nem hasznalhatok. Hasznalja a 'mezoelvalaszto jelet' .A(z) '%-.128s'-nak az adatbazis konyvtarban kell lennie, vagy mindenki szamara olvashatonakA '%-.200s' file mar letezik.Rekordok: %ld  Torolve: %ld  Skipped: %ld  Warnings: %ldRekordok: %ld  Duplikalva: %ldRossz alkulcs. A hasznalt kulcsresz nem karaktersorozat vagy hosszabb, mint a kulcsreszAz osszes mezo nem torolheto az ALTER TABLE-lel. Hasznalja a DROP TABLE-t helyetteA DROP '%-.192s' nem lehetseges. Ellenorizze, hogy a mezo/kulcs letezik-eRekordok: %ld  Duplikalva: %ld  Warnings: %ldYou can't specify target table '%-.192s' for update in FROM clauseErvenytelen szal (thread) id: %luA %lu thread-nek mas a tulajdonosaNincs hasznalt tablaTul sok karakter: %-.192s es SETEgyedi log-filenev nem generalhato: %-.200s.(1-999)
A(z) '%-.192s' tabla zarolva lett (READ lock) es nem lehet frissiteniA(z) '%-.192s' tabla nincs zarolva a LOCK TABLES-szelA(z) '%-.192s' blob objektumnak nem lehet alapertelmezett ertekeHibas adatbazisnev: '%-.100s'Hibas tablanev: '%-.100s'A SELECT tul sok rekordot fog megvizsgalni es nagyon sokaig fog tartani. Ellenorizze a WHERE-t es hasznalja a SET SQL_BIG_SELECTS=1 beallitast, ha a SELECT okayIsmeretlen hibaIsmeretlen eljaras: '%-.192s'Rossz parameter a(z) '%-.192s'eljaras szamitasanalRossz parameter a(z) '%-.192s' eljarasbanIsmeretlen tabla: '%-.192s' %-.32s-banA(z) '%-.192s' mezot ketszer definialtaA group funkcio ervenytelen hasznalataA(z) '%-.192s' tabla olyan bovitest hasznal, amely nem letezik ebben a MySQL versioban.A tablanak legalabb egy oszlopot tartalmazni kellA '%-.192s' tabla megteltErvenytelen karakterkeszlet: '%-.64s'Tul sok tabla. A MySQL csak %d tablat tud kezelni osszefuzeskorTul sok mezoTul nagy sormeret. A maximalis sormeret (nem szamolva a blob objektumokat) %ld. Nehany mezot meg kell valtoztatniaThread verem tullepes:  Used: %ld of a %ld stack. Hasznalja a 'mysqld --thread_stack=#' nagyobb verem definialasahozKeresztfuggoseg van az OUTER JOIN-ban. Ellenorizze az ON felteteleketTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerA(z) '%-.192s' fuggveny nem toltheto beA(z) '%-.192s' fuggveny nem inicializalhato; %-.192sNincs ut a megosztott konyvtarakhoz (shared library)A '%-.192s' fuggveny mar letezikA(z) '%-.192s' megosztott konyvtar nem hasznalhato (hibakod: %d %-.128s)A(z) '%-.128s' fuggveny nem talalhato a konyvtarbanA '%-.192s' fuggveny nem definialtA '%-.255s' host blokkolodott, tul sok kapcsolodasi hiba miatt. Hasznalja a 'mysqladmin flush-hosts' parancsotA '%-.255s' host szamara nem engedelyezett a kapcsolodas ehhez a MySQL szerverhezNevtelen (anonymous) felhasznalokent nem negedelyezett a jelszovaltoztatasOnnek tabla-update joggal kell rendelkeznie a mysql adatbazisban masok jelszavanak megvaltoztatasahozNincs megegyezo sor a user tablabanMegegyezo sorok szama: %ld  Valtozott: %ld  Warnings: %ldUj thread letrehozasa nem lehetseges (Hibakod: %d). Amenyiben van meg szabad memoria, olvassa el a kezikonyv operacios rendszerfuggo hibalehetosegekrol szolo reszetAz oszlopban talalhato ertek nem egyezik meg a %ld sorban szamitott ertekkelNem lehet ujra-megnyitni a tablat: '%-.192sA NULL ervenytelen hasznalata'%-.64s' hiba a regularis kifejezes hasznalata soran (regexp)A GROUP mezok (MIN(),MAX(),COUNT()...) kevert hasznalata nem lehetseges GROUP BY hivatkozas nelkulA '%-.48s' felhasznalonak nincs ilyen joga a '%-.255s' host-on%-.128s parancs a '%-.48s'@'%-.64s' felhasznalo szamara nem engedelyezett a '%-.64s' tablaban%-.16s parancs a '%-.48s'@'%-.64s' felhasznalo szamara nem engedelyezett a '%-.192s' mezo eseten a '%-.192s' tablabanErvenytelen GRANT/REVOKE parancs. Kerem, nezze meg a kezikonyvben, milyen jogok lehetsegesekA host vagy felhasznalo argumentuma tul hosszu a GRANT parancsbanA '%-.192s.%-.192s' tabla nem letezikA '%-.48s' felhasznalo szamara a '%-.255s' host '%-.192s' tablajaban ez a parancs nem engedelyezettA hasznalt parancs nem engedelyezett ebben a MySQL verziobanSzintaktikai hibaDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useMegszakitott kapcsolat %ld db: '%-.192s' adatbazishoz, felhasznalo: '%-.48s' (%-.64s)A kapott csomag nagyobb, mint a maximalisan engedelyezett: 'max_allowed_packet'Olvasasi hiba a kapcsolat soranHiba a fcntl() fuggvenybenHelytelen sorrendben erkezett adatcsomagokA kommunikacios adatcsomagok nem tomorithetok kiHIba a kommunikacios adatcsomagok olvasasa soranIdotullepes a kommunikacios adatcsomagok olvasasa soranHiba a kommunikacios csomagok irasa soranIdotullepes a kommunikacios csomagok irasa soranEz eredmeny sztring nagyobb, mint a lehetseges maximum: 'max_allowed_packet'A hasznalt tabla tipus nem tamogatja a BLOB/TEXT mezoketA hasznalt tabla tipus nem tamogatja az AUTO_INCREMENT tipusu mezoketINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESErvenytelen mezonev: '%-.100s'A hasznalt tablakezelo nem tudja a '%-.192s' mezot indexelniA MERGE tablaban talalhato tablak definicioja nem azonosA '%-.192s' nem irhato, az egyedi mezok miattBLOB mezo '%-.192s' hasznalt a mezo specifikacioban, a mezohossz megadasa nelkulAz elsodleges kulcs teljes egeszeben csak NOT NULL tipusu lehet; Ha NULL mezot szeretne a kulcskent, hasznalja inkabb a UNIQUE-otAz eredmeny tobb, mint egy sort tartalmazAz adott tablatipushoz elsodleges kulcs hasznalata kotelezoEzen leforditott MySQL verzio nem tartalmaz RAID support-otOn a biztonsagos update modot hasznalja, es        WHERE that uses a KEY column. %sA '%-.192s' kulcs nem letezik a '%-.192s' tablabanNem tudom megnyitni a tablatA tabla kezeloje (handler) nem tamogatja az %sAz On szamara nem engedelyezett a parancs vegrehajtasa a tranzakcioban%d - '%-.192s' hiba a COMMIT vegrehajtasa soran%d - '%-.192s' hiba a ROLLBACK vegrehajtasa soran%d hiba a FLUSH_LOGS vegrehajtasa soran%d hiba a CHECKPOINT vegrehajtasa soranAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add a child row: a foreign key constraint failsCannot delete a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDuplikalt bejegyzes '%-.64s' a '%-.385s' kulcs szerint.Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTA(z) '%-.48s'@'%-.64s' felhasznalo szamara tiltott eleres.SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setA '%-.64s' partition nem letezikFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDuplikalt bejegyzes a '%-.192s' kulcs szerint.Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\q��e�e�italian/errmsg.sysnu�[�����Q��L���5��.e��C{��<��
H��*U��� `���L���#	<	�	�	�	�	*
I
j
�
�
�
�
!G��%Eq����
7
a
�
�
l��6Lt���P��Nl��L��[v���$t��5���%Qy�� Hf���L����$F���Y��\��}��	#��&��/ W � � !\!|!�!�!7"U"v"�"�" #Y#�#�#$U$�$�$%b%�%&�&�&�&$'�'�'�'(D(w(�(�()[)�)�)�)*D*m*�*+;+�+�+^,-g-�-&.�.�.$/W/�/�/.0{0�0�01}1�1�1N2�2�2/3^3�3�3�3/4�4�4�4I5�56E6�6�67>7p7�7�7#8V8�8�8�8�8*9I9n9�9�9�9+:�:�:�:;-;�;�;<0<Q<~<�<=F=p=�=�=>J>�>�>?.?�?e@�@A�AB!BBB�B�B�B=CYC�C�C/D�D�D�D\E�E�E�EF@FrF�F�FG<GQGfG{G�G�G�G�GHBHgH�H�HhI�I�I�I�IJ?J`JuJ�J�J�J�JK'K>KVKkK�K�K�KLALcL�L�L�L)MkM�M�MN(N]N�N�N�NeO�O�O}P�P�PQQHQwQ�Q�Q�QRDRyR�R�RS=SbS�S�S�S�ST-TXTyT�T�TU4U_U�U�U�UV4VNV�V�VW/WFW}W�WXpX�X�X/YbY�Y�Y�YZOZ�Z�Z�ZL[y[�[{\@]�]M^u^�^
_F_�_�_`f`�`�`Ta�ab@bXb�b
c'ccc�c�c;d�d1eqe�efcf�f�f0gzg�gh`h�h7iXi�i�i+jWj�j�j�jkPkZkdk�k�k,lQlml�l%m�m�m'nnn�n�no]o�op5pwp�pq4qiq�q�q!rSr�r�rs~s�s�sFtst�t�tuRu�u�uRv�v�v�vwQwrw�w�wax�x�xy7yYy�y�y�y�yzYz�z�z�z2{�{�{|'|G|Y|�|�|�|}$}~}�}�}~*~H~�~�~A�@����>�l���ʁہ
�&�v�߂��:�f�����؃�|���ӄ����"�^���φ����<�l�҈����-�J�s���؉�G���Ċ��+�a�����>�`�����E�v������"�����$�`���Ǐ��-�����������ʐҐ��0�P�s���Ƒ��=�|���ɒ�@�������9�c�����=�v����S����&���/���Z���V���$������Q������)�K�����H�������I����?�����ڢ�W����'���c��R����)�^�����ħ��~�L������s�����ٯ�?���ڰ�������3�o������r�ӳ�V�t���
�����D�n����@�w���������S�t��]�����F����P�����B�m�����*��������$�t����Q�4�r�����^����:�w�<�|�����0�������~��e�����?�T�y���������%�8�{�������N����\������M�����Q����x��������:�}���1�e���6�f�������!�C�t����E�~���������4�v����������\�����L�����E�b�������~����^���-�1���"�7�{�=�o�����N�����X�����4�W�������_�������?�2���+�`�{���8������A����� �M�w�����4������1�W�}������&�O�t�����M��G�������9�h���j����\����*�O����f����(����@�|���F�N�U�]�6}��?��h��	K	�	�	e
�
'��4q����
/
�
�
�
�
��n�����d��'T��3��7��^��`�����+b����0`�D���1i��5P��"�p��, } !�!7"�"�"V#h#�#�#�#$)$F$%R%�%�%L&�&�&�&�&)'S'~'�'�'�'�'(4(X(%)�)�)B*w*,+�+�+9,�,1-�-*.~.�.5/V/�/�/�/070h0�0�0�01�1�1�1*2�2�2W3�3414Q4{4�4�4(5\5�5�5�56n6�6�6E7�7�7>8t8�839�9�9
:A:s:�:�:;D;u;�;�;�;�;�;:<�<�<!={=�=�=*>�>�>�>Z?�?@Z@�@PAB�B�B�B0CnC�CD<DrD�D5E�EF3FQF�F�FWG�G�G3HuH�HIZI�I�I�InJ�J�J"KVK�K�KLTL|L�L�LIM�M�MN8N]N�N�NBO�O�O�P�PQ5QiQ�Q�QDR�R�R<S�S�S8T�TaUV�VWX8XgX�X�X�X�X1YRYmY�Y�Y�Y�Y!ZZZ�Z�Z�Z4[\[�[�[!\n\�\�\�]�]^=^�^�^&_�_`�`�`aEawa�a�aCbqb�b�bcOc�c�cdAd�d6ekeye�efcff�f�f!gqg�g�g�g�h�h�h4i�i�j�j/k|k�k�l3m�m�mnYn�nJo�o�owp&qcq�q�qPr~r�rslst�t�ubv�vxIx�x�xy�y�y>z�z�z�z{j{�{�{>|�|B}�}�}(~m~�~�~0����;����P�ڂc����>�u��
�E�}����;����d����`������3�x��R�J��&�R���ڏ*�v�ϐ�L�t��������!�����i��r�����-�m��>�����S�����A����'�����ƚ��#�g��������i��/�ٞ�,�~����?������D�t����3�\�_����0�t���K�a�ۤ�D�k�����S����Y�Ƨ������s���թ�n�ʪ��F������f��>���ѭ&�|�Ů
�I�q�������ұa���Ȳ��/�b�f�߳A����v���M����_����m�Ƹ,�:�z����L�Һ8��������B��G���$�Z�������|�	���F����x����N�����*���������!�C�������p�����%�F�_�����������%�t�����+�������I���I���T�����*��������M������D���f�����>�~����r����,���C���#���)�o���j�����3�d�����2���1�����/�Z���J�������(�y���/�G��������P���k����L���k�����(�}��$���*��C����������M�4���G�����Y�����B���T�/��b�����F|
����"����	�	�	
-
u
�
^�7��5
�
�
d�
G�`�������$X����%O{�`��X��	f��$A���>i��g�#N|��T����!:��Y��% N � � !!Z!�!�!�!)"["�"�"�"@#�#�#$�$?%&-&Q&�&'`'�'�'s(�(d)�)�)�)*/*]*{*�*H+�+9,�,!-d-�-$.Z.�.�.�.)/�/�/�/0�0�01R1y1�1�1�1�12:2�2�2d3o3z3�3�3�3�34e4s4�4�4�4�4"5n5�5�536U6{6�6797X7m7�78?8s8�8!9:9|:�:m;�;�;�<Q=�=�=>?>e>�>�>�><?d?�?�@�@�@YA{A�A�A'BXB�B�BC:C�C�DE!EmE�EFUFsF�F�FG�G�G�G<H�H�H�H(I^I�I�I�I�IEJyJ�J�J@KVKK�K�K2LYL{L�L�L�L�LXMyN�N�NO�O�PQ9QaQ{Q�Q�Q%RGRtR�R�R�RSQStS�S�S�S�STUT�T�T+UKUwU�U�U�U	V5V\V�V�V�VW?WhW�W�W�WXDXvX�X�X�X(YZYwY�Y0ZcZ�Z�Z�Z5[R[w[�[�[�[\7\\\�\�\-]k]�]^s^�^�^:_�_(`�`�`na�abb�b4ceYe�eMf�f�fgQg�g�gh]h�h�h6ivi�ij�jbk�k�kl`l�l+mBm[m�m�m�mn0n�n�n�nogo�o�o.pYp�p�pkq�q&r�r�r	s;sds�s�stNt�t�t-u�u�u\v�v�vwcw�w�wxNx�xmy<z�z�{|5|i|�|�|�|}!}$}h}�}�}T~�~�~�G�}�����4�r�����+�7�^�P���5�~����#���ӆ�O����X������%�w����J����$�D�Z�Q�Č��"�9������e���Ў������Џ+�I�����Ր�X���͑
�S����&�Y���.�ܔd���ϕ�7�a�t���Ӗ�3�d�����ݗ�R�����8�e���ә�4�V���ǚ
�r�����ʛ���c�~������ڝ�J����<���٠ �Z���ۡX���2�����Ǥ��8������a�������:�s�z����C���ެ
�7�R��C�����������1�\���ư�S�±��޲����U���	�R��^���϶�9�]�a��8�q�����M��_�����:������%�S�y���ӽ�1�a������;���ѿ��:�����v���F�������0�j�����#�Q���"������Z�������"�T����'�t���W����A�P�S�V���������3�a�����,���1�X������4��������B��������`�9�������!�Y�w������K��������B�c���������2�m�������3����H�������2�V�z���(�]�w�����%�D�k�����E�k��������!�N��������-�e����������G�x������3�f�������#�f������c��������9�����,�}����Z���X�m��������:�R�z�����K�{����V�}���*�o����������S��Q�w����j���������W�����X�������8�m�������6�������1�k����C������x����'�I�k����`�������x�����6�`�����|���Y��&�W������0������ho`��4���7_��8n���3+	b	
c
?u�Kz
W
�
�
�
)���!;XM�6Q��/S~��
5Ho�R��9n���Cx�m�X��'_���!T��l��(a��?g�
\��# G n � � !4!V!�!�!3"e"�"�"?#i#�#�#�#E$�$�$�$%/%U%�%�% &C&u&{&�&'�'!(�(<)�)�)�)�)O*�*H+�+�+A,y,�,�,-�-�-.�./�/J0�0�0�0$1(1,1014181<1]1�1�1�12N2�2�2�2�23-3@3`3�3O4�45S5�5�5�5�5W6�6�6�617~7�78d8�8�89�9:�:w;�;�;<=G=r=�=�=�=�= >j>�>�>?&?G?i?�?�?�?�?@.@A@T@b@�@�@A3AUAlA�A�A�A/BVBgB�B�B�B=CYCyC�C�C�C	D4D�D�DE5E�E�EF-FvF�F�F�F7GUG�G�G�G*HZH|H�H�H�HWIgI�I�IJ?JmJ�J�JKUKxK�K�K�K,L]L|L�L�L�L�LqM�M�NO#OLO�O�OP/P_P�P�PQQEQ�Q�QR/R_R�R�R�R�RS%SGSS�S�S�S,TXT�T�T�T�TU9UAUKUuU�U�UVoVrV�VUW�W�W�WXXXX<XnX�XYEY�Y�Y�Z[�[i\+]=^i^�^�^_3_�_�_�_�_�_<`n`�`�`�`+aXa�a�ab2bPbgb�b�bcdc�c�c	d(dJdaddd�d�d�d
e?eze�e�efVf�f�f�fg]g�g�g�g�gheh�h�h�hiii�i�i�ij!j<jOjzj�j�j�jk/kwk�k�kl5l[ll�l�lmvm�m�m3n1o�o�o�o pXpop�p�p.q�q�q�qr}r�r�r�r
s>sostuVugu�u�uvXv}v�v�v�vw'wew�w�w�w�wxWxwx�x�x�xyy�y�yzEz�z({�{�{%|
}g}�}S~�~9��7�i������������!�p������1�����˄J�������0�j�����z�ׇ����`�ω�p�ʊ�M����p���S���6���"�T���K���ߐ����ʑj���6�`������J�z�����;�b���ޕY���ۖ	����$���њ�3���Ǜ�^���˜�J�t���W�����ܟO�àC���ġ#���8������L���ЦX���̧�;������*����b���A�z�����R����g�����������ݰ;�������'�D�e�����ܳ�N�Ĵ:�|�ȵ
�:���ݶ7�(�Ƹ�{�͹����n�/��#�\���ý"���ؾC��� �W����?���G������t����T�����-����V���0�����&�h����a���/���B�����!�������%���?���&�_���:�v�����J���
�E�}������I�������-�x�����`������z�����#�P���<�m���������A�����4���C�����z�����K�����B�|���(������{�����H��������X�������$�m�����R����2���^������U�����K�N����_����8�l������5�I�c�}��������%�L�{�����&�J�s����� �5�s������M�~���z�����F������'�b�������L��������*��������(�I�g������2����@���B�s����%Y��7X{c��������������������������

"%(+.147:=@CFILORU���������������������	?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_b������������������������ #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������Cw��KNQTWZ�	�	�	2
�
�
�
;r�8�3
S
�
�
#f���+��������������������� #&),/258;>ADG��������69<?BEHKNQTWZ]`cfiloru�!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(������������������������������������������	!$'*-0369<?BEHKNQT���TWZ]`cfilorux{~����������6�"���*��Cc����@j���� = j � � !�!
":"!#T#�#�$�$�$�$9%�%�%�%�%�%�%�%�%�%�%�%�&�&U'�'�'
({(�(�())\)�)*1*\*�*w+�+-,�,-*-`-c-f-i-l-o-r-u-x-{-~-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-.......... .#.&.).,./.2.5.8.;.>.A.D.G.J.M.P.S.V.Y.\._.b.e.h.k.n.q.t.w.z.}.�.�.�.�.�.�.�.�.�.�.//!/$/'/*/-/0/3/6/9/</?/B/E/H/K/N/Q/T/W/Z/]/`/c/f/i/l/o/r/u/x/{/~/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/0000000000 0#0&0)0,0/0205080;0>0A0D0G0J0M0P0S0V0Y0\0_0b0e0h0k0n0q0t0w0z0}0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0111
1
1111111"1%1(1+1.1114171:1=1@1C1F1I1L1O1R1U1X1[1^1a1d1g1j1m1p1�1_2�2�263v3�3�314a4�4�4	5(5A5R5�5�5�566w6�6�6�6777W7x7�7�7�798v8�8�8979W9�9�9:k:�:�:�:Y;�;�;3<�<�<=?=b=�=�=�=#>�>�>�>?=?�?@]@`@c@f@i@l@o@r@u@x@{@'AEAHA�A�ABBBcB�B�BC}C/E�E�EFlF$G,H�H�H�HI"I%I�I�JK<LaLL�L�LM.M1M4M7M:M=M@MCMFMIM�M�M�M�M�MNNANDNnNqNtNwNzN}N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�NOO�O�O�O�O�O�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P!Q$Q�QuRxR{R~R�R�R�RS6SlS�S�S�S	TETTUU!U$U'U*U-U0U3U6U9U[U�U�U�V�V�V�V�W)XYJYjZ�Zl[V\�\�\�\^�^_(_a_�_L`�`�`�`a.abaa�a�abQb�b�b�b�b�c�c:dWd�d�d�d	e8eoe�e�e&f�fg
gZg�g�g]h�h!i1i4i`i�i�i�i�i7jMjqj9k}k�kl,lcl�l�l�l+m�m�m
n<n�n�nUo�o�o�op4p7pp�p�pq@q^q�q�q�q�q�q�q�qrrr
r
r�r�r%sZs�s�s�tuju�u�u�u&vYv�v3wtw�wtx�xZywy�yzez�z{�{�{=|v|�|}4}�}�}�}~�~�~z���$������ǂ:�O�k����>�b�������'�p�����ʅ��І��2�j�z���Ƈ��2�}�3�X���
�$�_���Њ#�n�ˋ1�k����^�Ӎ���܎M������:���%�����c�ݒM�����N���ݔ=������S�q��P����&�X�����d�g���љ-�������=�L���ܛQ�m�����ޜ.�n���ݝ�J�`�u���Ş��+�}�ğT���ӡZ����m�
������ĥ�k���g����0�U�q�����+�H�}��K�q������h����������˭�K�����ܮ��;���̯�[���߰9���ӱ,�G������������<���޵)�^�����Ҷ��u�ķ�Z���
�9�s�����k�\�����Ȼ�,���B�E�H�K�}������ž��`�o���V���h���K�c���%�f�|������!��K�����E�������c��������g�����1���������c���A����r�������	�V����� ���������������.�f�������>��������D�G�J�k��������������������������������������3�\��������������S�x����������>�������H����������b���u���n���8�����@�������T���
�o����a�����N�����!�$�'�*�-�0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~����������������_������0�Q����r���8�����.���O�������C�������0�Q�x�����H���F�i�Q�"����D�X�������(��s��@V��K��T��I��g	�	�	k
�
��)�D
�
U�A�b s+�V��S��OE�h�}��|�sq����W  !�!S"�"`#�#0$f$�$�$%>%&'-()*~*'+�+t,�,-n-�-�-�-�-(.�.�./8/W/�/�/�/s0�1�1
2822�2�23r3�3#4�4�4F5�5}7�7�9n:�:;�;<8<_=�=>>�>�>?�?@2@A�AB8BcB�B�B	C>CBCFCJC�C9D�D�D�D�EF�F�F6GqG�G�G(H�HI|I�IJ�J�J2K�K�L:M�M�N�O�O!P�P�P�P(QcQ�Q�Q�QR&ReR�RbS�ST\T�T�T�TUJUtU�U�U)V�V�WzX8[�]�]�]-^_^�^!_n_�_`7`�`Ba�a~b$c�cdd�deeye�e�ewfzf�f�f<g�g�gh4h^hh�h�hi%iJiriui�i�i�ij�jkyk�k;lbm�n�n�p�p�p2qBqkq�q�q#r�r
s�s�s>t�t�t.u�u�u$vdv�v
w?w�w+xhy�y`zcz�z�z�z�{;|�|}�}+~�~�~p�5��Z����S���Â8�k���ǃ��h�������_������A����Q���Ј����(�L�k�v�����݉��`��w��������=�n���/���T�ȏ��&�M�z���V���K�����I��b�D�����|�Ж$�d������:���hashchkisamchkNOSIImpossibile creare il file '%-.200s' (errno: %d - %s)Impossibile creare la tabella '%-.200s' (errno: %d - %s)Impossibile creare il database '%-.192s' (errno: %d - %s)Impossibile creare il database '%-.192s'; il database esisteImpossibile cancellare '%-.192s'; il database non esisteErrore durante la cancellazione del database (impossibile cancellare '%-.192s', errno: %d - %s)Errore durante la cancellazione del database (impossibile rmdir '%-.192s', errno: %d - %s)Errore durante la cancellazione di '%-.192s' (errno: %d - %s)Impossibile leggere il record dalla tabella di sistemaImpossibile leggere lo stato di '%-.200s' (errno: %d - %s)Impossibile leggere la directory di lavoro (errno: %d - %s)Impossibile il locking il file (errno: %d - %s)Impossibile aprire il file: '%-.200s' (errno: %d - %s)Impossibile trovare il file: '%-.200s' (errno: %d - %s)Impossibile leggere la directory di '%-.192s' (errno: %d - %s)Impossibile cambiare la directory in '%-.192s' (errno: %d - %s)Il record e` cambiato dall'ultima lettura della tabella '%-.192s'Disco pieno (%s). In attesa che qualcuno liberi un po' di spazio... (errno: %d - %s)Scrittura impossibile: chiave duplicata nella tabella '%-.192s'Errore durante la chiusura di '%-.192s' (errno: %d - %s)Errore durante la lettura del file '%-.200s' (errno: %d - %s)Errore durante la rinominazione da '%-.210s' a '%-.210s' (errno: %d - %s)Errore durante la scrittura del file '%-.200s' (errno: %d - %s)'%-.192s' e` soggetto a lock contro i cambiamentiOperazione di ordinamento abbandonataLa view '%-.192s' non esiste per '%-.192s'Rilevato l'errore %d - '%-.192s' dal gestore delle tabelleIl gestore delle tabelle per '%-.192s' non ha questa opzioneImpossibile trovare il record in '%-.192s'Informazione errata nel file: '%-.200s'File chiave errato per la tabella : '%-.200s'; prova a riparaloFile chiave vecchio per la tabella '%-.192s'; riparalo!'%-.192s' e` di sola letturaMemoria esaurita. Fai ripartire il demone e riprova (richiesti %d bytes)Memoria per gli ordinamenti esaurita. Incrementare il 'sort_buffer' al demoneFine del file inaspettata durante la lettura del file '%-.192s' (errno: %d - %s)Troppe connessioniFine dello spazio/memoria per i threadImpossibile risalire al nome dell'host dall'indirizzo (risoluzione inversa)Negoziazione impossibileAccesso non consentito per l'utente: '%-.48s'@'%-.64s' al database '%-.192s'Accesso non consentito per l'utente: '%-.48s'@'%-.64s' (Password: %s)Nessun database selezionatoComando sconosciutoLa colonna '%-.192s' non puo` essere nullaDatabase '%-.192s' sconosciutoLa tabella '%-.192s' esiste gia`Tabella '%-.129s' sconosciutaColonna: '%-.192s' di %-.192s e` ambiguaShutdown del server in corsoColonna sconosciuta '%-.192s' in '%-.192s'Usato '%-.192s' che non e` nel GROUP BYImpossibile raggruppare per '%-.192s'Il comando ha una funzione SUM e una colonna non specificata nella GROUP BYIl numero delle colonne non e` uguale al numero dei valoriIl nome dell'identificatore '%-.100s' e` troppo lungoNome colonna duplicato '%-.192s'Nome chiave duplicato '%-.192s'Valore duplicato '%-.192s' per la chiave %dSpecifica errata per la colonna '%-.192s'%s vicino a '%-.80s' linea %dLa query e` vuotaTabella/alias non unico: '%-.192s'Valore di default non valido per '%-.192s'Definite piu` chiave primarieTroppe chiavi. Sono ammesse max %d chiaviTroppe parti di chiave specificate. Sono ammesse max %d partiLa chiave specificata e` troppo lunga. La max lunghezza della chiave e` %dLa colonna chiave '%-.192s' non esiste nella tabellaLa colonna BLOB '%-.192s' non puo` essere usata nella specifica della chiaveLa colonna '%-.192s' e` troppo grande (max=%lu). Utilizza un BLOB.Puo` esserci solo un campo AUTO e deve essere definito come chiave%s: Pronto per le connessioni
Version: '%s'  socket: '%s'  port: %d%s: Shutdown normale
%s: Ricevuto segnale %d. Interruzione!
%s: Shutdown completato
%s: Forzata la chiusura del thread %ld utente: '%-.48s'
Impossibile creare il socket IPLa tabella '%-.192s' non ha nessun indice come quello specificatato dalla CREATE INDEX. Ricrea la tabellaL'argomento 'Field separator' non e` quello atteso. Controlla il manualeNon possono essere usate righe a lunghezza fissa con i BLOB. Usa 'FIELDS TERMINATED BY'.Il file '%-.128s' deve essere nella directory del database e deve essere leggibile da tuttiIl file '%-.200s' esiste gia`Records: %ld  Cancellati: %ld  Saltati: %ld  Avvertimenti: %ldRecords: %ld  Duplicati: %ldSotto-parte della chiave errata. La parte di chiave utilizzata non e` una stringa o la lunghezza e` maggiore della parte di chiave.Non si possono cancellare tutti i campi con una ALTER TABLE. Utilizzare DROP TABLEImpossibile cancellare '%-.192s'. Controllare che il campo chiave esistaRecords: %ld  Duplicati: %ld  Avvertimenti: %ldYou can't specify target table '%-.192s' for update in FROM clauseThread id: %lu sconosciutoUtente non proprietario del thread %luNessuna tabella usataTroppe stringhe per la colonna %-.192s e la SETImpossibile generare un nome del file log unico %-.200s.(1-999)
La tabella '%-.192s' e` soggetta a lock in lettura e non puo` essere aggiornataNon e` stato impostato il lock per la tabella '%-.192s' con LOCK TABLESIl campo BLOB '%-.192s' non puo` avere un valore di defaultNome database errato '%-.100s'Nome tabella errato '%-.100s'La SELECT dovrebbe esaminare troppi record e usare troppo tempo. Controllare la WHERE e usa SET SQL_BIG_SELECTS=1 se e` tutto a posto.Errore sconosciutoProcedura '%-.192s' sconosciutaNumero di parametri errato per la procedura '%-.192s'Parametri errati per la procedura '%-.192s'Tabella '%-.192s' sconosciuta in %-.32sCampo '%-.192s' specificato 2 volteUso non valido di una funzione di raggruppamentoLa tabella '%-.192s' usa un'estensione che non esiste in questa versione di MySQLUna tabella deve avere almeno 1 colonnaLa tabella '%-.192s' e` pienaSet di caratteri '%-.64s' sconosciutoTroppe tabelle. MySQL puo` usare solo %d tabelle in una joinTroppi campiRiga troppo grande. La massima grandezza di una riga, non contando i BLOB, e` %ld. Devi cambiare alcuni campi in BLOBThread stack overrun:  Usati: %ld di uno stack di %ld.  Usa 'mysqld --thread_stack=#' per specificare uno stack piu` grande.Trovata una dipendenza incrociata nella OUTER JOIN. Controlla le condizioni ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerImpossibile caricare la funzione '%-.192s'Impossibile inizializzare la funzione '%-.192s'; %-.192sNon sono ammessi path per le librerie condivisaLa funzione '%-.192s' esiste gia`Impossibile aprire la libreria condivisa '%-.192s' (errno: %d %-.128s)Impossibile trovare la funzione '%-.128s' nella libreriaLa funzione '%-.192s' non e` definitaSistema '%-.255s' bloccato a causa di troppi errori di connessione. Per sbloccarlo: 'mysqladmin flush-hosts'Al sistema '%-.255s' non e` consentita la connessione a questo server MySQLImpossibile cambiare la password usando MySQL come utente anonimoE` necessario il privilegio di update sulle tabelle del database mysql per cambiare le password per gli altri utentiImpossibile trovare la riga corrispondente nella tabella userRows riconosciute: %ld  Cambiate: %ld  Warnings: %ldImpossibile creare un nuovo thread (errno %d). Se non ci sono problemi di memoria disponibile puoi consultare il manuale per controllare possibili problemi dipendenti dal SOIl numero delle colonne non corrisponde al conteggio alla riga %ldImpossibile riaprire la tabella: '%-.192s'Uso scorretto del valore NULLErrore '%-.64s' da regexpIl mescolare funzioni di aggregazione (MIN(),MAX(),COUNT()...) e non e` illegale se non c'e` una clausula GROUP BYGRANT non definita per l'utente '%-.48s' dalla macchina '%-.255s'Comando %-.128s negato per l'utente: '%-.48s'@'%-.64s' sulla tabella '%-.64s'Comando %-.16s negato per l'utente: '%-.48s'@'%-.64s' sulla colonna '%-.192s' della tabella '%-.192s'Comando GRANT/REVOKE illegale. Prego consultare il manuale per sapere quali privilegi possono essere usati.L'argomento host o utente per la GRANT e` troppo lungoLa tabella '%-.192s.%-.192s' non esisteGRANT non definita per l'utente '%-.48s' dalla macchina '%-.255s' sulla tabella '%-.192s'Il comando utilizzato non e` supportato in questa versione di MySQLErrore di sintassi nella query SQLDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useInterrotta la connessione %ld al db: '%-.192s' utente: '%-.48s' (%-.64s)Ricevuto un pacchetto piu` grande di 'max_allowed_packet'Rilevato un errore di lettura dalla pipe di connessioneRilevato un errore da fcntl()Ricevuti pacchetti non in ordineImpossibile scompattare i pacchetti di comunicazioneRilevato un errore ricevendo i pacchetti di comunicazioneRilevato un timeout ricevendo i pacchetti di comunicazioneRilevato un errore inviando i pacchetti di comunicazioneRilevato un timeout inviando i pacchetti di comunicazioneLa stringa di risposta e` piu` lunga di 'max_allowed_packet'Il tipo di tabella usata non supporta colonne di tipo BLOB/TEXTIl tipo di tabella usata non supporta colonne di tipo AUTO_INCREMENTINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESNome colonna '%-.100s' non correttoIl gestore delle tabelle non puo` indicizzare la colonna '%-.192s'Non tutte le tabelle nella tabella di MERGE sono definite in maniera identicaImpossibile scrivere nella tabella '%-.192s' per limitazione di unicita`La colonna '%-.192s' di tipo BLOB e` usata in una chiave senza specificarne la lunghezzaTutte le parti di una chiave primaria devono essere dichiarate NOT NULL; se necessitano valori NULL nelle chiavi utilizzare UNIQUEIl risultato consiste di piu` di una rigaQuesto tipo di tabella richiede una chiave primariaQuesta versione di MYSQL non e` compilata con il supporto RAIDIn modalita` 'safe update' si e` cercato di aggiornare una tabella senza clausola WHERE su una chiave. %sLa chiave '%-.192s' non esiste nella tabella '%-.192s'Impossibile aprire la tabellaIl gestore per la tabella non supporta il %sNon puoi eseguire questo comando in una transazioneRilevato l'errore %d - '%-.192s' durante il COMMITRilevato l'errore %d - '%-.192s' durante il ROLLBACKRilevato l'errore %d durante il FLUSH_LOGSRilevato l'errore %d durante il CHECKPOINTInterrotta la connessione %u al db: ''%-.192s' utente: '%-.48s' host: '%-.255s' (%-.64s)Il gestore per la tabella non supporta il dump binarioBinlog closed, cannot RESET SOURCEFallita la ricostruzione dell'indice della tabella copiata '%-.192s'Errore dal master: '%-.64sErrore di rete durante la ricezione dal masterErrore di rete durante l'invio al masterImpossibile trovare un indice FULLTEXT che corrisponda all'elenco delle colonneImpossibile eseguire il comando richiesto: tabelle sotto lock o transazione in attoVariabile di sistema '%-.64s' sconosciutaLa tabella '%-.192s' e` segnalata come corrotta e deve essere riparataLa tabella '%-.192s' e` segnalata come corrotta e l'ultima ricostruzione (automatica?) e` fallitaAttenzione: Alcune delle modifiche alle tabelle non transazionali non possono essere ripristinate (roll back impossibile)La transazione a comandi multipli (multi-statement) ha richiesto piu` di 'max_binlog_cache_size' bytes di disco: aumentare questa variabile di mysqld e riprovareQuesta operazione non puo' essere eseguita con un database 'slave' che gira, lanciare prima STOP SLAVEQuesta operaione richiede un database 'slave', configurarlo ed eseguire START SLAVEIl server non e' configurato come 'slave', correggere il file di configurazione cambiando CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logImpossibile creare il thread 'slave', controllare le risorse di sistemaL'utente %-.64s ha gia' piu' di 'max_user_connections' connessioni attiveSi possono usare solo espressioni costanti con SETE' scaduto il timeout per l'attesa del lockIl numero totale di lock e' maggiore della grandezza della tabella di lockI lock di aggiornamento non possono essere acquisiti durante una transazione 'READ UNCOMMITTED'DROP DATABASE non e' permesso mentre il thread ha un lock globale di letturaCREATE DATABASE non e' permesso mentre il thread ha un lock globale di letturaArgomenti errati a %sA '%-.48s'@'%-.64s' non e' permesso creare nuovi utentiDefinizione della tabella errata; tutte le tabelle di tipo MERGE devono essere nello stesso databaseTrovato deadlock durante il lock; Provare a far ripartire la transazioneLa tabella usata non supporta gli indici FULLTEXTImpossibile aggiungere il vincolo di integrita' referenziale (foreign key constraint)Impossibile aggiungere la riga: un vincolo d'integrita' referenziale non e' soddisfattoImpossibile cancellare la riga: un vincolo d'integrita' referenziale non e' soddisfattoErrore durante la connessione al master: %-.128sErrore eseguendo una query sul master: %-.128sErrore durante l'esecuzione del comando %s: %-.128sUso errato di %s e %sLa SELECT utilizzata ha un numero di colonne differenteImpossibile eseguire la query perche' c'e' un conflitto con in lock di letturaE' disabilitata la possibilita' di mischiare tabelle transazionali e non-transazionaliL'opzione '%s' e' stata usata due volte nel comandoL'utente '%-.64s' ha ecceduto la risorsa '%s' (valore corrente: %ld)Accesso non consentito. Serve il privilegio %-.128s per questa operazioneLa variabile '%-.64s' e' una variabile locale ( SESSION ) e non puo' essere cambiata usando SET GLOBALLa variabile '%-.64s' e' una variabile globale ( GLOBAL ) e deve essere cambiata usando SET GLOBALLa variabile '%-.64s' non ha un valore di defaultAlla variabile '%-.64s' non puo' essere assegato il valore '%-.200s'Tipo di valore errato per la variabile '%-.64s'Alla variabile '%-.64s' e' di sola scrittura quindi puo' essere solo assegnato un valore, non lettoUso/posizione di '%s' sbagliatoQuesta versione di MySQL non supporta ancora '%s'Errore fatale %d: '%-.512s' dal master leggendo i dati dal log binarioReplica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionValore duplicato '%-.64s' per la chiave '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAccesso non consentito per l'utente: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setLa tabella particione '%-.64s' non esisteFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionValore duplicato per la chiave '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\��m
m
japanese/errmsg.sysnu�[�����Y��d��d�)��f��L��?��'h�S��/���d	�	�	p
�
r��
<
�

A`���?p��W���?i���C��B�8��Vw��^�F�Hja�O���X��0|�����,q��]���& ? H!�!R"�"�"3#p#�#$M$�$%a%�%O&�&�&�'�'�'"(U(�()�)%*�*�*+�+�+V,�,�,-i-�-�-�-4.n.�.�../u/�/60�0�01�1�1'2�2�23t3�3%4J4�4�4 5`5�5�5D6�6
7L7x7�78N8�8�8:9�9�9�:K;�;�<=�=�=>�>�>�>K?�?�?@�@ACAqA�A�ABSB~B�B�BEC�C�C>D�DEnE�E�EFkF�F�F\G�G�GHVH�H�H0IvI�I�I	J1JlJ�JsK�K�K'LXL�LM�M�M�M8N�NOJO�O�O&PUP�PQWQ�Q�Q�R�S<T�T�U�U!VNV�V�V3W�WXuX�X3Y�YZIZ�Z[G[�[�[�[\A\�\�\�\�\]%]<]Z]n]�]�]�]^8^�^_2_o_�_�_�_�_
``6`I`a`�`�`�`�`aa+aHaxa�a�a
b5bbb�b�bc]c�c�c�cd,d[d�de]e�e'fcf�f�f�f�f!gBgog}g�g�g#hIh�h�h�hi-i_iqi�i�i�ij#jmjj�j�j	kMkpk�k�k�k�kFl�l�l�l�l'm�m�mnLn�n�no5oHo�o�o�o/pfp�p�p#qgq%r�r}s�stit�t�t1uou�uv@v�v�vdw�w�wx�x�x�x'yJysy�yOz�z5{T{�{'|j|�|�|>}v}�}$~�~�~p���Q�����܀��(�i����*�F�����]����G�~����6�|�݅�P����
�B�������,�z�����W�~����L���Њ��+�f���+�f���Ɍ�*�K���ȍ:�|�����2�Z��������2�����ѐ������� �2�]���ݒ��W�������!�a���������y�Ŗ�E�|��������O���Ԙ�?�\�������U�z���ޚz�����7�v����d���L���ݞ��
�*�S�������'�e���۠�A�i�ơ��@���ɢ�%�V�n���ģ�p����@�t���ڥ
�z�������������ڦ�0�S�}���ѧ���\�����¨ �q���ҩ���C���֪�V����3����������:�ر6����������1�l���Ҵ	�+���ߵ(�c���Ѷ�)�t���a������J���޹���V�ٻE���ټ�Q���������q�?������f�v�v�����2������x�����&�b�������e����I�g���������7�o�����A�x���������
�T�u���^�����G����Q�����C�n�����+��������%�u����R�5�s�����_����;�x�=�}�����1���������f�����@�U�z���������&�9�|�������O����]������N�����R����y�������;�~���2�f���7�g�������"�D�u����F����������<�~���������d�����T�����M�j�����%�����f���5�9���*�?���E�w����V����`����<_���g���G:�3h��@��!I��(U��<	�	�	
9
_
�
�
�
	.W|���U�O
�
�
 Ap�r��d��2W��n��0�H��N"�V�]�e�>��G��$p��S��m � /!�!�!<"y"�"�"�"�"#7#�#�#�#$�$�$	%v%�%�%�&�&�&l'�'�'/(\(�(�(;)�)�)?*�*�*	+f+�+�+',h,�,�, -�-�-�-.3.j.�.�.�./8/h/�/L0�0�0�1292q2�2�23=3X3�3�3*4�4x5�5�546�67�7?8�8�8^9p9�9�9�9:1:N:;Z;�;�;T<�<�<�<�<1=[=�=�=�=�=�=><>`>-?�?�?J@@4A�A�AAB�B9C�C2D�D�D=E^E�E�E�EF?FpF�F�F�F%G�G�G�G2H�H�H_I�IJ9JYJ�J�J�J0KdK�K�K�K'LvL�LMMM�M�MFN|N�N;O�O�OPIP{P�P�PQLQ}Q�Q�Q�Q�QRBR�R�R)S�S�ST2T�T�TUbU�U$VbV�VXWX�X�XY8YvY�YZDZzZ�Z=[�[\;\Y\�\]_]�]�];^}^�^"_b_�_�_�_v`�`a*a^a�a�ab\b�b�bcQc�c�c	d@ded�d�dJe�e�e�f�f
g=gqg�g�gLh�h�hDi�i�i@j�jik l�l"mn@non�n�n�n�n9oZouo�o�o�o�o)pbp�p�p�p<qdq�q�q)rvr�r�r�s�stEt�t�t.u�uv�v�vwMww�w�wKxyx�x�xyWy�y�yzIz�z>{s{�{�{!|k|�|�|�|)}y}�}�}~�~�~�~<�����7�������;���ԃ�a�ڄR�����.�k�����X������t��݊��j��Q����%���ۏF�������r�����F���J����0�u�Ĕ�8�������C����X��k���!�F�}����M������C����l�ȝ'�h���Þ��;����Z�R��.�Z����2�~�צ�T�|�����!����)����q���z����!�5�u���F������[����I����/�����ΰ�+�o�������q��7����4���õ�G���Ŷ��L�|�ɷ�;�d�g����8�|��
�S�i���L�s����[���
�a�ν!������{���ݿ�v����N�������n���F�����.������Q�y���
������i������7�j�n���I����~���U����g����u���4�B�������T���@����� ���J���O���,�b�������������N��������"�V�����2���������)�K������x�����-�N�g�����������-�|�����3�������Q���Q���\�����2�������!�U������L���n�����F�����%�z�%��4��K��+��1�w��r����;�l����:���9��7b�R��0��7O���'X�s�$	T	�	s
�
�
0��,�2
�
K���U<�O�a��J�\�7��j�����&N�����*����"�� 5 } � f!�!?"�"�"=#�#�#$l$�$%O%&h&�&�& '�'�'�(�)�)*,*`*�*�*�*+-+W+�+�+,h,�,�,`-�-�-.n.�.�./,/I/�/�/�/0F0q0�0�0o1�1
2+2V2�2�2�23&3\3�3�3�3�3)4B4�4�45a5�56-6V6�6�6
77b7�7�7818c8�8�8�8H9�9�9#:�:G;<5<Y<�<=h=�=�={>�>l?�?�?�?@7@e@�@�@PA�AAB�B)ClC�C,DbD�D�D�D1E�E�EF!F�F�F"GZG�G�G�G�G�GHBH�H�HlIwI�I�I�I�I�IJmJ{J�J�J�J�J*KvK�K�K;L]L�L�LMAM`MuM�MNGN{N�N)OBO�P�PuQ�Q�Q�RYS�S�S!TGTmT�T�T�TDUlU�U�V�V�VaW�W�WX/X`X�X�X
YBY�Y�Z&[)[u[�[&\]\{\�\�\#]�]�]�]D^�^�^�^0_f_�_�_�_�_M`�`�`�`Ha^a�a�a�a:bab�b�b�b�b�b`c�d�d�de�e�fgAgig�g�g�g-hOh|h�h�h�h'iYi|i�i�i�i�ij]j�j�j3kSkk�k�k�kl=ldl�l�l�lmGmpm�m�m�mnLn~n�n�n�n0oboo�o8pkp�p�p�p=qZqq�q�q�qr?rdr�r�r5sss�s t{t�t�tBu�u0v�v�vvw�wjx�x<y{a{�{U|�|�|}Y}�}�}~e~�~�~>~��Àj�����
�h��3�J�c���ƃ��8������$�o�����6�a�����s�ȇ.�����C�l���ɉ�V����5�ǋ�d���͌#�k����%�V���u�D��ґ�=�q��������)�,�p����\��������O�������<�z����3�?�f�X��=������+���ۜ!�W����`���Ğ�-��Ɵ�R�����,�L�b�Y�̢�*�A������m���ؤ�����ťإ3�Q�����ݦ��`���է�[����.�a���6��l���׫�?�i�|���۬��;�l���ɭ��Z�����@�m���ۯ�<�^���ϰ�z�����ұ���k������³��R�����D����(�b����`���:�����Ϻ��!�@�����i�������B�{������K������?�Z��K������������9�d�������[����������]����Z���f�������A�e�i��@�y�����U��g������B�����-�[��������9�i�������C������B�����#�~���!�N�������8�r�����+�Y���*������b�������*�\�����/�|���_����I�X�[�^��������;�i�����4���9�`������<��������J��������h�A������)�a������!�S��������J�k��������:�u�������;���
�P������:�^����0�e������-�L�s�����M�s��������)�V�������
�5�m��������"�O��������;�n�������+�n���� �k������ �A�����4�����b��`�u�����!�B�Z������S�����#�^����2�w�����[Y�r����_�`���@u��>��	9	s	�	
K
�
�
	���/Qs�
h
�
�
������&>h�����a�._���8����pw$h��<���?g� �@v���;3j k !G!}!�!"S"�"#_#�#�#�#1$�$�$�$)%C%`%&U&�&>'Y'�'�'(7([(�(�(�()=)P)w)�)Z*�*�*A+v,�,�,�,#-K-�-�-u.�.
/`/�/�//0g0�0�0�0)1\1�1�12t2�2�203i3�3�34G4o4�45d5�56+6O6v6�6�67<7^7�7�7;8m8�8�8G9q9�9�9�9M:�:�:�:
;7;];�;�;(<K<}<�<�<=�=)>�>D?�?�?�?�?W@�@PA�A�AIB�B�B�B%C�C�CD�D%E�ERF�F�F�F,G0G4G8G<G@GDGeG�G�G�GHVH�H�H�H�HI5IHIhI�IWJ�J	K[K�K�K�KL_L�L�L�L9M�M�MNlN�N�N%O�O!P�PQ�Q�QRSOSzS�S�STT(TrT�T�TU.UOUqU�U�U�UV'V6VIV\VjV�V�VW;W]WtW�W�WX7X^XoX�X�XYEYaY�Y�Y�Y�YZ<Z�Z�Z
[=[�[�[\5\~\�\�\�\?]]]�]�]�]2^b^�^�^�^�^__o_�_``G`u`�`�`a]a�a�a�a�a4beb�b�b�b�b�byc�c�d
e+eTe�e�ef7fgf�f�fggMg�g�gh7hgh�h�h�h�hi-iOi�i�i�i�i4j`j�j�j�j�j"kAkIkSk}k�k�klwlzl�l]m�m�m�mnnnnDnvn�n#oMo�o�o�p�q�qqr3sEtqt�t�t#u;u�u�u�u�uvDvvv�v�vw3w`w�w�wx:xXxox�x�x
yly�y�yz0zRzizlz�z�z�z{G{�{�{�{|^|�|�|�|%}e}�}�}�}~~m~�~�~�~#q����)�D�W�����ƀ��7����ށ�=�c������!�~�����;�9���؅��(�`�w�����6���͇������̈��F�w���^�o�����`�����Ҍ��/�m�������܍'�_������َ�&������M���0�����-��o�Ǔ[��A����?�q��������ǘ�)�x�����9���ƚӚR���Ǜ�8�r�������ߝ����h�ן&�x�Ҡ!�U����x���[�ģ>���*�\��S��������ҧr����>�h���ɩ�R���ê�C�j����a�����!���,���ٰ�;���ϱ	�f���Ӳ�R�|�ʳ�_������W�˶K���̷+���@������T���ؼ`���Խ�C���#���2����j��#�I������Z����o��� �����#�����C��������/�L�m��������V���B������B�����?�0���'���������v�7���+�d�����*�����K���(�_�����G���O������|����\�����5����^���8�����.�p���
�i���7���J�����)������-���G���.�g���B�~�����R����M�������'�Q�������5�������h������������+�X���D�u���!�����I�����<���K�����������S����J����0����������P�����&�`������,�u�����Z�:�f��]��SV�	g�@t��&=Qk����-T���.	R	{	�	�	(
=
{
�
�
U�����
N
�
�
�
/j���T���2����0Qo���:�H�J{��	-a��?`�k�����������������������	!$'*-0369<?BEHKNQTWZ]�������������������GJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgj���������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|���������������������������#K��SVY\_b���: � � � C!z!�!@"�";#[#�#�#$+$n%�&�&�&3'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'(((
(
((((((("(%(((+(.(1(4(7(:(=(@(C(F(I(L(O(�(�(�(�(�()))
)
)))))>)A)D)G)J)M)P)S)V)Y)\)_)b)e)h)k)n)q)t)w)z)})�)#*&*)*,*/*2*5*8*;*>*A*D*G*J*M*P*S*V*Y*\*_*b*e*h*k*n*q*t*w*z*}*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++
+
+++++++"+%+(+++.+1+4+7+:+=+@+C+F+I+L+O+R+U+X+[+^+a+d+g+j+m+p+s+v+y+|++�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,	,,,,,,,,!,$,',*,-,0,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---------- -#-&-)-,-/-2-5-8-;->-A-D-G-J-M-P-S-V-Y-\-�-�-�-\._.b.e.h.k.n.q.t.w.z.}.�.�.�.�.�.�.�.�.�.�.�.�.�./>/�/*0�1�1�122�2�23K3k3�3�3�344H4r4�4�45�5�56E6r6�6�6%7�78B8)9\9�9�:�:�:�:A;�;�;�;�;�;�;�;�;<<<�<=]=�=�=>�>�>�>?'?d?�?!@9@d@�@A�A5B�B	C2ChCkCnCqCtCwCzC}C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�C�CDDD
D
DDDDDDD"D%D(D+D.D1D4D7D:D=D@DCDFDIDLDODRDUDXD[D^DaDdDgDjDmDpDsDvDyD|DD�D�D�D�D�D�D�D�D�D�D�D�D#E&E)E,E/E2E5E8E;E>EAEDEGEJEMEPESEVEYE\E_EbEeEhEkEnEqEtEwEzE}E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�E�EFFF
F
FFFFFFF"F%F(F+F.F1F4F7F:F=F@FCFFFIFLFOFRFUFXF[F^FaFdFgFjFmFpFsFvFyF|FF�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�FGGG	GGGGGGGG!G$G'G*G-G0G3G6G9G<G?GBGEGHGKGNGQGTGWGZG]G`GcGfGiGlGoGrGuGxG�GgH�H�H>I~I�I�I9JiJ�J�JK0KIKZK�K�K�K>LL�L�L�L#M?M_M�M�M�MNAN~N�NO$O?O_O�O�OPsP�P�P�PaQ�Q�Q;R�R�RSGSjS�S�S�S+T�T�TU$UEU�UVeVhVkVnVqVtVwVzV}V�V�V/WMWPW�W�WXJXkX�X�XY�Y7[�[�[\t\,]4^�^�^_'_*_-_�_�`aDbib�b�b�bc6c9c<c?cBcEcHcKcNcQc�c�c�c�c�cd dIdLdvdyd|dd�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�deee	ee�e�e�e�e�e�f�f�f�f�f�f�f�f�f�f�f�f�f�f�f�f�f�f)g,g�g}h�h�h�h�h�h�hi>iti�i�i�ijMj�j#k&k)k,k/k2k5k8k;k>kAkck�k�k�l�l�l�l�m1noRorp�ptq^r�r�r�rt�tu0uiu�uTv�v�v�vw6wjw�w�w�w
xYx�x�x�x�x�yzBz_z�z�z�z{@{w{�{�{.|�|}}b}�}~e~�~)9<h����?�U�y�A�����4�k�������3���ڃ�D����]�����"�<�?���І�!�H�f�����ɇ�����	�������̈-�b�������r���Ջ�.�a�ߌ;�|��|�َb��Ə�m���
�ݑ�E�~����<���ȓ����Ҕ������,��� ���ϘB�W�s����F�j�������/�x�����қ�!�؜��:�r�����Ν�:���ʞ;�`����,�g���ؠ+�v�ӡ9�s����f�ۣ%����U���å��B���-����k��U����V����E�����#�[�y��X����.�`�����l�o���ٯ5������!�E�T����Y�u������6�v�ĳ��R�h�}���ʹ��3���̵\���۷b����u�������̻�s��o�ý�8�]�y����
�3�P����S�y�����p����%����������S��������C�����&�c�����A�����4�O��� ����������D�����1�f����������}����b����A�{�����s�d�������	�4���J�M�P�S�����������h�w���^����p���S�k���-�n�������
�)��S�����M�����#�&�k��������o�����9���������k���I���#�z���������^�����(���������������6�n�������F�������!�L�O�R�s��������������������������������������;�d�������������#�[������������F�����P�������j��}���v���@����H������\����w���i�V��),/258;>ADGJMPSVY\_behknqtwz}����������g��8Y�#z�@��6�W��	K	�	�	
8
Y
�
 ��P
NqY*��L`������0��{��H^��S��\�Q��o��s !�!�!"1"�"L#�#]$%I%&�&j'(({(3)*^*�*�*[+�+�+W,M-�-p.�.�/�0�01�1�1{23y3
4�4�4�4�4_6(7�7[8�8h9�98:n:�:�:;F;'<=5>
?$@�@/A�A|B�B"CvC�C�C�C�C0D�D�DE@E_E�E�E�E{F�G�GH@H�H�H�H IzI�I+J�J�JNK�K�M�M�OvP�PQ�QR@RgS�SFT�T�T'U�UV:V$W�WX@XkX�X�XYFYJYNYRYZAZ�Z�Z�Z�[!\�\�\>]y]�]�]0^�^_�_�_'`�`�`:a�a�bBc�c�d�e�e)f�f�fg0gkg�g�g�gh.hmh�hji�ijdj�j�j�jkRk|k�k�k1lm�m�n@q�s�st5tgt�t)uvu�uv?v�vJw�w�x,y�ylz�z{{�{�{�{|�|�|�|D}�}�}~<~f~�~�~�~-Rz}��� �΀"���ԁC�j����І��:�J�s���Ň+�������F����6����,�l����G��3�p��h�k�Ɛ����C�Ē$���3���Քx���=��b����[���˘@�s���ϙ���p���Ț�g�������I����Y���؞����0�T�s�~�������h�����������E�v���7���\�Х��.�U�����^���S������Q��j�L���$�'���ج,�l� �ɮ��B���hashchkisamchkNOYESファイル '%-.200s' を作成できません。(エラー番号: %d - %s)表 '%-.200s' を作成できません。(エラー番号: %d - %s)データベース '%-.192s' を作成できません。(エラー番号: %d - %s)データベース '%-.192s' を作成できません。データベースはすでに存在します。データベース '%-.192s' を削除できません。データベースは存在しません。データベース削除エラー ('%-.192s' を削除できません。エラー番号: %d - %s)データベース削除エラー (ディレクトリ '%-.192s' を削除できません。エラー番号: %d - %s)ファイル '%-.192s' の削除エラー (エラー番号: %d - %s)システム表のレコードを読み込めません。'%-.200s' の状態を取得できません。(エラー番号: %d - %s)作業ディレクトリを取得できません。(エラー番号: %d - %s)ファイルをロックできません。(エラー番号: %d - %s)ファイル '%-.200s' をオープンできません。(エラー番号: %d - %s)ファイル '%-.200s' が見つかりません。(エラー番号: %d - %s)ディレクトリ '%-.192s' を読み込めません。(エラー番号: %d - %s)ディレクトリ '%-.192s' に移動できません。(エラー番号: %d - %s)表 '%-.192s' の最後の読み込み時点から、レコードが変化しました。ディスク領域不足です(%s)。(エラー番号: %d - %s)書き込めません。表 '%-.192s' に重複するキーがあります。'%-.192s' のクローズ時エラー (エラー番号: %d - %s)ファイル '%-.200s' の読み込みエラー (エラー番号: %d - %s)'%-.210s' の名前を '%-.210s' に変更できません (エラー番号: %d - %s)ファイル '%-.200s' の書き込みエラー (エラー番号: %d - %s)'%-.192s' はロックされています。ソート処理を中断しました。ビュー '%-.192s' は '%-.192s' に存在しません。ストレージエンジンがエラー %d - '%-.192s' を返しました。表 '%-.192s' のストレージエンジンでは提供されないオプションです。'%-.192s' にレコードが見つかりません。ファイル '%-.200s' 内の情報が不正です。表 '%-.200s' の索引ファイル(key file)の内容が不正です。修復を試行してください。表 '%-.192s' の索引ファイル(key file)は古い形式です。修復してください。表 '%-.192s' は読み込み専用です。メモリが不足しています。サーバーを再起動してみてください。(%d バイトの割り当てに失敗)ソートメモリが不足しています。ソートバッファサイズ(sort buffer size)の増加を検討してください。ファイル '%-.192s' を読み込み中に予期せずファイルの終端に達しました。(エラー番号: %d - %s)接続が多すぎます。メモリが不足しています。mysqld やその他のプロセスがメモリーを使い切っていないか確認して下さい。メモリーを使い切っていない場合、'ulimit'の設定等で mysqld のメモリー使用最大量を多くするか、スワップ領域を増やす必要があるかもしれません。IPアドレスからホスト名を解決できません。ハンドシェイクエラーユーザー '%-.48s'@'%-.64s' によるデータベース '%-.192s' へのアクセスは拒否されました。ユーザー '%-.48s'@'%-.64s' のアクセスは拒否されました。(using password: %s)データベースが選択されていません。不明なコマンドです。列 '%-.192s' は null にできません。'%-.192s' は不明なデータベースです。表 '%-.192s' はすでに存在します。'%-.129s' は不明な表です。列 '%-.192s' は %-.192s 内で曖昧です。サーバーをシャットダウン中です。列 '%-.192s' は '%-.192s' にはありません。'%-.192s' はGROUP BY句で指定されていません。'%-.192s' でのグループ化はできません。集計関数と通常の列が同時に指定されています。列数が値の個数と一致しません。識別子名 '%-.100s' は長すぎます。列名 '%-.192s' は重複してます。索引名 '%-.192s' は重複しています。'%-.192s' は索引 %d で重複しています。列 '%-.192s' の定義が不正です。%s : '%-.80s' 付近 %d 行目クエリが空です。表名／別名 '%-.192s' は一意ではありません。'%-.192s' へのデフォルト値が無効です。PRIMARY KEY が複数定義されています。索引の数が多すぎます。最大 %d 個までです。索引のキー列指定が多すぎます。最大 %d 個までです。索引のキーが長すぎます。最大 %d バイトまでです。キー列 '%-.192s' は表にありません。指定されたストレージエンジンでは、BLOB列 '%-.192s' は索引キーにできません。列 '%-.192s' のサイズ定義が大きすぎます (最大 %lu まで)。代わりに BLOB または TEXT を使用してください。不正な表定義です。AUTO_INCREMENT列は１個までで、索引を定義する必要があります。%s: 接続準備完了。
バージョン: '%s'  socket: '%s'  port: %d%s: 通常シャットダウン
%s: シグナル %d を受信しました。強制終了します！
%s: シャットダウン完了
%s: スレッド %ld を強制終了します (ユーザー: '%-.48s')
IPソケットを作成できません。表 '%-.192s' に以前CREATE INDEXで作成された索引がありません。表を作り直してください。フィールド区切り文字が予期せぬ使われ方をしています。マニュアルを確認して下さい。BLOBには固定長レコードが使用できません。'FIELDS TERMINATED BY'句を使用して下さい。ファイル '%-.128s' はデータベースディレクトリにあるか、全てのユーザーから読める必要があります。ファイル '%-.200s' はすでに存在します。レコード数: %ld  削除: %ld  スキップ: %ld  警告: %ldレコード数: %ld  重複: %ldキーのプレフィックスが不正です。キーが文字列ではないか、プレフィックス長がキーよりも長いか、ストレージエンジンが一意索引のプレフィックス指定をサポートしていません。ALTER TABLE では全ての列の削除はできません。DROP TABLE を使用してください。'%-.192s' を削除できません。列／索引の存在を確認して下さい。レコード数: %ld  重複数: %ld  警告: %ldFROM句にある表 '%-.192s' はUPDATEの対象にできません。不明なスレッドIDです: %luスレッド %lu のオーナーではありません。表が指定されていません。SET型の列 '%-.192s' のメンバーの数が多すぎます。一意なログファイル名 %-.200s.(1-999) を生成できません。
表 '%-.192s' はREADロックされていて、更新できません。表 '%-.192s' は LOCK TABLES でロックされていません。BLOB/TEXT 列 '%-.192s' にはデフォルト値を指定できません。データベース名 '%-.100s' は不正です。表名 '%-.100s' は不正です。SELECTがMAX_JOIN_SIZEを超える行数を処理しました。WHERE句を確認し、SELECT文に問題がなければ、 SET SQL_BIG_SELECTS=1 または SET MAX_JOIN_SIZE=# を使用して下さい。不明なエラー'%-.192s' は不明なプロシージャです。プロシージャ '%-.192s' へのパラメータ数が不正です。プロシージャ '%-.192s' へのパラメータが不正です。'%-.192s' は %-.32s では不明な表です。列 '%-.192s' は2回指定されています。集計関数の使用方法が不正です。表 '%-.192s' は、このMySQLバージョンには無い機能を使用しています。表には最低でも1個の列が必要です。表 '%-.192s' は満杯です。不明な文字コードセット: '%-.64s'表が多すぎます。MySQLがJOINできる表は %d 個までです。列が多すぎます。行サイズが大きすぎます。この表の最大行サイズは BLOB を含まずに %ld です。格納時のオーバーヘッドも含まれます(マニュアルを確認してください)。列をTEXTまたはBLOBに変更する必要があります。スレッドスタック不足です(使用: %ld ; サイズ: %ld)。必要に応じて、より大きい値で 'mysqld --thread_stack=#' の指定をしてください。OUTER JOINに相互依存が見つかりました。ON句の条件を確認して下さい。Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler関数 '%-.192s' をロードできません。関数 '%-.192s' を初期化できません。; %-.192s共有ライブラリにはパスを指定できません。関数 '%-.192s' はすでに定義されています。共有ライブラリ '%-.192s' を開く事ができません。(エラー番号: %d %-.128s)関数 '%-.128s' は共有ライブラリー中にありません。関数 '%-.192s' は定義されていません。接続エラーが多いため、ホスト '%-.255s' は拒否されました。'mysqladmin flush-hosts' で解除できます。ホスト '%-.255s' からのこの MySQL server への接続は許可されていません。MySQL を匿名ユーザーで使用しているので、パスワードの変更はできません。他のユーザーのパスワードを変更するためには、mysqlデータベースの表を更新する権限が必要です。ユーザーテーブルに該当するレコードが見つかりません。該当した行: %ld  変更: %ld  警告: %ld新規にスレッドを作成できません。(エラー番号 %d) もしも使用可能メモリーの不足でなければ、OS依存のバグである可能性があります。%ld 行目で、列の数が値の数と一致しません。表を再オープンできません。: '%-.192s'NULL 値の使用方法が不適切です。regexp がエラー '%-.64s' を返しました。GROUP BY句が無い場合、集計関数(MIN(),MAX(),COUNT(),...)と通常の列を同時に使用できません。ユーザー '%-.48s' (ホスト '%-.255s' 上) は許可されていません。コマンド %-.128s は ユーザー '%-.48s'@'%-.64s' の表 '%-.64s' の使用に関して許可されていません。コマンド %-.16s は ユーザー '%-.48s'@'%-.64s'
 の列 '%-.192s'(表 '%-.192s') の利用に関して許可されていません。不正な GRANT/REVOKE コマンドです。どの権限で利用可能かはマニュアルを参照して下さい。GRANTコマンドへの、ホスト名やユーザー名が長すぎます。表 '%-.192s.%-.192s' は存在しません。ユーザー '%-.48s' (ホスト '%-.255s' 上) の表 '%-.192s' への権限は定義されていません。このMySQLバージョンでは利用できないコマンドです。SQL構文エラーです。バージョンに対応するマニュアルを参照して正しい構文を確認してください。Delayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in use接続 %ld が中断されました。データベース: '%-.192s' ユーザー: '%-.48s' (%-.64s)'max_allowed_packet'よりも大きなパケットを受信しました。接続パイプの読み込みエラーです。fcntl()がエラーを返しました。不正な順序のパケットを受信しました。圧縮パケットの展開ができませんでした。パケットの受信でエラーが発生しました。パケットの受信でタイムアウトが発生しました。パケットの送信でエラーが発生しました。パケットの送信でタイムアウトが発生しました。結果の文字列が 'max_allowed_packet' よりも大きいです。指定されたストレージエンジンでは、BLOB/TEXT型の列を使用できません。指定されたストレージエンジンでは、AUTO_INCREMENT列を使用できません。INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES列名 '%-.100s' は不正です。使用のストレージエンジンは列 '%-.192s' の索引を作成できません。MERGE表の構成表がオープンできません。列定義が異なるか、MyISAM表ではないか、存在しません。一意性制約違反のため、表 '%-.192s' に書き込めません。BLOB列 '%-.192s' をキーに使用するには長さ指定が必要です。PRIMARY KEYの列は全てNOT NULLでなければいけません。UNIQUE索引であればNULLを含むことが可能です。結果が2行以上です。使用のストレージエンジンでは、PRIMARY KEYが必要です。このバージョンのMySQLはRAIDサポートを含めてコンパイルされていません。'safe update mode'で、索引を利用するWHERE句の無い更新処理を実行しようとしました。. %s索引 '%-.192s' は表 '%-.192s' には存在しません。表をオープンできません。この表のストレージエンジンは '%s' を利用できません。このコマンドはトランザクション内で実行できません。COMMIT中にエラー %d - '%-.192s' が発生しました。ROLLBACK中にエラー %d - '%-.192s' が発生しました。FLUSH_LOGS中にエラー %d が発生しました。CHECKPOINT中にエラー %d が発生しました。接続 %u が中断されました。データベース: '%-.192s' ユーザー: '%-.48s' ホスト: '%-.255s' (%-.64s)この表のストレージエンジンはバイナリ形式の表ダンプを利用できません。バイナリログがクローズされています。RESET MASTER を実行できません。ダンプ表 '%-.192s' の索引再構築に失敗しました。マスターでエラーが発生: '%-.64s'マスターからのデータ受信中のネットワークエラーマスターへのデータ送信中のネットワークエラー列リストに対応する全文索引(FULLTEXT)が見つかりません。すでにアクティブな表ロックやトランザクションがあるため、コマンドを実行できません。'%-.64s' は不明なシステム変数です。表 '%-.192s' は壊れています。修復が必要です。表 '%-.192s' は壊れています。修復(自動？)にも失敗しています。トランザクション対応ではない表への変更はロールバックされません。複数ステートメントから成るトランザクションが 'max_binlog_cache_size' 以上の容量を必要としました。このシステム変数を増加して、再試行してください。この処理は、稼働中のスレーブでは実行できません。あらかじめSTOP SLAVEコマンドを実行してください。この処理は、稼働中のスレーブでなければ実行できません。スレーブの設定をしてSTART SLAVEコマンドを実行してください。このサーバーはスレーブとして設定されていません。コンフィグファイルかCHANGE MASTER TOコマンドで設定して下さい。'master info'構造体の初期化ができませんでした。MySQLエラーログでエラーメッセージを確認してください。スレーブスレッドを作成できません。システムリソースを確認してください。ユーザー '%-.64s' はすでに 'max_user_connections' 以上のアクティブな接続を行っています。SET処理が失敗しました。ロック待ちがタイムアウトしました。トランザクションを再試行してください。ロックの数が多すぎます。読み込み専用トランザクションです。グローバルリードロックを保持している間は、DROP DATABASE を実行できません。グローバルリードロックを保持している間は、CREATE DATABASE を実行できません。%s の引数が不正です'%-.48s'@'%-.64s' は新しいユーザーを作成できません。不正な表定義です。MERGE表の構成表はすべて同じデータベース内になければなりません。ロック取得中にデッドロックが検出されました。トランザクションを再試行してください。使用の表は全文索引を利用できません。外部キー制約を追加できません。親キーがありません。外部キー制約違反です。子レコードがあります。外部キー制約違反です。マスターへの接続エラー: %-.128sマスターでのクエリ実行エラー: %-.128s%s コマンドの実行エラー: %-.128s%s の %s に関する不正な使用法です。使用のSELECT文が返す列数が違います。競合するリードロックを保持しているので、クエリを実行できません。トランザクション対応の表と非対応の表の同時使用は無効化されています。オプション '%s' が2度使用されています。ユーザー '%-.64s' はリソースの上限 '%s' に達しました。(現在値: %ld)アクセスは拒否されました。この操作には %-.128s 権限が(複数の場合はどれか1つ)必要です。変数 '%-.64s' はセッション変数です。SET GLOBALでは使用できません。変数 '%-.64s' はグローバル変数です。SET GLOBALを使用してください。変数 '%-.64s' にはデフォルト値がありません。変数 '%-.64s' に値 '%-.200s' を設定できません。変数 '%-.64s' への値の型が不正です。変数 '%-.64s' は書き込み専用です。読み込みはできません。'%s' の使用法または場所が不正です。このバージョンのMySQLでは、まだ '%s' を利用できません。致命的なエラー %d: '%-.512s' がマスターでバイナリログ読み込み中に発生しました。replicate-*-table ルールに従って、スレーブSQLスレッドはクエリを無視しました。変数 '%-.192s' は %s 変数です。外部キー '%-.192s' の定義の不正: %s外部キーの参照表と定義が一致しません。オペランドに %d 個の列が必要です。サブクエリが2行以上の結果を返します。'%.*s' はプリペアードステートメントの不明なハンドルです。(%s で指定されました)ヘルプデータベースは壊れているか存在しません。サブクエリの参照がループしています。列 '%s' を %s から %s へ変換します。'%-.64s' の参照はできません。(%s)導出表には別名が必須です。Select %u は最適化によって減らされました。特定のSELECTのみで使用の表 '%-.192s' は %-.32s では使用できません。クライアントはサーバーが要求する認証プロトコルに対応できません。MySQLクライアントのアップグレードを検討してください。空間索引のキー列は NOT NULL でなければいけません。COLLATION '%s' は CHARACTER SET '%s' に適用できません。スレーブはすでに稼働中です。スレーブはすでに停止しています。展開後のデータが大きすぎます。最大サイズは %d です。(展開後データの長さ情報が壊れている可能性もあります。)ZLIB: メモリ不足です。ZLIB: 出力バッファに十分な空きがありません。(展開後データの長さ情報が壊れている可能性もあります。)ZLIB: 入力データが壊れています。Row %u was cut by GROUP_CONCAT()行 %ld はすべての列へのデータを含んでいません。行 %ld はデータを切り捨てられました。列よりも多いデータを含んでいました。列にデフォルト値が設定されました。NOT NULLの列 '%s' に 行 %ld で NULL が与えられました。Out of range value for column '%s' at row %ld列 '%s' の 行 %ld でデータが切り捨てられました。ストレージエンジン %s が表 '%s' に利用されています。照合順序 (%s,%s) と (%s,%s) の混在は操作 '%s' では不正です。Cannot drop one or more of the requested users指定されたユーザーから指定された全ての権限を剥奪することができませんでした。照合順序 (%s,%s), (%s,%s), (%s,%s) の混在は操作 '%s' では不正です。操作 '%s' では不正な照合順序の混在です。変数 '%-.64s' は構造変数の構成要素ではありません。(XXXX.変数名 という指定はできません。)不明な照合順序: '%-.64s'このMySQLスレーブはSSLサポートを含めてコンパイルされていないので、CHANGE MASTER のSSLパラメータは無視されました。今後SSLサポートを持つMySQLスレーブを起動する際に利用されます。サーバーは --secure-auth モードで稼働しています。しかし '%s'@'%s' は古い形式のパスワードを使用しています。新しい形式のパスワードに変更してください。フィールドまたは参照 '%-.192s%s%-.192s%s%-.192s' は SELECT #%d ではなく、SELECT #%d で解決されました。START SLAVE UNTIL へのパラメータまたはその組み合わせが不正です。START SLAVE UNTIL で段階的にレプリケーションを行う際には、--skip-replica-start オプションを使うことを推奨します。使わない場合、スレーブのmysqldが不慮の再起動をすると問題が発生します。スレーブSQLスレッドが開始されないため、UNTILオプションは無視されました。索引名 '%-.100s' は不正です。カタログ名 '%-.100s' は不正です。クエリキャッシュのサイズを %lu にできませんでした。サイズは %lu になりました。列 '%-.192s' は全文索引のキーにはできません。'%-.100s' は不明なキーキャッシュです。MySQLは --skip-name-resolve モードで起動しています。このオプションを外して再起動しなければ、この権限操作は機能しません。'%s' は不明なストレージエンジンです。'%s' は将来のリリースで廃止予定です。代わりに %s を使用してください。対象表 %-.100s は更新可能ではないので、%s を行えません。機能 '%s' は無効です。利用するためには '%s' を含めてビルドしたMySQLが必要です。MySQLサーバーが %s オプションで実行されているので、このステートメントは実行できません。列 '%-.100s' で、重複する値 '%-.64s' が %s に指定されています。不正な %-.64s の値が切り捨てられました。: '%-.128s'不正な表定義です。DEFAULT句またはON UPDATE句に CURRENT_TIMESTAMP をともなうTIMESTAMP型の列は1つまでです。列 '%-.192s' に ON UPDATE句は無効です。This command is not supported in the prepared statement protocol yetエラー %d '%-.100s' が %s から返されました。一時エラー %d '%-.100s' が %s から返されました。Unknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaスレッドスタック不足です(使用: %ld ; サイズ: %ld ; 要求: %ld)。より大きい値で 'mysqld --thread_stack=#' の指定をしてください。Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)対象表 %-.100s は挿入可能ではないので、%s を行えません。Table '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native function'%-.64s' は索引 '%-.385s' で重複しています。Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTユーザー '%-.48s'@'%-.64s' のアクセスは拒否されました。SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setパーティション '%-.64s' は存在しません。Failure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionは索引 '%-.192s' で重複しています。Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\|L�Au�u�korean/errmsg.sysnu�[�����a��e�_�)���B��V��E��L��	*i�9b��	g	�	
A
�
;I�.U���
4
V
|
�
�
Z����!Zx��l�T�z��Nv�S�8d��D�>���E�� d�����%]��u����O�6�� l � � .!d!�!S"�"T#�#�#z$�$�$"%I%�%&�&'y'�'(�(�()D)d)�)*A*z*�*�*#+a+�+�+ ,V,�,�,	-=-w-�-�-U.{.�.�.D/s/�/�/�/0>0]0|0�0121i1�1�1�1�1Q2r2�2�253�34^4�4+5c5�5�56K6�6�6737h7�7�7*8L8�8�8�89F9c9�9�9#:G:�:�:);r;�;�;<3<U<�<�<=<=o=�=�=�=>C>b>�>�>�>?D?�?�?
@%@F@�@�@.AIAjA�A�A1B_B�B�B�B CcC�C�C+DGD�D~E�EF�FG:G[G�G�G�GVHrH�H�HHI�I�I�IuJ�J�JK0KYK�K�K�K LULjLL�L�L�L�L�LM[M�M�M	N�N�N�N�NO6OXOyO�O�O�O�O�O(P@PWPoP�P�P�P�P-QZQ|Q�Q�QRBR�R�RSSASvS�S�S�S~T�TU�U�UVV2VaV�V�V�V�V-W]W�W�W�W XVX{X�X�X�X�X'YFYqY�Y�Y�Y ZMZxZ�Z�Z�Z'[M[g[�[�[)\H\_\�\�\,]�]�]^H^{^�^�^�^8_h_�_�_`e`�`�`�aYb�bfc�c�c&d_d�d�d.ee�efmf�fgYgqg�g#h@h|h�h�hTi�iJj�j�j,k|k�k�kIl�l�l4mym�mPnqn�n�nDopo�o�op1pipsp}p�p�pEqjq�q�q>r�r�r@s�s�s�s3tvt�tuNu�u�u!vMv�v�vw:wlw�w�w5x�x�x�x_y�y�yz6zkz�z{k{�{�{	|2|j|�|�|}z}�}�}1~P~r~�~�~�~�~%r���K�̀�(�@�`�r���Ł��=���҂��'�C�a�����5�Z�ȄY����W�������&�?������S����Ј�5�����������;�w��������P�������-�A�^������,�[���؏�?�u�����#�R�t�����(�Y�����Œ��6���˓8�t���۔�A�������Ǖԕޕ��D�d�����ږ�0�Q�����ݗ��T���Θ�0�M�w���
�Q������g����:�ƞC�ȟn��j�С8���΢+�e���ʣ�=�_����\���ʥ�&�]����S������/�u���	�E�ߩ���p�ɫ�G�|���Ƭ�����j�=��˱0���������!�]�����;���߶�Q�����ܷ
����7�t���ݹ+�ź�1�b���»�U����ͽн�!�h����r���[����e���
�W�������?���*�����9�����0�f�I�������s����O���Q������E����������z����T�i����������:�M�������
�c���2�q����.�b����f���/������.��O�����F�z���K�{������6�X�����*�Z�����������D����������
�l�����\�����U�r�����-������n���=�A���2�G���M������^�����h�����D�g������o�������O�B���;�p�����H�����)�Q���0�]�������D�����A�g�������6�_�������]��W�����(�I�x��z���!�l����:_��v��8�P�V*�^�	e	�	m
�
F��
O��,
x
�
�
[��u�7�D���� ?�����~�����t��7d��C��G��n��/p��(���;r���@p�T��� !A!y!�!"!"E"`"�"�"2#�#�$�$�$<%�%#&�&G'�'�'f(x(�(�(�()9)V)*b*�*�*\+�+�+�+�+9,c,�,�,�,�,�, -D-h-5.�.�.R/�/<0�0�0I1�1A2�2:3�3�3E4f4�4�4�45G5x5�5�5�5-6�6�6�6:7�7�7g8�89A9a9�9�9�98:l:�:�:�:/;~;�;<U<�<�<N=�=�=C>�>�>?Q?�?�?�?'@T@�@�@�@�@�@	AJA�A�A1B�B�BC:C�C�CDjD�D,EjE�E`F"G�G�G	H@H~H�HILI�I�IEJ�JKCKaK�K	LgL�L�LCM�M�M*NjN�N�NO~O�OP2PfP�P�P"QdQ�Q�Q
RYR�R�RSHSmS�STRT�T�T�U�UVEVyV�V�VTW�W�WLX�X�XHY�YqZ([�[*\]H]w]�]�]�]�]A^b^}^�^�^�^�^1_j_�_�_�_D`l`�`�`1a~a�ab�b�b cMc�c�c6d�de�e�e#fUf�f�f�fSg�g�g�gh_h�h�h#iQi�iFj{j�j�j)ksk�k�k�k1l�l�l�lm�m�mnDn�n�op?p�p�p�qCr�r�rsis�sZt�tu�u6vsv�vw`w�w�wx|x"y�y�zr{�{%}Y}�}�}-~�~�~N���#�z��N���R����8�}�̃�@����ŅK�����`��s���)�N�����U���Ɗ��K����t�Ќ/�p���ˍ�C����b�Z��6�b����:���ߕ�\���Ȗ��)�����1����y���������)�=�}���N����#�c����Q����7�����֟�3�w��������y��?���<���ˤ�O���ͥ�T���Ѧ�C�l�o�����@�����[�q���T�{����c����i�֬)���ĭ������%�~�گ�V������v���N����6���ճ�Y����������q���ط
�?�r�v��Q���"�����]�˻&�o���&�}�ֽ<�J���Ⱦ�\��H����(���R���W���4�j�������������V��������*�^�����:���������1�S�
�����������5�V�o���$���!�����5�������;�������Y���Y���d�����:�������)�]�����#�T���v�����N�����-���-���<���S���3���9����z����C�t����B���A�����?�j���Z������8�����?�W�������/�`��{��,�\���{���8����4���:��S��#��
���]D�W�
i�R�d�?��	r	�	
�
�
.V�����2
�
�
�
�
*��=��n�G��E�� t�Wp��(����%4h���5_��#p��h��v��4Q���"Ny��w � !3!^!�!�!�!"."d"�"�"�"�"1#J#�#�#$i$�$%5%^%�%�%&&j&�&�&'9'k'�'�'(P(�(�(+)�)O*+=+a+�+',p,�,�,�-�-t.�.�.�.%/?/m/�/�/X0�0I1�112t2�243j3�3�3494�4�45)5�5�5*6b6�6�6�6�6�67J7�7�7t88�8�8�8�8�89u9�9�9�9�9�92:~:�:�:C;e;�;�;<I<h<}<�<=O=�=�=1>J>�?�?}@�@�@�AaB�BC)COCuC�C�C�CLDtD�D�E�E�EiF�F�F
G7GhG�G�GHJH�H�I.J1J}J�J.KeK�K�K�K+L�L�LMLM�M�MN8NnN�N�N�NOUO�O�O�OPPfP�P�P�PBQiQ�Q�Q�Q�Q�QhR�S�S�S$T�T�U#VIVqV�V�V�V5WWW�W�W�W�W/XaX�X�X�X�X�X%YeY�Y�Y;Z[Z�Z�Z�Z�Z[E[l[�[�[�[$\O\x\�\�\�\ ]T]�]�]�]�]8^j^�^�^@_s_�_�_`E`b`�`�`�`�`aGala�a�a=b{b�b(c�c�cdJd�d8e�e�e~f�frg�gDh&jij�j]k�k�klal�l�l%mmm�m�mFn�n�no�orp�p�pqpq�q;rRrkr�r�r�rs@s�s�s�s,twt�tu>uiu�uv{v�v6w�w�wxKxtx�x�xy^y�y�y=z�z�zl{�{�{+|s|�|�|-}^}�}}~L�ڀ�E�y�����ȁ&�1�4�x����d���	����W��������D�����
�;�G�n�`��E���Ŋ��3����)�_�����h���̍��5���Ύ �Z�����4�T�j�a�ԑ
�2�I���Ȓ!�u������&���͔�;�Y�������h���ݖ�c�����6�i���>��t���ߚ�G�q�������C�t���ќ��b�����!�H�u�����D�f���ן�������ڠ�'�s������ʢ��Z����L����0�j����h��B�����ש��)�H�����q�������J�����İ'�S�����G�b��S���ϳ������ �A�l���ֵ��c�Ҷ����Ǹe����b��n�ǻ߻��I�m�q��H������]�&�o����� �J���
�!�5�c��������A�q�������K�����	�J�����+�����)�V�������@�z����3�a���2�����%�j������2�d����7�����g����Q�`�c�f��������C�q�����<���A�h�����%�D��������R�������"�p�I�����	�1�i�������)�[������'�R�s�������
�B�}�������C����X�����
�B�f���	�8�m������5�T�{�����U�{��������1�^��������=�u�������
�*�W��������C�v�������3�v�����(�s������(�I����&�<������j���h�}�������)�J�b�������[�����+�f����:������!�����c�#�a����� �z���������g���
�h�������H�}�����F�����A�{���S���������7�Y�{���p��������������.�F�p������%i�6g���@���x,p��D���	"
G
o
�
(�H~���
C
;r#sO��[�g���9���1Kh]�Fa��?c���EX�b��I~���+S��}�h��7o�� 1 d � � !|!�!�!8"q"�"�"#O#w#�#$l$�$
%3%W%~%�%�%&D&f&�&�&C'u'�'�'O(y(�(�(�(U)�)�)�)*?*e*�*�*0+S+�+�+�+,�,1-�-L.�.�.�./_/�/X0�0�0Q1�1�1�1-2�2�2$3�3-4�4Z5�5�564686<6@6D6H6L6m6�6�6�67^7�7�7�7�7#8=8P8p8�8_9�9:c:�:�:�:;g;�;�;�;A<�<�<=t=�=�=->�>)?@�@�@�@"A!BWB�B�B�BCC0CzC�C�CD6DWDyD�D�D�DE/E>EQEdErE�E�E FCFeF|F�F�FG?GfGwG�G�GHMHiH�H�H�H�HIDI�I�IJEJ�J�JK=K�K�K�K�KGLeL�L�L�L:MjM�M�M�M�MgNwN�NO#OOO}O�O�O$PeP�P�P�PQ<QmQ�Q�Q�Q�Q�Q�R�R�ST3T\T�T�TU?UoU�U�U"V%VUV�V�VW?WoW�W�W�W�WX5XWX�X�X�X�X<YhY�Y�YZZ*ZIZQZ[Z�Z�Z�Z[[�[�[e\�\�\�\]]"]%]L]~]�]+^U^�^�^�_�`�`ya;bMcyc�c�c+dCd�d�d�d�deLe~e�e�ef;fhf�f�f!gBg`gwg�g�ghth�hii8iZiqiti�i�i�ijOj�j�j�j&kfk�k�k�k-lml�l�l�lm'mum�m�m�m+nyn�n�n�no1oLo_o�o�o�o�op?p�p�p�pqEqkq�q�q�q)r�r�r�rCsAt�t�tu0uhuu�uv>v�v�vww�w�w�w�wxNxxyzfzwz�z�z'{h{�{�{�{�{|7|u|�|�|�|�|/}g}�}�}�}�}~.~�~�~U�8�À�5��w�ςc���I����G�y�����$���χ
�1��������A���ΉۉZ���ϊ	�@�z�ȋ��!����"�����p�ߎ.���ڏ)�]���$����c�̒F���2�d��[��������ږz��� �F�p���ј�Z���˙�K�r����i�����)���4����&�C���נ�n���ۡ�Z���Ң�g�����_�ӥS���Ԧ3���H��� �Ʃ\����h���ܬ�K���+���:����r��+�Q�����	�b�ǲ!�w���(�����+����K����̷�7�T�u���˸��^�ԹJ���غ�J����G�8�ֽ/���ݾ����~�?��3�l�����2�����S���0�g�����O���W����� ������d�����=����f���@�����6�x����q���?��R�����1������5���O���6�o���J�������Z����U�������/�Y������=�������p�����������3�`���L�}���)���
��Q�����D���S����������[�����R�����8������������X�������.�h�������4�}����b��� �B���n�����!�e�����[�^����o����H�|����.�E�Y�s��������5�\�����6�Z������0�E������ �]�����$�������V�����7�r������'�\�������:�������8Yw��%B�P�R���5i��&Gh�s��������������������� #&),/258;>ADGJMPSVY\_be����������������			
	
							"	%	O	R	U	X	[	^	a	d	g	j	m	p	s	v	y	|		�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�

!
$
'
*
-
0
3
6
9
<
?
B
E
H
K
N
Q
T
W
Z
]
`
c
f
i
l
o
r
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
	!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������+S���$
[
^
a
d
g
j
���B���K��H�Cc��3v��;���������������	!$'*-0369<?BEHKNQTW��	!FILORUX[^adgjmpsvy|���+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258�������������������������������������

"%(+.147:=@CFILORUX[^ad���dgjmpsvy|���������������F�2� � !:!�!�!$"S"s"�"�"�"#"#P#z#�#�#!$�$�$ %M%z%�%�%-&�&'J'1(d(�(�)�)�)�)I*�*�*�*�*�*�*+++++�+
,e,�,�,-�-�-�-./.l.�.)/A/l/�/�01=1�12:2p2s2v2y2|22�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2333	33333333!3$3'3*3-303336393<3?3B3E3H3K3N3Q3T3W3Z3]3`3c3f3i3l3o3r3u3x3{3~3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3+4.4144474:4=4@4C4F4I4L4O4R4U4X4[4^4a4d4g4j4m4p4s4v4y4|44�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4555	55555555!5$5'5*5-505356595<5?5B5E5H5K5N5Q5T5W5Z5]5`5c5f5i5l5o5r5u5x5{5~5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�56666666666 6#6&6)6,6/6265686;6>6A6D6G6J6M6P6S6V6Y6\6_6b6e6h6k6n6q6t6w6z6}6�67o7�7�7F8�8�89A9q9�9�9:8:Q:b:�:�:;F;�;�;�;�;+<G<g<�<�<�<=I=�=�=>,>G>g>�>�>?{?�?�?�?i@�@�@CA�ABBOBrB�B�B�B3C�C�CD,DMD�D&EmEpEsEvEyE|EE�E�E�E�E7FUFXF�FG'GRGsG�G�GH�H?J�J�J&K|K4L<M�M�MN/N2N5N�N�OPLQqQ�Q�Q�Q#R>RARDRGRJRMRPRSRVRYR�R�R�R�R�R%S(SQSTS~S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�S�STTTTTTT�T�T�T�T�T�U�U�U�U�U�U�U�U�U�U�U�U�U�U�U�U�U�U1V4V�V�W�W�W�W�W�W�W&XFX|X�X�X�XYUY�Y+Z.Z1Z4Z7Z:Z=Z@ZCZFZIZkZ�Z�Z�[�[�[�[�\9]^Z^z_�_|`fa�a�a�ac�cd8dqd�d\e�e�eff>frf�f�f�fgag�g�g�g�g�h	iJigi�i�i�ijHjj�j�j6k�klljl�lmmm�m1nAnDnpn�n�n�n�nGo]o�oIp�p�p&q<qsq�q�qr;r�r�rsLs�s	tet�t�tu*uDuGu�u�uv)vPvnv�v�v�vwwwwwwwww�w�w5xjx�xy�yzzz�z�z	{6{i{�{C|�|�|�}�}j~�~�~!u����M������D���Ђ����ڃ�����4���(���ׇJ�_�{�Ɉ�N�r�������7�������ڊ��)�� �#�B�z�����֌�B���ҍC�h����4�o����3�~�ېA�{�����n��-����]���˔�J���5����s��]����^����M�����+�c���'�`�����6�h����t�w����=���ǟ�)�M�\����a�}������>�~�̢�%�Z�p�����գ�;���Ԥd����j����}�������Ԫ#�{�	�w�ˬ&�@�e��������;�X����[������
�x�����-�����%�۲�[�������K���ܴ.�k����I����<�W�Ƿ(����ù�� �L����9�n���û��#���Լ!�j�½�I���¾�{�l�������<���R�U�X�[����� �����
�p����f���'�x���[�s���5�v��������1�'�[�����U�����+�.�s��������w�����A��������s���Q���+�����������f�����0���"�����������#�>�v�������N�����)�T�W�Z�{��������������������������������������C�l�������������+�c����������%�N�������X���������$�r������~��H�����P������d��������q���	�^����1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|��������������������������%�o�����!�@�a���+�����H�����>���_����S�����@�a���(����X��V�y�a�2����Th�����8��	�	�	
!
P
f
�
�
[��d�

Y
�
�
w��{��9�T�eQ�r0�;
f��c�_U�x����% � � �!"�"#�#�#�#$g%0&�&c'�'p(�(@)v)�)�) *N*/+,=-.,/�/70�0�1�1*2~2�2�2�2�283�3�3 4H4g4�4�4�4�5�6�67H7�7�7�7(8�8�839�9�9V:�:�<�<�>~?�?@�@AHAoB�BNC�C�C/D�DEBE,F�F GHGsG�G�GHNHRHVHZH
III�I�I�I�J)K�K�KFL�L�L�L8M�MN�N�N/O�O�OBP�P�QJRS�S�TU1U�U�UV8VsV�V�V�VW6WuW�WrX�XYlY�Y�YZ ZZZ�Z�Z�Z9[\�\�]H`�b�b
c=coc�c1d~d�deGe�eRf�f�g4h�hti�ij j�j�j�j�k�k�k�kLl�l�l#mDmnm�m�m�mn5nZn�n�n�n�n�n(o�o*p�p�pKqrr�s�s�u�u�uBvRv{v�v�v3w�wx�x�xNy�y�y>z�z�z4{t{�{|O|};}x~�~ps�	��ɀK�́,���;���݃���E��j�����c���ӇH�{���׈�$�x���Љ�o���'����Q����a���
� �8�\�{���������p�������$����M�~���?�Ɠd�ؔ�6�]�����f��[����� �Y��r�T�Ě,�/����4�t�(�ѝ��J���hashchkisamchk아니오예화일 '%-.200s'를 만들지 못했습니다. (에러번호: %d - %s)테이블 '%-.200s'를 만들지 못했습니다. (에러번호: %d - %s)데이타베이스 '%-.192s'를 만들지 못했습니다.. (에러번호: %d - %s)데이타베이스 '%-.192s'를 만들지 못했습니다.. 데이타베이스가 존재함데이타베이스 '%-.192s'를 제거하지 못했습니다. 데이타베이스가 존재하지 않음 데이타베이스 제거 에러('%-.192s'를 삭제할 수 없읍니다, 에러번호: %d - %s)데이타베이스 제거 에러(rmdir '%-.192s'를 할 수 없읍니다, 에러번호: %d - %s)'%-.192s' 삭제 중 에러 (에러번호: %d - %s)system 테이블에서 레코드를 읽을 수 없습니다.'%-.200s'의 상태를 얻지 못했습니다. (에러번호: %d - %s)수행 디렉토리를 찾지 못했습니다. (에러번호: %d - %s)화일을 잠그지(lock) 못했습니다. (에러번호: %d - %s)화일을 열지 못했습니다.: '%-.200s' (에러번호: %d - %s)화일을 찾지 못했습니다.: '%-.200s' (에러번호: %d - %s)'%-.192s'디렉토리를 읽지 못했습니다. (에러번호: %d - %s)'%-.192s'디렉토리로 이동할 수 없었습니다. (에러번호: %d - %s)테이블 '%-.192s'에서 마지막으로 읽은 후 Record가 변경되었습니다.Disk full (%s). 다른 사람이 지울때까지 기다립니다... (에러번호: %d - %s)기록할 수 없읍니다., 테이블 '%-.192s'에서 중복 키'%-.192s'닫는 중 에러 (에러번호: %d - %s)'%-.200s'화일 읽기 에러 (에러번호: %d - %s)'%-.210s'를 '%-.210s'로 이름 변경중 에러 (에러번호: %d - %s)'%-.200s'화일 기록 중 에러 (에러번호: %d - %s)'%-.192s'가 변경할 수 없도록 잠겨있읍니다.소트가 중단되었습니다.뷰 '%-.192s'가 '%-.192s'에서는 존재하지 않읍니다.테이블 handler에서 %d - '%-.192s' 에러가 발생 하였습니다.'%-.192s'의 테이블 handler는 이러한 옵션을 제공하지 않읍니다.'%-.192s'에서 레코드를 찾을 수 없읍니다.화일의 부정확한 정보: '%-.200s''%-.200s' 테이블의 부정확한 키 존재. 수정하시오!'%-.192s' 테이블의 이전버젼의 키 존재. 수정하시오!테이블 '%-.192s'는 읽기전용 입니다.Out of memory. 데몬을 재 실행 후 다시 시작하시오 (needed %d bytes)Out of sort memory. daemon sort buffer의 크기를 증가시키세요'%-.192s' 화일을 읽는 도중 잘못된 eof을 발견 (에러번호: %d - %s)너무 많은 연결... max_connection을 증가 시키시오...Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space당신의 컴퓨터의 호스트이름을 얻을 수 없읍니다.Bad handshake'%-.48s'@'%-.64s' 사용자는 '%-.192s' 데이타베이스에 접근이 거부 되었습니다.'%-.48s'@'%-.64s' 사용자는 접근이 거부 되었습니다. (using password: %s)선택된 데이타베이스가 없습니다.명령어가 뭔지 모르겠어요...칼럼 '%-.192s'는 널(Null)이 되면 안됩니다. 데이타베이스 '%-.192s'는 알수 없음테이블 '%-.192s'는 이미 존재함테이블 '%-.129s'는 알수 없음칼럼: '%-.192s' in '%-.192s' 이 모호함Server가 셧다운 중입니다.Unknown 칼럼 '%-.192s' in '%-.192s''%-.192s'은 GROUP BY속에 없음'%-.192s'를 그룹할 수 없음Statement 가 sum기능을 동작중이고 칼럼도 동일한 statement입니다.칼럼의 카운트가 값의 카운트와 일치하지 않습니다.Identifier '%-.100s'는 너무 길군요.중복된 칼럼 이름: '%-.192s'중복된 키 이름 : '%-.192s'중복된 입력 값 '%-.192s': key %d칼럼 '%-.192s'의 부정확한 칼럼 정의자'%s' 에러 같읍니다. ('%-.80s' 명령어 라인 %d)쿼리결과가 없습니다.Unique 하지 않은 테이블/alias: '%-.192s''%-.192s'의 유효하지 못한 디폴트 값을 사용하셨습니다.Multiple primary key가 정의되어 있슴너무 많은 키가 정의되어 있읍니다.. 최대 %d의 키가 가능함너무 많은 키 부분(parts)들이 정의되어 있읍니다.. 최대 %d 부분이 가능함정의된 키가 너무 깁니다. 최대 키의 길이는 %d입니다.Key 칼럼 '%-.192s'는 테이블에 존재하지 않습니다.BLOB 칼럼 '%-.192s'는 키 정의에서 사용될 수 없습니다.칼럼 '%-.192s'의 칼럼 길이가 너무 깁니다 (최대 = %lu). 대신에 BLOB를 사용하세요.부정확한 테이블 정의; 테이블은 하나의 auto 칼럼이 존재하고 키로 정의되어져야 합니다.%s: 연결 준비중입니다
Version: '%s'  socket: '%s'  port: %d%s: 정상적인 shutdown
%s: %d 신호가 들어왔음. 중지!
%s: Shutdown 이 완료됨!
%s: thread %ld의 강제 종료 user: '%-.48s'
IP 소켓을 만들지 못했습니다.테이블 '%-.192s'는 인덱스를 만들지 않았습니다. alter 테이블명령을 이용하여 테이블을 수정하세요...필드 구분자 인수들이 완전하지 않습니다. 메뉴얼을 찾아 보세요.BLOB로는 고정길이의 lowlength를 사용할 수 없습니다. 'fields terminated by'를 사용하세요.'%-.128s' 화일는 데이타베이스 디렉토리에 존재하거나 모두에게 읽기 가능하여야 합니다.'%-.200s' 화일은 이미 존재합니다.레코드: %ld개  삭제: %ld개  스킵: %ld개  경고: %ld개레코드: %ld개  중복: %ld개부정확한 서버 파트 키. 사용된 키 파트가 스트링이 아니거나 키 파트의 길이가 너무 깁니다.ALTER TABLE 명령으로는 모든 칼럼을 지울 수 없습니다. DROP TABLE 명령을 이용하세요.'%-.192s'를 DROP할 수 없습니다. 칼럼이나 키가 존재하는지 채크하세요.레코드: %ld개  중복: %ld개  경고: %ld개You can't specify target table '%-.192s' for update in FROM clause알수 없는 쓰레드 id: %lu쓰레드(Thread) %lu의 소유자가 아닙니다.어떤 테이블도 사용되지 않았습니다.칼럼 %-.192s와 SET에서 스트링이 너무 많습니다.Unique 로그화일 '%-.200s'를 만들수 없습니다.(1-999)
테이블 '%-.192s'는 READ 락이 잠겨있어서 갱신할 수 없습니다.테이블 '%-.192s'는 LOCK TABLES 명령으로 잠기지 않았습니다.BLOB 칼럼 '%-.192s' 는 디폴트 값을 가질 수 없습니다.'%-.100s' 데이타베이스의 이름이 부정확합니다.'%-.100s' 테이블 이름이 부정확합니다.SELECT 명령에서 너무 많은 레코드를 찾기 때문에 많은 시간이 소요됩니다. 따라서 WHERE 문을 점검하거나, 만약 SELECT가 ok되면  SET SQL_BIG_SELECTS=1 옵션을 사용하세요.알수 없는 에러입니다.알수 없는 수행문 : '%-.192s''%-.192s' 수행문에 대한 부정확한 파라메터'%-.192s' 수행문에 대한 부정확한 파라메터알수 없는 테이블 '%-.192s' (데이타베이스 %-.32s)칼럼 '%-.192s'는 두번 정의되어 있읍니다.잘못된 그룹 함수를 사용하였습니다.테이블 '%-.192s'는 확장명령을 이용하지만 현재의 MySQL 버젼에서는 존재하지 않습니다.하나의 테이블에서는 적어도 하나의 칼럼이 존재하여야 합니다.테이블 '%-.192s'가 full났습니다. 알수없는 언어 Set: '%-.64s'너무 많은 테이블이 Join되었습니다. MySQL에서는 JOIN시 %d개의 테이블만 사용할 수 있습니다.칼럼이 너무 많습니다.너무 큰 row 사이즈입니다. BLOB를 계산하지 않고 최대 row 사이즈는 %ld입니다. 얼마간의 필드들을 BLOB로 바꾸셔야 겠군요..쓰레드 스택이 넘쳤습니다.  사용: %ld개 스택: %ld개.  만약 필요시 더큰 스택을 원할때에는 'mysqld --thread_stack=#' 를 정의하세요Cross dependency found in OUTER JOIN; examine your ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler'%-.192s' 함수를 로드하지 못했습니다.'%-.192s' 함수를 초기화 하지 못했습니다.; %-.192s공유 라이버러리를 위한 패스가 정의되어 있지 않습니다.'%-.192s' 함수는 이미 존재합니다.'%-.192s' 공유 라이버러리를 열수 없습니다.(에러번호: %d %-.128s)라이버러리에서 '%-.128s' 함수를 찾을 수 없습니다.'%-.192s' 함수가 정의되어 있지 않습니다.너무 많은 연결오류로 인하여 호스트 '%-.255s'는 블락되었습니다. 'mysqladmin flush-hosts'를 이용하여 블락을 해제하세요'%-.255s' 호스트는 이 MySQL서버에 접속할 허가를 받지 못했습니다.당신은 MySQL서버에 익명의 사용자로 접속을 하셨습니다.익명의 사용자는 암호를 변경할 수 없습니다.당신은 다른사용자들의 암호를 변경할 수 있도록 데이타베이스 변경권한을 가져야 합니다.사용자 테이블에서 일치하는 것을 찾을 수 없읍니다.일치하는 Rows : %ld개 변경됨: %ld개  경고: %ld개새로운 쓰레드를 만들 수 없습니다.(에러번호 %d). 만약 여유메모리가 있다면 OS-dependent버그 의 메뉴얼 부분을 찾아보시오.Row %ld에서 칼럼 카운트와 value 카운터와 일치하지 않습니다.테이블을 다시 열수 없군요: '%-.192sNULL 값을 잘못 사용하셨군요...regexp에서 '%-.64s'가 났습니다.Mixing of GROUP 칼럼s (MIN(),MAX(),COUNT(),...) with no GROUP 칼럼s is illegal if there is no GROUP BY clause사용자 '%-.48s' (호스트 '%-.255s')를 위하여 정의된 그런 승인은 없습니다.'%-.128s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 테이블 '%-.64s''%-.16s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 칼럼 '%-.192s' in 테이블 '%-.192s'잘못된 GRANT/REVOKE 명령. 어떤 권리와 승인이 사용되어 질 수 있는지 메뉴얼을 보시오.승인(GRANT)을 위하여 사용한 사용자나 호스트의 값들이 너무 깁니다.테이블 '%-.192s.%-.192s' 는 존재하지 않습니다.사용자 '%-.48s'(호스트 '%-.255s')는 테이블 '%-.192s'를 사용하기 위하여 정의된 승인은 없습니다. 사용된 명령은 현재의 MySQL 버젼에서는 이용되지 않습니다.SQL 구문에 오류가 있습니다.Delayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in use데이타베이스 접속을 위한 연결 %ld가 중단됨 : '%-.192s' 사용자: '%-.48s' (%-.64s)'max_allowed_packet'보다 더큰 패킷을 받았습니다.연결 파이프로부터 에러가 발생하였습니다.fcntl() 함수로부터 에러가 발생하였습니다.순서가 맞지않는 패킷을 받았습니다.통신 패킷의 압축해제를 할 수 없었습니다.통신 패킷을 읽는 중 오류가 발생하였습니다.통신 패킷을 읽는 중 timeout이 발생하였습니다.통신 패킷을 기록하는 중 오류가 발생하였습니다.통신 패팃을 기록하는 중 timeout이 발생하였습니다.Result string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native function중복된 입력 값 '%-.64s': key '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INT'%-.48s'@'%-.64s' 사용자는 접근이 거부 되었습니다.SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction중복된 입력 값: key '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\ �������norwegian/errmsg.sysnu�[�����ǔ�L���7��3l���)_��X���5Zl��(L���-���C_��		7	Q	x	�	�	�		
2
R
�
�
�
0V�����U���?
�
�
=V��	L��Md�]����@q��9W�Lr���%Ie����D��+M���1o�:h�!Sp��^��V��9[���3]w��� 9 c � � !d!�!�!�!0"u"�"�"#U#�#�#�#,$i$�$�$�$�$F%�%�%�%&&:&m&�&�&)'r'�'5(�(�(:)�)�)**Y*�*�*+O+�+�+�+-,p,�,�,-M-q-�-�-�-.].�.�./Z/�/�/0U0�0�0�0�0K1�1�1�12<2]2�2�2�23(3T3~3�3$4R4�4�4�405H5�5�5�56^6�6�67+7l7�7�7%8R8�8�8s9�9Q:�:Y;�;�;�;<H<d<�<�<?=s=�=>K>w>�>?c?�?�?�?@,@p@�@�@�@�@A'AEAYAtA�A�A�A#B�B�BCZCrC�C�C�C�C
D!D4DLDpD�D�D�D�DEE3EcE�E�E�E FMF�F�FGHGG�G�G�GHFHzH�HHI�IJNJ�J�J�J�JK-KZKhK�K�KL4LzL�L�L�LMJM\MyM�M�M�MNXNjN�N�N�N8O[OqO�O�O�O1PuP�P�P�PQmQ�QR7R�R�R�R S3SxS�S�STQT~T�TURUV�VhW�W
XTX�X�XYZY�Y�Y+Z�Z�ZO[�[�[�[x\�\�\�\]D]�] ^�^_%_�_�_;`w`�`aGa�a�aXb�b�bAcqc�c�c"dVd�d�d�d�d�d:ete�e�efyf�fgbg�gh:hoh�h�h8i�i�ij=j�j�j�jDk|k�k�k6lvl�lm:mlm�mnHn�n�n�n"o}o�o"p`p�p�p�pq<q�q�q8rrr�r�r�rsEsYsks�s�sFtZt�t�tHugu�u�u�u�uvAv~v�v�vwNwzw�w�w�wxrx�x�xDy�y5z�z�z{8{_{p{�{�{|t|�|�|�|}L}m}�}~6~h~�~6y��2�^������ˁ��a�q�������ق�1�g���փ�S�������u���ͅ�/�x���Ԇ��@�s����F����#�V�����)�2�8�B�O�Y�a�����ߊ�,�U�����̋�2�X�q�ό �I�����ȍ�7���̎���7����9���A���C�����K���8�I�����E�����ژ9���י�E�����ؚ#���Λ�2�i���ܜ(�p���F��k�ן0�k�����-�I���ѣ��y�2�������^���ĩ'�_���
�F������!�C�q���X���ۭ��D���,�k���ɯ�)�i����w�4�7�o���ϲ�l�ٴ;�x�µ���̶�q�����-���&����7����=���ͻ������ڿ_����������/�n���(�?�V���~���8�h��������.�R�o�������	�2�q���0������j������r���K�����[�{���w�����D�����������*�j�������E��������C��@�����T�v��<�p����V����]�����v��u�����H�~���������.������������S����@����Q������:�m�����=�����V�������K����\�����)�k��������]�����M�v�������#�O�w��������<�h���<����F�n�������m���E�Y�����!�N������Y���e����y����l�����*�v���|����E����<s��R��U��%e�9��l��.Hj���&SrHw�	^	
:
X
�
R��\�
+
�
Aw�O��5��5Y}��H_r��N��OR~��f���>`�O�e����0��CY~����7c� - C Z � � � � !*!O!�!�!�!�"#C#�#�#�$%`%�%�%�&R'�'�'E(�(�(�(-)W)�)�)�)*5*V*�*+#+`+�+,H,�,V-~-�-�-�-
.<.�.�.///Z/�/�/40q0�0�091�1�1d2�23X3�3�3�34Q4�4�4�45,595?5o5�5�5I6�6�6$7q7�78@8n8�8;9�9�9Q:�:�;<N<o<�<�<3=z=�=�=2>�>?}?�?�?5@o@�@ANA�A�APB�B�BC=CgC�CDrD�D�DEKE�E�E�E&FsF�FG9GwG�G�GHiH�HIXIJ:JxJ�J�J%KaK�K#LQL�L1MOM�M�M�N�OP�PzQ�Q�Q�Q&R8RQR�R�R�RS"S@SZS�S�S�S2T_T�T�TUQU�U�UJVjVWSW�W�W7X`X�X?YyY+Z_Z�Z�Z�Z*[^[�[�[\T\�\�\]U]�]�]�]�^�^�^?_�_�_�_`;`�`�`!a[auabHbkb�bVcdhd�d�de"f�fgBg}g�gHh�hiqi�i�j�j.klk�k�k l�l�l�mKno�o0p�q�q�qPr�rsIs�s�s$tOt�t�t(uiu�uv�v
wRw�w�w2xqx�xyfy+z�z�zb{�{P|�|}�}�}�}f~�~�~�~,^�'�|�ڀ6���ց�1�f����~�Ȅ������Ȉ�P����E�}��.�d����^�����q�ߍd�� �]������d���$�f���ɑ�n����X������<�t���ݔ	�^���n�ߖX���O�j����1�z����3�i����7�y���қ՛�_����W�x���םQ�v����"�u�ɟ�x�Ϡ<����*�Y���K����@�m����#�g�ܥe����G����;�������{��~�H�׫�>�p���جܬU��������ï1���հ&����<������.�X�³H�����1�������e���5���й�?��|���>���7�z��a���Ŀ��*���.�]�'�`�����s�\�����R����������K���6�e������L���e��7���7���D���N����E�1�]�������Z�����S�����>�����'�������3���6���S���b�����W���1�i�����l�3���,��� �M�����4����t������O������'�^�����B���=�����]���U�X�����>������Q���)���-�p����������p���l�����\���
�K����3�k��<�m��������9d��>`��[���`�T�`��W����u	�	�	0
�
-m*

I
�
�
�
#r���6�� :�:�E|��	1[���1�Hx��� N����%)_��L��5q��"Jx~�&Bq��'k�T�-�|�� � � !T!�!D"�"�"+#]#�#�#�#�#-$�$%�%&�&�&Z'�'�'(9(m(�()<)r)�)*K*�*�*�*
+;+D+O+z+�+,e,�,�,�,�,
--\-z-�-�-
..A.d.�.�./O/�/�/�/L0v0�0�0�0I1�1�1�12�2�2�3B4�45V506�6E7k7�7�7�7868R8�8�8�8�9C:e:�:�:#;s;�;�;<L<{<�<:=;>�>�>�>@?�?�?�?@B@�@�@(AmA�A�AABjB�B�B�BCFCgC�C�CDKD�D�D�D"EWE�E�E�E�E
FF;F�F�GHBH�HdI8J�J�J�J�J3KeK�K�K�KL<L]L�L�L�LM,MCM^M�M�M
NDN�N�N�NO'OWOO�O�O�O$PQP�P�P�PQ*QSQ�Q�Q�QR@RTR�R�R�R1S�S�ST>ThT�T�T�TU3UYU~U�U�U�UGV�V�V1W�W�W/XhX�X&Y�Y&Z`Z�Zb[�[\�\�^�^
_�_`U`�`�`�`=a�a�abAb�b�bc�c1d�d�d e{e�ePf�f�f�fg4g\g}g�ghhNh�h�h*imi�i�i�iij�j6k�klTll�l�lm7m~m�mn\n�n5o`o�op;p�p�pq[q�q�q�q�r�s\t@uvu�u�u�uv.v�v�v�v�v#wVw�wxox�xmy�y�yz\z�{�{�{|p|�|�|�|�}r~�~�~+]��I���ŀ��]�΁�2�`����4������e�����Єǅ:�s�������.���ۇ��F�e���
�3�F�������!�K�j�Ί�C���ɋ�b���ό#���R�ڎ�E�����׏�
�I�f���ڐ�7�S���ȑ�_�����ے!�I�y���̓��=�����%�@�k���ٕ�W��0�P����� �j����O���К��Q�Λl���
��=�c�������t�Z�נ����������*������T�����Ȧv�����5�c��$�����ҩ�<�[�ɪ8�"�T�t�-�˭��ȮX�ԯ-�E�a���Ӱױ~�����k�ó��մ�_������s�����ɶ��I�z���׷�1�V����G�o�����8����R������0�[����?�h���ǽ/����5���п�:�i������g����I���)�}����������%�Y�t�������K���������X��������K�~����K�b�������'�O�o�������!�U������I�m����������G�p������9�`�����x���$�A�s�������o��������i��������>������9�V�~�������-�T�{������)�@�p�������!�N���������'�c����� �`�����$�F�m�����,�v�������<�����S������C�\����������b������������q�����2�[�����c���������^������I��H���-�p������_������G�u�����0�n�����4�v����H�w���(�G�������-�y���A�b��#���H�P�[���������H�g���a����;�����%�^����W�
�k�������@����,�M�����������@Q���������>|��y��$b�DQ����	�	�	�
�
�
>}���$[����
�
E��#V���^�@x�Z���"f��S��Z��'T���1��0p���Y���U��3]��(P�$G{��e����G | N!�!-"�"#4#J#j#�#A$�$%\%�%�%:&b&�&' '�'(�(4)�)!*H*f*�*�*�*�*�*�*�*�*	+++}+�+,,-,N,�,�,�,�,8-�-.w.�.�./4/u/�/�/!0V0�0�0I1�1�1282�2	3�3k4�4*5_5�5�6�6�67>7n7t7�7�7�7<8}8�8�8�8	919L9r9�9�9�9�9�9:C:�:�:�:�:;:;r;�;�;�;
<D<r<�<�<�<=6=]==�=>W>{>�>?3?}?�?�?@7@Z@�@�@A$AaA�A�A�ABIBcB�B�BCtC�C�C�CD[D�D�D�DEAEiE�E�E�EF$F?FBF�FFGHxH�H�HIKIvI�I�IJ4J�J�J�JKEKzK�K�K�KL7LWL�L�L�L�L$MBM]M�M�M�M"NjNmN�N�N�N�N�NOYOvO�O�OLP�PQ>QbQ�Q�Q�Q�Q�Q�Q^R�R�R�R=SVT�T2U�U�V�W�W&XDX�X�X�XY)YYYtY�Y�YZGZtZ�Z�Z[?[�[�[�[�[\Q\x\�\8]i]]�]�]�]�]�]2^Q^�^�^�^_Z_�_�_	`<`b`�`�`�`<a]aua�a�a�a"bJb�b�bc1cXc�c�c�c�c�cd4dYd}d�d�d.eLe~e�e�e�e!f[f�f�f�f'g�g�h�hFiki�i�i�ijkj�jk;kqk�k�k�k:lZl�l�l�l}m}n�n�noTo�o�o�o!p@p`p�p�p�p�pq,qJq�q�q�qr+rGr}r�r�r.s�s�s#t�t)uku�u�v�v5w�wax�xyvy�y�y
z{�{|5|s|�|�|}^}u}�}�}4~A~�~�~5o��.�_����M�����a�ւE����@���Ä$����m�Ɇ2���!���ʈu����U����@��d�����֌�7�z����1�t���؎�T�Ϗ�Q��������$�G������=�w�ԕ�A������8�t�͗k���R�ř9����:������
���,���F�Π�B�|���������!���ؤV�������o�Ȧ-���ݧ"�����$����S���#�i�2�������۬��1�R���ĭ:����>������S�����<����C���������i���Ҷ�9���
�N���+���͹�L�������M����9�}�ʽ�[����}�̿R�����I����0�{���W���f����d����A�n������O������������A���5�������'�a�������1�m����� �R����L�~���8�l���������������p������B������%�l���.�c����`�����;����L�����V�����9���L������#�M������k���>�����K����J�������9������w���4��������W������������7�T�|�������9�g�������D�\�������!�R�������`�����
�<�|����C�k�����	��T��������F�r����0�3�e��������A�i�����5�|���/����!�[�w�����/��������)�,�/�2�5�8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b�e�h�k�n�q�t�w�z�}�������������������������������������������������7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|����������������������������������������������	��������!�$�'�*�-�0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~�����������������������������������������������������0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~���������������������������������������������������������������������� #&),/258;>���7b�������
-U�	^��<�0��G���
H
m
�
HKNQTWZ]`cfilorux{~���������������������`cfilorux{~�������������������������<
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
	!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������

"%(+.147:=@CFILORUX[^adgjmpsvy|�������������������������@CF������������������	z�E�?m�[���Y\q���Z�#P���$Z�*����T_�EHKbehknqt! s � '!Q!�!�!!"X"|"�"�"#�#�#�#$�$f%�%=&w&�&�&�&�&�&�&�&�&�&�&�&�&�&�&�&'''	''''''''!'$'''*'-'0'3'6'9'<'?'B'E'H'K'N'Q'T'W'Z']'`'c'f'i'l'o'r'u'x'{'~'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'((('(*(-(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))	))))))))!)$)')*)-)0)3)6)9)<)?)B)E)H)K)N)Q)T)W)Z)])`)c)f)i)l)o)r)u)x){)~)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)********** *#*&*)*,*/*2*5*8*;*>*A*D*G*J*M*P*S*V*Y*\*_*b*e*h*k*n*q*t*w*z*}*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*j+�+�+\,�,�,-i-�-�-.8..�.�.�.�.(/m/�/�/0-0N0�0�0�0�01J1n1�1�12t2�2�2�2�23�3�34D4c4�45I5�5%6j6�6�6�6�67`7�78G8u8�8�8Q9�9�9�9�9�9�9�9�9�9�9�9�9�:�:�:e;h;�;�;�;+<V<~<�<�>*?G?�?�?�@�A$B?BnB�B�B�B�BD|D�E�E�EF\F�F�F�F�F�F�F�F�F�F�F�FG2G5GSGVG�G�G�G�G�G�G�G�G�G�G�G�G�G�GHHHHH>HAHDHGHJHMHPHSHVHYH\H_HbHeHhHkHnHqHtHwHzH�H�HI7I:IJJJJJJJJJJ J#J&J)J,J/J2J5J�J�J]K�K�K�K�K�K3L]L�L�L�L�LMTMM�M�M�N�N�N�N�N�N�N�N�N�N�N�N!O$O0P3P6PePQ�Q�R�R�SbT�T�UV1VYV|W�WyX�X�XY�YZYZmZ}Z�Z�Z�Z[,[{[�[�[&\4\U\�\o]�]�]^'^P^^�^�^_F_�_*`�`�`�`-aua�a7b�b�b�b�b�bc9c]c�c�c�c�d�dbe�e�e�e�e,fmf�fgHg�g�g+hoh�h*iOiri�i�i�i�i>jqj�j�j�j�j�j7kkknkqktkwkzk}k�k�k�k:l�l�lmtmnzn�n	oCooo�o�oMp�p�p^q�qGr�r�r4s�s�stxtKuru�u�uvyv�vw6wWwzwx@x�xly�y�z{�{|=|�|�|�|/}�}�}�}�}#~&~�~�~�~@[�F����������<�q����8���΂�����Ճ
�F����A���� �\�ԆI�����R�È��1�h�������q�ًS�Ì$�q�č�S����� ���ɏ���Ɛ�\���Α�m�ڒݒ�G�����-�W�����&�R�Ǖ����T����2�S�����֗��;�k����:�ʙ��I�Л�}������y�	�:����o�ݠ1�����ˡ���^�x������y�����Z�p�ޤ�^�������A�j������R�q�����B���ѩ��U����I�����-����k�)�[������T���ԯ�)�H�h����:���б(������(�l��Ҵ��'�>�w��������������'�����;�s�ָ�/�̺[���޻_���ټC���ܽ�	�N�x��������4����`���������K��G�����N��� �e��h���@���<�����A�v���>�����4��������N���G����������N���=�i�l����������������	��������!�$�'�*�-�0�������)�,�/�2�5�8�������"�D�G�j�������5�]���0�3�
�b�����H���i���h����]���M��i���*�����%�~���!�o����m��������������������������������������������������������������������������C������G�������)�����c����������8�V�t���&�X�t���������H����r����������I����Q�_�b�e�h����9�~�i���F���������Z���3�!p�c�$S�qGy�R��q��	G
�
���p
�
)Q��f��U�[�J��d���{�$'m��,�;�U��;���� �!{"�#�#�$3%�%H&�&�&�&'-'`'�'(L(�(�(�())2)�)?+\+�+�+�+0,S,�,�,=-�-�-[.�./�0123�3V4�4�4v5�5�6X7�7	8J8�889v9�9�:;�;�;�;�;<<�<�<�<�<s=�=>>>�>�?$@R@�@�@AbA�AB�B�B-C�CDQD�DNEF�FmGEHIfI�I�I,JnJ�J�J�J!KFKyK�K�K	L�L+M}M�M�MANgN�N�N�NO`O�OnP.Q�Q�TW?WpW�W�W7X�X�XDY}Y�YZ�Z^[�[�\@]�]^�^�^�^_)_�_�_>`b`�`aOa�a�a�a�a(bdb�b�b�b�b�bc#c6c�c<d�d�dBe�e�fhYh>jPj`j�j�j�jk3k�kl�lmYm�mnWn�noWo�o�o*p�p�ptq�q�rOs�s�s4totrt/u�u2v�v#w�w�wCx�xky�yZz�z�zb{�{�{9|�|�|}=}f}�}�}
~6~q~�~!��W����y�ǁ(�F�h�s��������%�S�n�փ����j�����~�������,�ʈ>�m���É��̊l����������W�؍��*������F���ڐ��7�����hashchkisamchkNEIJAKan ikke opprette fila '%-.200s' (Feilkode: %d - %s)Kan ikke opprette tabellen '%-.200s' (Feilkode: %d - %s)Kan ikke opprette databasen '%-.192s' (Feilkode: %d - %s)Kan ikke opprette databasen '%-.192s'; databasen eksistererKan ikke fjerne (drop) '%-.192s'; databasen eksisterer ikkeFeil ved fjerning (drop) av databasen (kan ikke slette '%-.192s', feil %d - %s)Feil ved sletting av database (kan ikke slette katalogen '%-.192s', feil %d - %s)Feil ved sletting av '%-.192s' (Feilkode: %d - %s)Kan ikke lese posten i systemkatalogenKan ikke lese statusen til '%-.200s' (Feilkode: %d - %s)Kan ikke lese aktiv katalog(Feilkode: %d - %s)Kan ikke låse fila (Feilkode: %d - %s)Kan ikke åpne fila: '%-.200s' (Feilkode: %d - %s)Kan ikke finne fila: '%-.200s' (Feilkode: %d - %s)Kan ikke lese katalogen '%-.192s' (Feilkode: %d - %s)Kan ikke skifte katalog til '%-.192s' (Feilkode: %d - %s)Posten har blitt endret siden den ble lest '%-.192s'Ikke mer diskplass (%s). Venter på å få frigjort plass... (Feilkode: %d - %s)Kan ikke skrive, flere like nøkler i tabellen '%-.192s'Feil ved lukking av '%-.192s' (Feilkode: %d - %s)Feil ved lesing av '%-.200s' (Feilkode: %d - %s)Feil ved omdøping av '%-.210s' til '%-.210s' (Feilkode: %d - %s)Feil ved skriving av fila '%-.200s' (Feilkode: %d - %s)'%-.192s' er låst mot oppdateringerSortering avbruttView '%-.192s' eksisterer ikke for '%-.192s'Mottok feil %d - '%-.192s' fra tabell håndtererTabell håndtereren for '%-.192s' har ikke denne mulighetenKan ikke finne posten i '%-.192s'Feil informasjon i filen: '%-.200s'Tabellen '%-.200s' har feil i nøkkelfilen; forsøk å reparer denGammel nøkkelfil for tabellen '%-.192s'; reparer den!'%-.192s' er skrivebeskyttetIkke mer minne. Star på nytt tjenesten og prøv igjen (trengte %d byter)Ikke mer sorteringsminne. Vurder å øke sorteringsminnet (sort buffer size) for tjenestenUventet slutt på fil (eof) ved lesing av filen '%-.192s' (Feilkode: %d - %s)For mange tilkoblinger (connections)Tomt for tråd plass/minneKan ikke få tak i vertsnavn for din adresseFeil håndtrykk (handshake)Tilgang nektet for bruker: '%-.48s'@'%-.64s' til databasen '%-.192s' nektetTilgang nektet for bruker: '%-.48s'@'%-.64s' (Bruker passord: %s)Ingen database valgtUkjent kommandoKolonne '%-.192s' kan ikke vere nullUkjent database '%-.192s'Tabellen '%-.192s' eksisterer alleredeUkjent tabell '%-.129s'Felt: '%-.192s' i tabell %-.192s er ikke entydigDatabase nedkobling er i gangUkjent kolonne '%-.192s' i tabell %-.192sBrukte '%-.192s' som ikke var i group byKan ikke gruppere på '%-.192s'Uttrykket har summer (sum) funksjoner og kolonner i samme uttrykkFelt telling stemmer verdi tellingIdentifikator '%-.100s' er for langFeltnavnet '%-.192s' eksisterte fra førNøkkelnavnet '%-.192s' eksisterte fra førLike verdier '%-.192s' for nøkkel %dFeil kolonne spesifikator for felt '%-.192s'%s nær '%-.80s' på linje %dForespørsel var tomIkke unikt tabell/alias: '%-.192s'Ugyldig standardverdi for '%-.192s'Fleire primærnøkle spesifisertFor mange nøkler spesifisert. Maks %d nøkler tillattFor mange nøkkeldeler spesifisert. Maks %d deler tillattSpesifisert nøkkel var for lang. Maks nøkkellengde er is %dNøkkel felt '%-.192s' eksiterer ikke i tabellenBlob felt '%-.192s' kan ikke brukes ved spesifikasjon av nøklerFor stor nøkkellengde for kolonne '%-.192s' (maks = %lu). Bruk BLOB istedenforBare ett auto felt kan være definert som nøkkel.%s: klar for tilkoblinger
Version: '%s'  socket: '%s'  port: %d%s: Normal avslutning
%s: Oppdaget signal %d. Avslutter!
%s: Avslutning komplett
%s: Påtvinget avslutning av tråd %ld  bruker: '%-.48s'
Kan ikke opprette IP socketTabellen '%-.192s' har ingen index som den som er brukt i CREATE INDEX. Gjenopprett tabellenFelt skiller argumentene er ikke som forventet, se dokumentasjonenEn kan ikke bruke faste feltlengder med BLOB. Vennlisgt bruk 'fields terminated by'.Filen '%-.128s' må være i database-katalogen for å være lesbar for alleFilen '%-.200s' eksisterte alleredePoster: %ld  Fjernet: %ld  Hoppet over: %ld  Advarsler: %ldPoster: %ld  Like: %ldFeil delnøkkel. Den brukte delnøkkelen er ikke en streng eller den oppgitte lengde er lengre enn nøkkel lengdenEn kan ikke slette alle felt med ALTER TABLE. Bruk DROP TABLE isteden.Kan ikke DROP '%-.192s'. Undersøk om felt/nøkkel eksisterer.Poster: %ld  Like: %ld  Advarsler: %ldYou can't specify target table '%-.192s' for update in FROM clauseUkjent tråd id: %luDu er ikke eier av tråden %luIngen tabeller i brukFor mange tekststrenger kolonne %-.192s og SETKan ikke lage unikt loggfilnavn %-.200s.(1-999)
Tabellen '%-.192s' var låst med READ lås og kan ikke oppdateresTabellen '%-.192s' var ikke låst med LOCK TABLESBlob feltet '%-.192s' kan ikke ha en standard verdiUgyldig database navn '%-.100s'Ugyldig tabell navn '%-.100s'SELECT ville undersøke for mange poster og ville sannsynligvis ta veldig lang tid. Undersøk WHERE klausulen og bruk SET SQL_BIG_SELECTS=1 om SELECTen er korrektUkjent feilUkjent prosedyre %-.192sFeil parameter antall til prosedyren %-.192sFeil parametre til prosedyren %-.192sUkjent tabell '%-.192s' i %-.32sFeltet '%-.192s' er spesifisert to gangerInvalid use of group functionTable '%-.192s' uses a extension that doesn't exist in this MySQL versionA table must have at least 1 columnThe table '%-.192s' is fullUnknown character set: '%-.64s'Too many tables; MySQL can only use %d tables in a joinToo many columnsRow size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBsThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if neededCross dependency found in OUTER JOIN; examine your ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerCan't load function '%-.192s'Can't initialize function '%-.192s'; %-.192sNo paths allowed for shared libraryFunction '%-.192s' already existsCan't open shared library '%-.192s' (errno: %d %-.128s)Can't find symbol '%-.128s' in libraryFunction '%-.192s' is not definedHost '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.255s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192sInvalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used.The host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionSomething is wrong in your syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetMottok feil %d '%-.100s' fa %sMottok temporary feil %d '%-.100s' fra %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionLike verdier '%-.64s' for nøkkel '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTTilgang nektet for bruker: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setPartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionLike verdier for nøkkel '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�2���norwegian-ny/errmsg.sysnu�[��������M���=��<v��7n��7p��Ns���!Dg���D��5b}�	+	;	a	{	�	�	�	
3
]
~
�
�
	3`����
1R���-
r
�
�
2Il���<|�D��T��4Jv��Uu�7C\����]�����;|�?c���i�r��Y����S��2���9q���7k���� F q � � 	!D!�!�!�!*"h"�"#.#U#�#�#&$7$d$�$�$�$%/%~%�%�%&8&V&r&�&'%'a'�'�'m(�()r)�)*b*�*�*�*D+�+�+�+,e,�,�,�,6-{-�-�-�-.J.�.�.�.2/�/�/0J0�0�0�0�0-1y1�1�12F2j2�2�2�2303V3�3�3�3R4�4�4�4�4^5v5�5�56@6�6�6727Y7�7�78S8�8�8�8�9'::�:�;�;�;<D<v<�<�<=m=�=�=D>y>�>?L?�?�?�?@6@[@�@�@AA*A?AVAtA�A�A�AB+BRB�B,CLC�C�C�C�CD$D9DPDcD{D�D�D�DEE/EEEbE�E�EF'FOF|F�F�F/GwG�G�G�G!HFHuH�H)IwI�IAJ}J�J�J�JK;K\K�K�K�KL=LcL�L�LM&MGMyM�M�M�M�MN=N�N�N�N�N#OgO�O�O�O�OP`P�P�P�PQCQ�Q�Q6RhR�R�R(SQSdS�S�STKT�T�TU?U�UAVW�WX;X�X�XYMY�Y�Y,Z\Z�Z[�[�[\\�\�\�\)]L]u]^Q^�^7_V_�_)`l`�`�`@axa�a&b�b�bcrc�c�cdSd�d�d�de e*eke�e�ef3f�f�fJg�g�g4hkh�h�h#iii�i�i=jnj�j�j/kuk�k�klgl�l�lDmkm�mn9nyn�n�noSo�opSp�p�p�pq8qmq�q'rir�r�r�rsGsvs�s�s�stwt�t�t�tyu�u�u�u
vvJvrv�v�v�vDww�w�w�wxNx�x�xyuyzfz�z{2{i{�{�{�{�{<|�|�|},}I}}}�}�}B~g~�~�~g��$�c���ƀC�ǁ��+�������؂�	�2�a���׃�D������ �H���΅���_���ӆ�5�M�p����O�v���S������Y�b�h�r����������2�\�����ۋ��;�b�������P�y���ۍ��"�g�����5���g����i��q��s�����{��h�y�֗�K�u����
�i����B�u���њ�S�ś��@�b���̜�^����|����
�f�����M�c��R�9��ڤ��h�ͦ.�>�>�������]���ت@�|����*�W�y���-���ԭ�/�z�Ȯb���ί�� �_����)���j�m������&����q�����G����>�����<�c�ܸ\�ǹ6�m�ֺ&�s�ͻ��$�D�2�������)��.�e�����^�u���0����n������+�G�d���������-�?�h����f����7�������J��������*�����������/�z����M����A�`�������&�{�����0�Q�y�S�u���!�����8�q����A�����F�����
���G�����)�}���	�3�����c�����&����J�����:�u��5������E�o���
�@�S�r����������&�����N�������^�������"�K�����.��������(�X����������F�q�����q���C�{�����������z������V�������I����F����@����'�����_�����@����R��z��(q��.��@���Z�n�2��@c}���.[��P}�	=	�	;
o
�
A���O��E
`
�
=v�	A��8j�,j���
@}�����4����E����s���H��(�J�Fe:x������l��8 b x � � � )!,!I!_!�!�!�!"�"I#x#�#"$�$O%�%�%-&�&�'�')(z(�()0)b)�)�)�)*5*j*�*�*;+X+�+�+K,},-�-�-�-�-&.B.q.�./9/d/�/�/0i0�0�001n1�12�2�2;3�3�3�34K4�4�4�4 5K5a5n5t5�5�5.6~6�6&7Y7�7�7I8u8�89p9�9:�:�:�;K<�<�<�<=h=�=�=>g>�>J?�?�?�?j@�@AIA�A�A B�B�BC:CrC�CDED�D�DE;E�E�E�E'F[F�F�FEGnG�G�GHPH�H�H<I�I7JoJ�J�JKZK�K�KXL�L�LfM�M�M1NO�OEP�P�Q�QR2R[RmR�R�R�RS7SWSuS�S�ST.TgT�T�TUOU�U�UVV�VNW�W�W�WlX�X�XtY�Y`Z�Z�Z�Z"[_[�[�[\K\�\�\�\:]�]�]�]1^�^_$_t_�_`*`J`p`�`aVa�a�a9b}b�b�b�cMd�d�d'eEeWf�fCgwg�gh}h�h7i�i"j�jkck�k�k)lUl�lm�m�n:o
pep�q�q/r�r�rQs~s�s-tYt�t�tu]u�u�uOv�v?w�w�wxgx�x�x:y�y`z�z3{�{�{�|}S}�}�} ~�~�~�~(a��\����k�ʁ�D�f���ނ#���������ч��J���Չ!�z������c���ċF���̌2�������U���ď؏����Y�������I����K���ғ.�O�q���Δ�>���2������ڗ����ט)�f����E�h�����l���ޛ�
�T���ۜ��������������W�����E����q�ġ=�_����E������u����;�X�������K�|�ѧ'�p�����S���=���}��F�s���ڬ
�����F���!�F���f���
�[����q�ײ�%�c�����}��.�f�õ+�����j�Ϲ�F�t�K���'���s��l���#���ſ��0�_��c���\�����������K��=�������
�=�������k������R�������@�l���l���y�����;���z�f�������/����������-�s���)�\������h���k���������������f��������h���a���U������i���N���E���$�������5�\�������w��r��������������(�s���F�������^���b���@����G��J����Q����@������B�����
�h���N�q�����'�,Jn��2Js��,��� �	��=��-��R���	
,
e
�
b�_?
~
�
�
7FX���&k�UoGo�Sz���>f���7f}���'U����-Z^���F��j���W��[w��:\��J��b����D � !C!�!"y"#4#`#�#�#�#$&$b$�$H%�%G&�&'�'�'(6(n(�(�(L)q)�)�)J*�*�*�*$+B+p+y+�+�+�+F,�,--%-2-?-J-�-�-..?.Q.v.�.�./N/�/�/0&0�0�0�011~1�1�12P2�2�2'4w45C5�5e6�6z7�7�7�78C8k8�8�89292:x:�:;&;X;�;�;<R<�<�<�<o=p>�>�>?u?�?@@J@w@�@3A]A�A�A0BvB�B�B	C+CPC{C�C�C$DAD�D�DE*EWE�E�EF&F4FBFRFpFG$H@HwH�H�ImJ�J�JK&KhK�K�K�KLOLqL�L�L�LMNMaMxM�M�MNBNyN�N�N"OAO\O�O�O�OP,PYP�P�P�PQ<Q_Q�Q�Q�Q!RTRuR�R�RS"SfS�ST@TsT�T�T�T"UAUhU�U�U�UV+V|V�VWfW�WXdX�X�X[Y�Y[Z�Z[�[
\E\�\�^_?_�_T`�`�`�`.ara�abObvb�b!cEc�cfd
e4eUe�ef�f�f�fgRgig�g�g�g6hTh�h�hi_i�i�ij-j�jkkk�k9l�l�l�lm5mlm�m�mIn�n�njo�opDppp�pqPq�q�q�q.rs�s�tuu�u�uv3vLvcv�v�v�vwXw�w�w8x�x*y�y�y(zPz�z�{�{|T|�|�|�|	}�}�~�~)`��H�~�Ā��1����5�g���Ђ"�i�����F���τ����o���͆�-�c����/�{�����B�h�{�։�,�V������I�x�����Q���ь�X�ٍ���9�z������B�~���ސ�7�l�������;�������V�~���ߓ�-�r����5�Z�u����)���G�e�������U����9���˚�+������ݜ?�<�r���Ğ�0������<���8�����%�_�¥�R�����������+�j���C�Y���ܩ�6�q�����m�W�����b��M�������	�b�z����������N�������
�R������J�����ж��$�L�~���ܷ�7�f����M�|����,�m�ƺ!���Ļ�5�e���ۼ�t���ν��d�;=�j����6�o������*�����~��^����������<�Z��������1�����R����8�������2�T�������K����������\��������"�V�������S�~��������1�Q�|������C�n�����3�����Y�v������%������"�K��������C�s����O�n���������,�b��������G�^�u�������#�V��������3�\������U������Y�{�������a�������(�q��������N�x���������%�8�����&�S����(������g�����0���������"������K�~�=�}��b����2�M������E�|�����,�e������i�����7�}���#�]�|������b����v���6�X�#�}����������1�}���'������p���A�Z����8���?�������M�u��A�a������
�C��I�Gu����
��� s��%�0Y��<y���	�	�	+
�
�
1s���)Y����
E
�
Iz�TX���#�u�E��
3W���6��I��\���f�e���M���7��h��9]��9Y|��K���  & | � �!�!b"�"J#i##�#�#v$�$N%�%�%$&o&�&�&='U'�'7(�(i)�)V*}*�*�*�*�*�*�*�*�*+>+A+T+�+�+5,8,b,�,�,�,�,-m-�-@.�.�.1/K/i/�/0-0V0�0�0)1~1�1282m2�2>3�3�4"5_5�5�5�6�67O7s7�7�7�7808q8�8�8�89>9f9�9�9�9�9�9�9
:A:x:�:�:;;F;o;�;�;<<?<y<�<�<=$=F=k=�=�=�=@>�>�>�>:?h?�?�?!@R@l@�@�@A;AYA�A�AB'BRB~B�BCCNC�C�C�CDAD�D�DE#EIEvE�E�EF'FAFYFtFwFG{GLH�H�H�H=I�I�I�I
J;JiJ�J�J�J7KzK�K�K
L1LLLlL�L�L�L�L*MYMwM�M�MN3NWN�N�N�N�N�N�N OKO�O�OPP�PQ:QsQ�Q�Q�Q�Q�Q�QR�R�R�R/SrS�T*UgUV�V�WX[XyX�X�X.YOY^Y�Y�Y�YZKZ|Z�Z�Z[;[t[�[�[�[\A\�\�\]m]�]�]�]�]^^1^g^�^�^�^%_M_�_�_`>`q`�`�`a0aqa�a�a�ab3bWbb�bc@cfc�c�c�c�c�c%dOdid�d�d�d"ece�e�e�ef*fVf�f�f!g2g\g�g�h-i{i�i�ijjLj�j�j=kpk�k�k(l+lol�l�l�lm�m�noo<o�o�op(pVpup�p�p�pq,qEqaqq�qr"r<r`r|r�r�r1scs�s�sXt�t^u�u�u�vwjw�w�x�xIy�y�yz?z9{�{I|j|�|�|}E}�}�}�}0~i~v~�~3j���c�����%�����.����z�Ƀ�u�Ą��Y��������g��V�͈������D���,�M�u��������E�l�����%�f����
�K����T�����đ.�ϓY�|���ޔG�r���	�E�v������m������4�����n��@�o�ΛD��?���a���,�{��A�w����8�ƢF�գV���
���ƥ�%�I�����b����W�è2�Y�Ʃ7����X���g���Ҭ��0�f�������o��'�s����7����ӱq�ʲ&�x���:����ڵ��ζ�9�n�ͷ?����`�˹�;����R��D������n�����R���ؾG�������/�~���e������������F�����L�v�����;�������
�.���!�I�v���j�����(�\�������0�f�����#�U����F�����%�m�������2����M���5�������=�w���P���Z���%�c�����K�����'�p���<�����&���2���n�/������7�X������E�����s�������	�L�����2�n�����R���
�i������G����������(�E�l���������&�n��������y��������V�������)�����%�?�q�����8�x�����
�>�K�������+�N�{�����7�e�h��������L�v������j����d���V�������8�d�����&��^�a�d�g�j�m�p�s�v�y�|����������������������������������������������������������������������l�o�r�u�x�{�~������������������������������������������������������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b�e�h�k�n�q�t�w�z�}�������������������������������������������������������������������������
�
�e�h�k�n�q�t�w�z�}����������������������������������������������������������������������

"%(+.147:=@CFILORUX[^adgjmps��"l������?b��;>��q�e��=|��	K
}
�
�
=@CFI}����������������������������������������������������������������

q
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
 #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|����������������������������-0369<?BEHKNQTWZ]`cfilorux{~�������������������������������������������ux{� #&),/258;>ADG��z�:t��O���C�����P��X���Y��_�����GJM��Lz}��������V � !\!�!�!&"V"�"�"�"#J#�#�#$M$"%�%�%r&�&�&''''''' '#'&')','/'2'5'8';'>'A'D'G'J'M'P'S'V'Y'\'_'b'e'h'k'n'q't'w'z'}'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'�'(((
(
((((((("(%(((+(.(1(4(7(:(=($_(b(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))))))))) )#)&))),)/)2)5)8);)>)A)D)G)J)M)P)S)V)Y)$_)b)e)h)k)n)q)t)w)z)})�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)***
*
*******"*%*(*+*.*1*4*7*:*=*@*C*F*I*L*O*R*U*X*[*^*a*d*g*j*m*p*s*v*y*|**�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++	+++++++�+
,2,�,�,!-Q-�-�-.=.m.�.�.�.�../]/�/�/"0=0b0�0�0�01#1T11�1�1!2L2�2�2�23,3S3�34=4y4�45:5~5�5Z6�6�6�6
7-7M7�7�7M8|8�8�8�8�9�9:::::::: :#:&:�:�:�:�;�;�;�;<`<�<�<(=�>_?|?�?@�@�AYBtB�B�B�B�B+CQD�D�EF*FPF�F�F�F�F�F�F�F�F�F�F�F�F=GgGjG�G�G�G�G�G�GHHH"H%H(H+H.H1H4H7H:H=H@HCHsHvHyH|HH�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H,I/IIIlIoI7J:J=J@JCJFJIJLJOJRJUJXJ[J^JaJdJgJjJ�J�J�K L#L&L)L,LhL�L�L�LM,MDM�M�M�M*N�N�N�N�N�N�N�N�N�N�N�NOVOYOePhPkP�P8Q�Q�R�RT�TUVQVfV�V�W+X�X�XY5Y�YCZ�Z�Z�Z�Z
[*[E[a[�[�[0\[\i\�\1]�]�]^=^\^�^�^�^_S_{_�__`�`�`aba�ablb�b�b�bc0cQcnc�c�c�cd�d(e�e�e�ef3faf�f�f9g}g�g�g`h�hi_i�i�i�i�i�i*jsj�j�j�j	k,k/klk�k�k�k�k�k�k�k�k�k4lol�lmAm�m5n�no>oxo�o�op�p�pq�qr|rs"sis�stIt�t�u�u�u!vOv�v�vCwkw�w�w=xux%y�y+z�zP{�{=|r|�|�|}d}�}�}
~1~X~[~�~4Su��{�����݀�%�5�q���݁(�m�ނ�:���σ
�B�{�΄�v�܅�U���	�~�ȇ0�����/�f����Q�Њ;��������Y�����8����.�U�Ə�����G���ё�G�����D�|�ؓ+�b���Ĕ���[������4�I���ٖ�g�������� �H�p���֘(�o���+�~��E������.���>�o�������f���ۡ��2�����֢�(������O������N���ȥ5�P���v�����+�J������2�w�ɩ�0����9�~�׫�b�ì;���^������<���ԯ	�9�^�}����� �o����]�����]�����1�\�s���׵+������(�\���-�p�����d����»������x�н�'�>�����̾���F�i���Q������������E�|��4�����U���8����u���q����v���*�s����K�i���/���M���6�9�|������,�G�����r��������������2�5�8�;�>�A�D�G�J�M�P�S�V�Y�\�_�b�e������^�a�d�g�j�m�����#�W�y�|�������1�j�����e�h�?�����
�}� ��������;�������K�����_����Z����V�����J������������������������������������������������� �#�&�)�,�/�2�5�8�;�x���
�=�|�������^��������D�G���9���m�������[���������#���}�7������������6�~�������������8��n������M�{�������F�����<h�V��R�Y��7|����5���	|

���
^��4�����(G�'���3Y\��a�p��:p���� �!�"�#)$�$h%&}&�&'4'H'b'�'�'N(�(�(�()7)F)g)*t+�+�+�+*,e,�,�,-r-�-/.�.�.D/(1S1g34�4�4+5�5�5
7�7�7>88�8m9�9�9�:Q;�;�;<,<J<�<�<�<�<�<�=�=@>C>F>.?�?Y@�@�@AOA�A�A5B�B'CbC�C7D�D�D�E9F�F�GzHOI�I�I/JaJ�J�JK2KVK{K�K�KL>L
M`M�MN0NvN�N�N�NOOO�O�O�PcQ%R�TKWtW�W�W
XlX�XYyY�Y�YMZ�Z�[)\�\u]^P^�^�^$_5_^_"`%`s`�`�`5a�a�a�a	b*b]b�b�b�b�bc c:cXckc�cqd�d$ewe�e
gIh�hsj�j�j�j�jk8khk�kAl�l5m�m�mAn�n�n8o�o�op_p�p�p�q�qs�sttit�t�tdu�ugv�vXw�w3xxxy�y�y�z{2{�{�{4|n|�|}I}r}�}�}~?~k~�~
V�*����N�����]�{�������ӂ���!�7�Z��������"�T�����/�����M�ڇa���s���щ��%�R������*�S������
��_�Ǐʏ'�{�ϐ�Ñl�I��M�hashchkisamchkNEIJAKan ikkje opprette fila '%-.200s' (Feilkode: %d - %s)Kan ikkje opprette tabellen '%-.200s' (Feilkode: %d - %s)Kan ikkje opprette databasen '%-.192s' (Feilkode: %d - %s)Kan ikkje opprette databasen '%-.192s'; databasen eksistererKan ikkje fjerne (drop) '%-.192s'; databasen eksisterer ikkjeFeil ved fjerning (drop) av databasen (kan ikkje slette '%-.192s', feil %d - %s)Feil ved sletting av database (kan ikkje slette katalogen '%-.192s', feil %d - %s)Feil ved sletting av '%-.192s' (Feilkode: %d - %s)Kan ikkje lese posten i systemkatalogenKan ikkje lese statusen til '%-.200s' (Feilkode: %d - %s)Kan ikkje lese aktiv katalog(Feilkode: %d - %s)Kan ikkje låse fila (Feilkode: %d - %s)Kan ikkje åpne fila: '%-.200s' (Feilkode: %d - %s)Kan ikkje finne fila: '%-.200s' (Feilkode: %d - %s)Kan ikkje lese katalogen '%-.192s' (Feilkode: %d - %s)Kan ikkje skifte katalog til '%-.192s' (Feilkode: %d - %s)Posten har vorte endra sidan den sist vart lesen '%-.192s'Ikkje meir diskplass (%s). Ventar på å få frigjort plass... (Feilkode: %d - %s)Kan ikkje skrive, flere like nyklar i tabellen '%-.192s'Feil ved lukking av '%-.192s' (Feilkode: %d - %s)Feil ved lesing av '%-.200s' (Feilkode: %d - %s)Feil ved omdøyping av '%-.210s' til '%-.210s' (Feilkode: %d - %s)Feil ved skriving av fila '%-.200s' (Feilkode: %d - %s)'%-.192s' er låst mot oppdateringarSortering avbroteView '%-.192s' eksisterar ikkje for '%-.192s'Mottok feil %d - '%-.192s' fra tabell handterarTabell håndteraren for '%-.192s' har ikkje denne moglegheitaKan ikkje finne posten i '%-.192s'Feil informasjon i fila: '%-.200s'Tabellen '%-.200s' har feil i nykkelfila; prøv å reparere denGammel nykkelfil for tabellen '%-.192s'; reparer den!'%-.192s' er skrivetryggjaIkkje meir minne. Start på nytt tenesten og prøv igjen (trengte %d bytar)Ikkje meir sorteringsminne. Vurder å auke sorteringsminnet (sorteringsbuffer storleik) for tenestenUventa slutt på fil (eof) ved lesing av fila '%-.192s' (Feilkode: %d - %s)For mange tilkoplingar (connections)Tomt for tråd plass/minneKan ikkje få tak i vertsnavn for di adresseFeil handtrykk (handshake)Tilgang ikkje tillate for brukar: '%-.48s'@'%-.64s' til databasen '%-.192s' nektaTilgang ikke tillate for brukar: '%-.48s'@'%-.64s' (Brukar passord: %s)Ingen database valdUkjent kommandoKolonne '%-.192s' kan ikkje vere nullUkjent database '%-.192s'Tabellen '%-.192s' eksisterar allereideUkjent tabell '%-.129s'Kolonne: '%-.192s' i tabell %-.192s er ikkje eintydigTenar nedkopling er i gangUkjent felt '%-.192s' i tabell %-.192sBrukte '%-.192s' som ikkje var i group byKan ikkje gruppere på '%-.192s'Uttrykket har summer (sum) funksjoner og kolonner i same uttrykkKolonne telling stemmer verdi tellingIdentifikator '%-.100s' er for langFeltnamnet '%-.192s' eksisterte frå førNøkkelnamnet '%-.192s' eksisterte frå førLike verdiar '%-.192s' for nykkel %dFeil kolonne spesifikator for kolonne '%-.192s'%s attmed '%-.80s' på line %dFørespurnad var tomIkkje unikt tabell/alias: '%-.192s'Ugyldig standardverdi for '%-.192s'Fleire primærnyklar spesifisertFor mange nykler spesifisert. Maks %d nyklar tillattFor mange nykkeldelar spesifisert. Maks %d delar tillattSpesifisert nykkel var for lang. Maks nykkellengde er %dNykkel kolonne '%-.192s' eksiterar ikkje i tabellenBlob kolonne '%-.192s' kan ikkje brukast ved spesifikasjon av nyklarFor stor nykkellengde for felt '%-.192s' (maks = %lu). Bruk BLOB istadenforBare eitt auto felt kan være definert som nøkkel.%s: klar for tilkoblingar
Version: '%s'  socket: '%s'  port: %d%s: Normal nedkopling
%s: Oppdaga signal %d. Avsluttar!
%s: Nedkopling komplett
%s: Påtvinga avslutning av tråd %ld  brukar: '%-.48s'
Kan ikkje opprette IP socketTabellen '%-.192s' har ingen index som den som er brukt i CREATE INDEX. Oprett tabellen på nyttFelt skiljer argumenta er ikkje som venta, sjå dokumentasjonenEin kan ikkje bruke faste feltlengder med BLOB. Vennlisgt bruk 'fields terminated by'.Filen '%-.128s' må være i database-katalogen for å være lesbar for alleFilen '%-.200s' eksisterte allereidePoster: %ld  Fjerna: %ld  Hoppa over: %ld  Åtvaringar: %ldPoster: %ld  Like: %ldFeil delnykkel. Den brukte delnykkelen er ikkje ein streng eller den oppgitte lengda er lengre enn nykkellengdenEin kan ikkje slette alle felt med ALTER TABLE. Bruk DROP TABLE istadenfor.Kan ikkje DROP '%-.192s'. Undersøk om felt/nøkkel eksisterar.Postar: %ld  Like: %ld  Åtvaringar: %ldYou can't specify target table '%-.192s' for update in FROM clauseUkjent tråd id: %luDu er ikkje eigar av tråd %luIngen tabellar i brukFor mange tekststrengar felt %-.192s og SETKan ikkje lage unikt loggfilnavn %-.200s.(1-999)
Tabellen '%-.192s' var låst med READ lås og kan ikkje oppdaterastTabellen '%-.192s' var ikkje låst med LOCK TABLESBlob feltet '%-.192s' kan ikkje ha ein standard verdiUgyldig database namn '%-.100s'Ugyldig tabell namn '%-.100s'SELECT ville undersøkje for mange postar og ville sannsynligvis ta veldig lang tid. Undersøk WHERE klausulen og bruk SET SQL_BIG_SELECTS=1 om SELECTen er korrektUkjend feilUkjend prosedyre %-.192sFeil parameter tal til prosedyra %-.192sFeil parameter til prosedyra %-.192sUkjend tabell '%-.192s' i %-.32sFeltet '%-.192s' er spesifisert to gangarInvalid use of group functionTable '%-.192s' uses a extension that doesn't exist in this MySQL versionA table must have at least 1 columnThe table '%-.192s' is fullUnknown character set: '%-.64s'Too many tables; MySQL can only use %d tables in a joinToo many columnsRow size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBsThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if neededCross dependency found in OUTER JOIN; examine your ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerCan't load function '%-.192s'Can't initialize function '%-.192s'; %-.192sNo paths allowed for shared libraryFunction '%-.192s' already existsCan't open shared library '%-.192s' (errno: %d %-.128s)Can't find symbol '%-.128s' in libraryFunction '%-.192s' is not definedHost '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.255s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192sInvalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used.The host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionSomething is wrong in your syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetMottok feil %d '%-.100s' fra %sMottok temporary feil %d '%-.100s' fra %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for '%.256s'XAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionLike verdiar '%-.64s' for nykkel '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTTilgang ikke tillate for brukar: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setPartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionLike verdiar for nykkel '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\��6�6�polish/errmsg.sysnu�[�����"��	T��\�=n��!^��_��!^��-X���
S��	]���%	<	{	�	�	�	
/
N
h
�
�
�
.l���Au����#
g
�
�
;��$d���"C�������.a���B��X��hv���
*H����*;�p�)Gt���;��=��������g�� n � � !,!l!�!�!�!�!&"Q"{"�"�"#>#y#�#�#%$_$�$�$=%c%�%�%,&[&l&�&�&�&&'E'd'�'�'(Q(m(�(�(�(9)Z)�)�)*�*�*F+�+,K,�,�,�,3-y-�-..P.�.�./4/u/�/�/0.0K0�0�01/1q1�12Z2�2�2�23=3l3�34$4W4�4�4�45+5J5o5�5�5�5,6�6�6�6
7.7�7�7818R88�89G9q9�9�9:K:�:�:;/;�;f<�<=�=>">C>�>�>�>>?Z?�?�?0@�@�@�@]A�A�A�ABABsB�B�BC=CRCgC|C�C�C�C�CDCDhD�D�DiE�E�E�E�EF@FaFvF�F�F�F�FG(G?GWGlG�G�G�GHBHdH�H�H�H*IlI�I�IJ)J^J�J�J�JfK�K�K~L�L�LMMIMxM�M�M�MNENzN�N�NO>OcO�O�O�O�OP.PYPzP�P�PQ5Q`Q�Q�Q�QR5ROR�R�RS0SGS~S�STqT�T�T0UcU�U�U�U VPV�V�V�VMWzW�W|XAY�YNZvZ�Z[G[�[�[\g\�\�\U]�]^A^Y^�^_(_d_�_�_<`�`2ara�abdb�b�b1c{c�cdad�d8eYe�e�e,fXf�f�f�fgQg[geg�g�g-hRhnh�h&i�i�i(joj�j�jk^k�kl6lxl�l	m5mjm�m�m"nTn�n�noo�o�oGptp�p�pqSq�q�qSr�r�r�rsRsss�s�sbt�t�tu8uZu�u�u�u�u
vZv�v�v�v3w�w�wx(xHxZx�x�x�xy%yy�y�yz+zIz�z�z{B{�{A|�|�|?}m}�}�}�}~'~w~�~�~;g����}���Ԁ����#�_���Ղ
����B�r�؄���3�P�y���ޅ�M���ʆ�1�g�����D�f�����K�|������(�����*�f���͋�3���������ƌЌ،�6�V�y���̍��"�C�����ώ�F�������"�?�i�����C�|����Y����,���5���`���\�*������W�������/�Q����N��������O����E������	�O�������[�ޡJ���ޢ!�V���������v�D�����
�k�{�{�ѫ��7���Ҭ�}����+�g������j�˯�N�l������ޱ�<�]���ܲ/�f���������B�c�߶L����5����?�{��1�\�y�������s����c���
�@�#�a���o�M�����)�f�+�k������������m���T�����.�C�h����������'�j�|�����=����K�t����<�����@���	�g��������)�l��� �T���%�U�~������2�c����4�m���������(�j�����������P�����@�����9�V��������r�����R�|�!�%����+�o�1�c�����B�����L�~���(�K�������S�������3�&����T�o���,�����
�5������A�k�����(�w�����%�K�q��������C�h�������A���;��������-�\���^����P�����C����Z���������4�p��:�����B�����I�Q�*q��3w�\��?��Y�{�(o����	-	�	�	�	�	�
�
�
l�����b
�
�
%R��1��5���\��^����)`����.^�B���/g��3N�� �n��*{�5��Tf��� ' D !P!�!�!J"�"�"�"�"'#Q#|##�#�#�#$2$V$#%�%�%@&u&*'�'�'7(�(/)�)(*|*�*3+T+�+�+�+
,5,f,�,�,�,-�-�-�-(.�.�.U/�/0/0O0y0�0�0D1~1�1�12D2�2�2_3�34c45D5�5
6g6�6�67D7q7�7�78F8q8�8�8�8�89T9�9�9L::�:�:o;�;�;+<�<�<+=�=!>�>q?�?�?@?@�@�@
ACA�ABpB�BC"C�C�C(DoD�DEFE�E�E+F`F�F�F?GkG�G�G'HaH�H�H%IMI�I�IJkJ�J�J	K.KvK�KLbL�L]M�M�MN:N�N�NO~O�O
P�P�P	QWQ2R�RkS�S�T	U8UXU�U�U�UV#V>V]V}V�V�V�V+WTW�W�WX-XuX�X�X?Y�Y�YtZ�Z�Z[�[�[�[�\�\�]�]�]^H^�^�^_B_q_�_�_ ```�`�`aWab<bJb�b�b4cPcpc�c�cBd|d�d�d_e�e�ef�fsg�ghMhkh}ijij�j�j*k�kl]l�lHm�m4n�n�n!oOo{o�o=p�p�q`r3s�s�tuUu�u�uwv�vwSww�w�w;x�x�xyuyzez�z�z>{�{�{|`|�|�}~Y~�~!�4�y���F���ہ�N��������׃5����1�j������I�ن#��߉��#�p�����G���؍�E������l����X�̐:���C�{������>��������$�o�ɕ�q�����T�u���ϗ�8�d���X�ə:������ś��O���՜�k���ĝ�E���Ԟ�-�0�z����E���Ӡ�2���ѡ�<�}�Т$�k�ӣ*����c�����D�k����?���ȧ�a�~�¨7����q�����M���۫�B�y�֬c�٭��2�l���˯�3�7����l��G�l�����0����>������K��������	�T����Q���������+�l���q�׾M�ڿ������I������V��������������������q�A�c������0�c�������������E�x�������f���������%���a������������U��������7�S����O�����C������������������@���;������5���������{����+����t���k���J�����[�������!���<��������<�������N�����l������������f���m��p��*�w���f�%����h����3��t���M�Rp���Xp���R���F�/�	c	�	
S
�
�
5x��1
R
�
�
���e���)]l~�� L��1{�)m��7y���d���:]�8���M{���%S����l��*���}���+����,`�� p � � �!"�"�""#j#�#1$i$�$D%�%5&Z&�&�&�&'.'L'�'(n(
)m)�)5*�*�*++\+�+�+�+r,�,�,�,p-�-�-#.J.h.�.�.�.�./l/�/50@0K0X0e0p0�0�061D1e1w1�1�1�1?2t2�23&3L3�3�3
4)4>4�4�45D5v5�56M7�7>8i8�8�9":�:�:�:;6;i;�;�;
<5<X<X=�=�=*>L>~>�>�>)?x?�?�?@�@�A�A�A>B�B�B&CDCpC�C�CYD�D�D
EVE�E�E�E/FQFvF�F�FGJGgG�GH'HPH}H�HI*ILIZIhIxI�I)JJKfK�K�K�L�M�M
N2NLN�N�N�NOEOuO�O�O�O"PEPtP�P�P�P�P&QhQ�Q�QRHRgR�R�R�RS-SRSS�S�ST9TbT�T�T�TUGUzU�U�U�U+VHV�VW4WfW�W�WX#XHXgX�X�X�XY-YQY�Y�Y<Z�Z�ZD[�[�[\�\�\�]�]?^�^3_k_`�a*bebczc�c�c"dTd�d�d.eue�efGfkf�f�g3hZh{h�h1i�i�ij,jxj�j�j�jk\kzk�k�k8l�l�l�l*mSm�m<n�n�n_o�o�op5p[p�p�pqoq�q�q�r�r-sjs�s�s4tvt�t�tuTu>v
w�w�x�xy:yYyry�y�y�y�y9z~z�z%{^{�{P|�|}N}v}�}�~Cz���/�!�́�O������n���� �W���)�[�������H�����l������+�"���Ή�
�S����6�U������h��������R�|���ō)�o���ێ$�w�����*�~�����5�_�����2�E�h������5�]������#�a����	�6�|���Ԗ�'�S���ޗC�[�����Ƙ�4�O���m�������{�Ŝ
�_����+�Q���)�ǟ�e�b������	�V�Ϣ��2�b��^���D�K�����x���ީ�#�Ѫ�Q�����i����-�\�����$���}���ϯ��&�s�ڱ#���/�������
�.�2�ٵ	�B�t�ƶ��0�x�����p�ι���$�J�r���պ�2�]������s���ʼ�R����G�����[������;�����"����c�����+�\�������%�P�����E���(������!�$�'�b��������2�W�����x��)�^������X�z������q�������1�
���������*�H�|������y��������4�W�w������>�i������Y����������'�K�����.�H�q������<�i����<�u����������R���������6�m����������I�|������7�Y�������7�{�����4��������
���������N�����+���)�>�t��������#�K�^����L�y���'�N�����@�������V���$���"�H�����;�q���c���(�����)�X�s���	�>�k������R������<������]�����I��������<�����1�����\�~�I���������1�W����M����*�����(�g������^���e��9�@��1�s���g���0i�o	?m����3�4�F��	K	�	(
V

�
�
b���)�
Q
"W��$O��@k#o�
?z~��I�>��)k��0Y}��%\��=o��2���8��-���?s��']�6�� : _ � � !_!!�!�!"&"q"�"�"#F#L#�#�#�$�$�%
&p&�&�&�& '�'(t(�()J)�)�)�)c*{*�*]+�+�,-|-�-�-�-�-�-..	.
...d.g.z.�./[/^/�/�/�/�/010�0 1f1�1$2W2q2�2�2(3S3|3�34O4�4�455^5�5�5d6�6�7H8�8�8�8�9:C:u:�:�:�:�:;;V;�;�;�;<:<d<�<�<�<�<�<=%=3=g=�=�=>&>=>l>�>�>?'?8?e?�?�?@*@J@l@�@�@�@AfA�A�AB`B�B�B�BGCxC�C�CD&DaDD�D�D+EMExE�E�E(F8FtF�F�FG>GgG�G�G&HIHoH�H�H�H.IMIgII�I�IBJ�JrK�K�KLcL�L�LM0MaM�M�M�MN]N�N�NO0OWOrO�O�O�O�OPPPP�P�P�P)QYQ}Q�Q�Q�Q
RRRFRqR�R�R@SCS�S&T`T�T�T�T�T�T�T
U?U�U�UVUV�V�WPX�X:Y�Y[:[�[�[�[\T\u\�\�\�\
]?]q]�]�]�])^a^�^�^_!_8_g_�_�_5`�`�`�`�`a2a5aWa�a�a�abKbsb�b�b'cdc�c�c�c.dVd�d�d�d�d6eYe}e�e�e:fff�f�f�f�f
g gKgug�g�g�ghHh�h�h�hi,iPi|i�i�iGjXj�jklSl�l�l�l)m@mrm�m�mcn�n�n�nNoQo�o�o�op@p�p�q'r8rbr�r�r)sNs|s�s�s�s�s6tRtkt�t�t�t(uHubu�u�u�u�uWv�v�vw~w�w�x�x�x�y8z�z${�{
|o|�|}:}e}_~�~o���A�k���Ѐ�V������Y���ʂ�;������K����T���1����A�������A�ȉ$����|��%�Ќ�j���R�s���;�����1�k���Ր�K���ϑ�3�q���*�z���ړ�T��������m���Ҙ/�k���ߙ�E���Ϛ(�ƛZ��� ����f����j�	�e�����R���)�g���פ�^��l���|�ܧ3�����K�o�ʩ#����8�}��X���]����~�Į��ܯ���6�V�����ܰ����M���޲�]���������L���ݶ`�ܷ?��Ĺ�-�_����e�������(�a����x��j����E����%�x�����m���'����U�����9�����2�������l�����r�������a������0�T��G�o���������N��������V�������I�{���1�l�����K�������!�X�
�>�s���[������c����v������K������q����M�����b�����L���X����U�����)�]�~�����>�k���#��������/�r�����&�X�����x���0�����	�=�m�������4�N�k����������L��������D��������D�|������O�����K�e������^�������3�d�q�����Q�t������]����������8�r�������������D�|������*�^�����)�L�4�������������������������������������������������������������������� #&�����������������������������"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-03���������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~����������H���"%(+e��ad�C�		�	
$
c
�
�
�
7q
�
�
�
cfilo�������������������������������	��������������

"%(+.147:=@CF��������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~�����������������������������������������SVY\_behknqtwz}�������������������������������������������

"%���%(+.147:=@CFILORUX[^adgjm���`���u��4i����;v��~��;�����% � m!p!s!�!
"r"�"�"�"�"�"�"�"�"�"�"|#�#&$�$�$�$L%|%�%�%�%-&p&�&'-'s'H(�(�(�)�)�)1*4*7*:*=*@*C*F*I*L*O*R*U*X*[*^*a*d*g*j*m*p*s*v*y*|**�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++	++++++++!+$+'+*+-+0+3+6+9+<+?+B+E+H+K+N+Q+T+W+Z+]+`+c+�+�+�+�+�+�+�+�+�+�+,,,
,
,,,,,,,",%,(,+,.,1,4,7,:,=,@,C,F,I,L,O,R,U,X,[,^,a,d,g,j,m,p,s,v,y,|,,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---	--------!-$-'-*---0-3-6-9-<-?-B-E-H-K-N-Q-T-W-Z-]-`-c-f-i-l-o-r-u-x-{-~-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-.......... .#.&.).,./.2.5.8.;.>.A.�.0/X/�/0G0w0�0121c1�1�1�12#2T2�2�23H3c3�3�3�34(4I4z4�4�4
5G5r5�5�56(6R6y6�6<7c7�7�7*8`8�89�9�9�9:3:S:s:�:�:s;�;�;�;<�<�<.=1=4=7=:===@=C=F=I=L=�=>>�>�>�>?4?�?�?�?N@B�B�B�B=C�C�DE�E�E�E�E�EQFwG�G
I2IPIvI�I�I�IJJJJJJJJJcJ�J�J�J�J�J�JKK?KBKEKHKKKNKQKTKWKZK]K`KcKfKiK�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�KRLULoL�L�L]M`McMfMiMlMoMrMuMxM{M~M�M�M�M�M�M�M�M�M�NFOIOLOOORO�O�O�OP=PRPjP�P�PQPQ�Q�Q�Q�Q�Q�Q�QRRR
R,R|RR�S�S�S�S^T�T�UV;W�W=X'YwY�Y�Y�ZQ[�[�[2\[\]i]�]�]�]�]3^P^k^�^�^"_V_�_�_�_W`�`a(aca�a�a�a	b@byb�b�b�c�c�c+d�d�d.e�e�eff1fVfwf�f�fggBg
hNh�h�h�h4iYi�i�i�i_j�j�j
k�k�k&l�l�l�l�lmmPm�m�m�mn/nRnUn�n�n�n�n�n�n�n�n�n�nZo�o�o+pgp�p[q�q;rdr�r�r�r*s�stEt�tEu�u+vHv�v�v6wow�w�x�xyGyuy�yziz�z�z�zc{�{K|�|Q}�}v~�~c�� �<���܀�3�W�~�����A�Z�y�����������;�K�[���̄�N����)�`�ۆ��0�h����?����<�{���/����V����U���Ì�w���a�̎4�����̐�^����T�{��$�B��!�m�����)�m�ȕ5�8�j�����Q������������"�>�Z�o�����?�������1�F�n���ƛ��N���%�Q���+�k�؟>�ޠT�ԡd����<�ʣ8�����&�B�X���ӥ���N�Ԧ�B�u���˧9�t����[�v����Ū�Q�p���̫�X����,�V���
�_���������a�ư�����
�b�����/�_�����ó�F����+���޵
�D���Ƕ<�-�W�����Ҹ��Q�����N����S���λ1�@���'����9����4�����7�M�d��������l����w�������4�����k���8�Z����{���^���4��������C�����P�����'�q�����U���s���\�_�������7�R�m���������������<�X�[�^�a�d�g�j�m�p�s�v�y�|�������������-���������������$�I�}����������W����������e�����3���F���?���	�a������q���%�����@�����2�|����p����������������
�
�������"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�����0�c������"�����C���	�j�m���_� ���������������"�I�����]�����:�"��\����)����������^�������Ds���'l�b�%|�x�8�<�]����	
[
&���
3�D��'��$Z� �9�Nm��M�D�B�Y��(��$�1 � !7!`!�!�!"�"�#�$�%�&O'�'�(E)�)�)?*Z*n*�*�*�*t+�+�+	,(,],l,�,D-�.�.�.	/P/�/�/�/C0�0�0U1�12j2N4y4�6?7�7�7Q8�8	90:�:;d;�;�;�<�<=�=w>�>	?4?R?p?�?@@@@�@
AfAiAlATB�BC�CDBDuD�D�D[E�EMF�F�F]G�GH�H_IJ�J�KuL�L�LUM�M�M�M4NXN|N�N�N�N6OdO3P�P�P-QVQ�Q�Q�QRERuR�R�R�S�TKU	XqZ�Z�Z�Z0[�[�[?\�\�\]s]^�^O_�_�`5ava�a�aJb[b�bHcKc�c�c
d[d�d�de/ePe�e�e�e�efCfFf`f~f�f�f�g�gJh�hi3jok�k�m�m�mnn<n^n�n�ngo�o[p�pqgq�q�q^r�r�r5s�s�st�t�t9v�v1w4w�w�w�w�xy�y�y~z�zY{�{A|�|}�}+~X~�~$Z�	�<�o������9�e���́0�|��P����t�Ԅ"�����Å΅����<�G�]�����Ɇ1�܇H�z�ň�U�ى�?�s����%���Ȍ���K�x�'�ǎ�P�y�����3������M�����5����o��s�hashchkisamchkNIETAKNie można stworzyć pliku '%-.200s' (Kod błędu: %d - %s)Nie można stworzyć tabeli '%-.200s' (Kod błędu: %d - %s)Nie można stworzyć bazy danych '%-.192s' (Kod błędu: %d - %s)Nie można stworzyć bazy danych '%-.192s'; baza danych już istniejeNie można usun?ć bazy danych '%-.192s'; baza danych nie istniejeBł?d podczas usuwania bazy danych (nie można usun?ć '%-.192s', bł?d %d - %s)Bł?d podczas usuwania bazy danych (nie można wykonać rmdir '%-.192s', bł?d %d - %s)Bł?d podczas usuwania '%-.192s' (Kod błędu: %d - %s)Nie można odczytać rekordu z tabeli systemowejNie można otrzymać statusu '%-.200s' (Kod błędu: %d - %s)Nie można rozpoznać aktualnego katalogu (Kod błędu: %d - %s)Nie można zablokować pliku (Kod błędu: %d - %s)Nie można otworzyć pliku: '%-.200s' (Kod błędu: %d - %s)Nie można znaleĽć pliku: '%-.200s' (Kod błędu: %d - %s)Nie można odczytać katalogu '%-.192s' (Kod błędu: %d - %s)Nie można zmienić katalogu na '%-.192s' (Kod błędu: %d - %s)Rekord został zmieniony od ostaniego odczytania z tabeli '%-.192s'Dysk pełny (%s). Oczekiwanie na zwolnienie miejsca... (Kod błędu: %d - %s)Nie można zapisać, powtórzone klucze w tabeli '%-.192s'Bł?d podczas zamykania '%-.192s' (Kod błędu: %d - %s)Bł?d podczas odczytu pliku '%-.200s' (Kod błędu: %d - %s)Bł?d podczas zmieniania nazwy '%-.210s' na '%-.210s' (Kod błędu: %d - %s)Bł?d podczas zapisywania pliku '%-.200s' (Kod błędu: %d - %s)'%-.192s' jest zablokowany na wypadek zmianSortowanie przerwaneWidok '%-.192s' nie istnieje dla '%-.192s'Otrzymano bł?d %d - '%-.192s' z obsługi tabeliObsługa tabeli '%-.192s' nie posiada tej opcjiNie można znaleĽć rekordu w '%-.192s'Niewła?ciwa informacja w pliku: '%-.200s'Niewła?ciwy plik kluczy dla tabeli: '%-.200s'; spróbuj go naprawićPlik kluczy dla tabeli '%-.192s' jest starego typu; napraw go!'%-.192s' jest tylko do odczytuZbyt mało pamięci. Uruchom ponownie demona i spróbuj ponownie (potrzeba %d bajtów)Zbyt mało pamięci dla sortowania. Zwiększ wielko?ć bufora demona dla sortowaniaNieoczekiwany 'eof' napotkany podczas czytania z pliku '%-.192s' (Kod błędu: %d - %s)Zbyt wiele poł?czeńZbyt mało miejsca/pamięci dla w?tkuNie można otrzymać nazwy hosta dla twojego adresuZły uchwyt(handshake)Access denied for user '%-.48s'@'%-.64s' to database '%-.192s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Nie wybrano żadnej bazy danychNieznana komendaKolumna '%-.192s' nie może być nullNieznana baza danych '%-.192s'Tabela '%-.192s' już istniejeNieznana tabela '%-.129s'Kolumna: '%-.192s' w  %-.192s jest dwuznacznaTrwa kończenie działania serweraNieznana kolumna '%-.192s' w  %-.192sUżyto '%-.192s' bez umieszczenia w group byNie można grupować po '%-.192s'Zapytanie ma funkcje sumuj?ce i kolumny w tym samym zapytaniuLiczba kolumn nie odpowiada liczbie warto?ciNazwa identyfikatora '%-.100s' jest zbyt długaPowtórzona nazwa kolumny '%-.192s'Powtórzony nazwa klucza '%-.192s'Powtórzone wystąpienie '%-.192s' dla klucza %dBłędna specyfikacja kolumny dla kolumny '%-.192s'%s obok '%-.80s' w linii %dZapytanie było pusteTabela/alias nie s? unikalne: '%-.192s'Niewła?ciwa warto?ć domy?lna dla '%-.192s'Zdefiniowano wiele kluczy podstawowychOkre?lono zbyt wiele kluczy. Dostępnych jest maksymalnie %d kluczyOkre?lono zbyt wiele czę?ci klucza. Dostępnych jest maksymalnie %d czę?ciZdefinowany klucz jest zbyt długi. Maksymaln? długo?ci? klucza jest %dKolumna '%-.192s' zdefiniowana w kluczu nie istnieje w tabeliKolumna typu Blob '%-.192s' nie może być użyta w specyfikacji kluczaZbyt duża długo?ć kolumny '%-.192s' (maks. = %lu). W zamian użyj typu BLOBW tabeli może być tylko jedno pole auto i musi ono być zdefiniowane jako klucz%s: gotowe do poł?czenia
Version: '%s'  socket: '%s'  port: %d%s: Standardowe zakończenie działania
%s: Otrzymano sygnał %d. Kończenie działania!
%s: Zakończenie działania wykonane
%s: Wymuszenie zamknięcia w?tku %ld  użytkownik: '%-.48s'
Nie można stworzyć socket'u IPTabela '%-.192s' nie ma indeksu takiego jak w CREATE INDEX. Stwórz tabelęNie oczekiwano separatora. SprawdĽ podręcznikNie można użyć stałej długo?ci wiersza z polami typu BLOB. Użyj 'fields terminated by'.Plik '%-.128s' musi znajdować sie w katalogu bazy danych lub mieć prawa czytania przez wszystkichPlik '%-.200s' już istniejeRecordów: %ld  Usuniętych: %ld  Pominiętych: %ld  Ostrzeżeń: %ldRekordów: %ld  Duplikatów: %ldBłędna podczę?ć klucza. Użyta czę?ć klucza nie jest łańcuchem lub użyta długo?ć  jest większa niż czę?ć kluczaNie można usun?ć wszystkich pól wykorzystuj?c ALTER TABLE. W zamian użyj DROP TABLENie można wykonać operacji DROP '%-.192s'. SprawdĽ, czy to pole/klucz istniejeRekordów: %ld  Duplikatów: %ld  Ostrzeżeń: %ldYou can't specify target table '%-.192s' for update in FROM clauseNieznany identyfikator w?tku: %luNie jeste? wła?cicielem w?tku %luNie ma żadej użytej tabeliZbyt wiele łańcuchów dla kolumny %-.192s i polecenia SETNie można stworzyć unikalnej nazwy pliku z logiem %-.200s.(1-999)
Tabela '%-.192s' została zablokowana przez READ i nie może zostać zaktualizowanaTabela '%-.192s' nie została zablokowana poleceniem LOCK TABLESPole typu blob '%-.192s' nie może mieć domy?lnej warto?ciNiedozwolona nazwa bazy danych '%-.100s'Niedozwolona nazwa tabeli '%-.100s'...Operacja SELECT będzie dotyczyła zbyt wielu rekordów i prawdopodobnie zajmie bardzo dużo czasu. SprawdĽ warunek WHERE i użyj SQL_OPTION BIG_SELECTS=1 je?li operacja SELECT jest poprawnaUnknown errorUnkown procedure %-.192sIncorrect parameter count to procedure %-.192sIncorrect parameters to procedure %-.192sUnknown table '%-.192s' in %-.32sField '%-.192s' specified twiceInvalid use of group functionTable '%-.192s' uses a extension that doesn't exist in this MySQL versionA table must have at least 1 columnThe table '%-.192s' is fullUnknown character set: '%-.64s'Too many tables; MySQL can only use %d tables in a joinToo many columnsRow size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBsThread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if neededCross dependency found in OUTER JOIN; examine your ON conditionsTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerCan't load function '%-.192s'Can't initialize function '%-.192s'; %-.192sNo paths allowed for shared libraryFunction '%-.192s' already existsCan't open shared library '%-.192s' (errno: %d %-.128s)Can't find symbol '%-.128s' in libraryFunction '%-.192s' is not definedHost '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.255s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192sInvalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used.The host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionSomething is wrong in your syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionPowtórzone wystąpienie '%-.64s' dla klucza '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAccess denied for user '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setPartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionPowtórzone wystąpienie dla klucza '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Odmowa dostępu dla użytkownika '%-.48s'@'%-.64s'. Konto zablokowane.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesNie można znaleźć rodzaju zasobu w podanym URN: '%.192s'.Nie można znaleźć implementacji usługi ładującej rodzaj zasobu dla zasobu '%.192s' w podanym URN: '%.192s'.Nie można wczytać komponentu pod podanym URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenNie można pozyskać podanej implementacji usługi: '%.192s'.Nie można spełnić zależności w postaci usługi '%.192s' wymaganej przez komponent '%.192s'.Nie można wpisać implementacji usługi '%.192s' dostarczanej przez komponent '%.192s'.Metoda inicjalizująca dostarczona przez komponent '%.192s' nie zakończyła się z powodzeniem.Komponent podany do odłączenia przez URN '%.192s' nie był wcześniej załadowany.Metoda de-inicjalizująca dostarczona przez komponent '%.192s' nie zakończyła się z powodzeniem.Zwolnienie wcześniej pozyskanej implementacji usługi nie powiodło się.Wyrejstrowanie implementacji usługi '%.192s' dostarczonej przez komponent '%.192s' wykonywane podczas odłączania komponentu nie zakończyła się z powodzeniem.Nie można odłączyć komponentu pod podanym URN: '%.192s'.Persistent Dynamic Loader został użyty do odłączenia komponentu '%.192s', który nie był przez niego wcześniej wczytany.Tabela mysql.component nie istnieje lub ma nieodpowiednią definicję.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.Komponent z podanym URN: '%.192s' został podany w grupie więcej niż raz.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\���6��portuguese/errmsg.sysnu�[�����۟�P��^�>o��F���9���Z���7r��
Ox�5���	�	�	
_
�
�
�
�
Im���Jw���"
E
c
�
�
�
e��H�Wn���\�l�����?n���A��Ep�1Cf��+\���!m|���!?���U���� 5 Q p !o!�! ""�"�"R#�#�#�#$k$�$�$%(%\%�%�%&d&�&�&'g'�'�'%(i(�(W)�)�)�)t*�*�*�*$+N+z+�+�+#,b,�,�,�,	-+--�-.Q.�./�/E0�01x1�1$2Z2�2�2Y3�34:4v4�4K5�5�5/6{6�6�6�67G7�7�78M8�8�879d9�9�9:6:d:�:�:#;^;�;�;�;4<f<�<�<�<=7=x=�=%>\>v>�>?J?�?�?@F@�@�@�@#AVA�A�A#BtB�BC/C�CwD�DE�E;F_F�F�FG4G�G�GH5H�H�H/IWI�I	JNJmJ�J�J�JKZK�K�K�K�K�KL/LCL^L�L�L�L
MoM�MNDN\N{N�N�N�N�NOO6OZO�O�O�O�O�OPPMP�P�P�P
Q7QnQ�Q�Q2RiR�R�R�RS0SdS�S2TzT�T8UjU�U�U�U�UVDVRV�V�V�VWdW�W�W�WX4XFXcX�X�X�X�XBYTY�Y�Y�Y"ZEZ[Z�Z�Z�Z[_[�[�[�[�[W\�\�\!]y]�]�]
^^b^�^�^_;_h_�_�_<`�`�aRb�b�b>c�c�cdDd�d�dete�e9f�f�f�fbg�g�g�gh.h�h
i�i�ij�j�j%kak�k�k1l�l�lBm�m�m+n[n�n�no@omo�o�o�o�o$p^p�p�p�pcq�qrLr�r�r$sYs�s�s"t�t�t�t'u�u�u�u.vfv�v�v w`w�w�w$xVx�x�x2yvy�y�yzgz�z{J{o{�{�{�{&|n|�|"}\}�}�}�}~/~C~U~�~�~0Dw�2�Q�����ƀ؀�+�h�������8�d�����ǂ�\�����.����k����"�I�Z�������^�z�����6�W����� �R��� �c���݊�N���������Q�a�|�����ɍ�!�W���Ǝ�C�z�����e�����ߐ�h���đ��
�0�c����6���ߓ�F���Ô0�9�?�I�V�`�h���ƕ�	�3�\�����Ӗ�9�_�x�֗'�P�����Ϙ��>���ә���>����@���H�ŞJ�����R���?�P����"�L������@���ޤ�L�����ߥ*���զ�9�p����2�z���P��u��:�u����!�7�S�&�
�ۮ����<������h���δ1�i����P���¶��+�M�{��b�����N���6�u���Ӻ�0�p�û��~�;�>�v���ݽ��z��I���������������;���4����E�����K����������
���m���������=�|���6�M�d������F�v�������<�`�}�������@����>������x�����"�����Y����i����������R�����%������8�x�������S������)�Q�+�T����h����P����� �j���%�q�������&������\����������B����������)�g����T����e�����$�N������2�Q�����j������_���-�p����=������*�q���
�a�������7�c��������%�P�|��P��"�Z����������Y�m����5�b����(m�%y������>����1	�	Y
�
P��
f��
i
�
�
9y�M����B\~��
:g�/\��rNl� f��.p�$?�U�� c��I�Im���\s���b�cf � � � $!z!�!�!�!R"t"�"c#�#'$y$�$%�%)&�&%'D'�'�'(W(m(�(�(�(�)�)K*w*�*+A+W+n+�+�+,,(,>,c,�,�,�,�-(.W.�./�/.0t0�01�1f2�23Y3�3�34A4k4�4�4�45I5j5�5676t6�6*7\7�7j8�8�8�89!9P9�9�9:C:n:�:�:H;�;�;<M<�<�<x=�=>l>�>�>�>*?e?�?�?�?*@@@M@S@�@�@
A]A�AB8B�B�B(CTC�C�COD�D�DeE�E�F*GbG�G�G�GGH�H�H�HFI�I)J�J�J�JIK�K�K(LbL�L�LdM�M�MNQN{N�N$O�O�O�OP_P�P�PQ:Q�Q�Q$RMR�R�R�R/S}S�STlTUNU�U�U�U9VuV�V7WeW�WEXcX�XY�Y�Z$[�[�\�\�\]:]L]e]�]�]�]^6^T^n^�^�^
_F_s_�_�_.`e`�`�`^a~a-bgb�b�bKctc�cSd�d?ese�e�ef>frf�f�f*ghg�g�ghih�h�hi�i�ijSj�j�j	k)kOk�k�k5lol�lm\mm�mjn,o|o�op$p6q�q"rVr�r�r\s�st�tu�u�uBv�v�vw4w�w�w�x_yz�zD{�|�|}d}�}0~]~�~8c��<�}�Ȁ.�́�f�����F������z�?�Ņ�v�چd��2���Ȉ��z���ω�@�r�Ŋ;����J����#�E�z������܏Ԑ����ܓ)�d����Y���֕��B�x���%�r�������x���4�q�������x�ț8�z���ݜ(���˝*�l���
�.�P�������r�����l���c�~����E���ɤ$�G�}�Υ��K�������3�s�����k���ը�e���Ω��6���ݪ$����P����>�m���$�_�����T���Я�7�{��y�ȱ*�[����O���ӳ��2������\��%�R�������i�˸%����%�׺E����:�����P���Ľ�B�l�־\�¿
�E���
��y���I�����%�S�*������R���K����u������>���B�q�;�t�������p�*����f����������_���J�y�����1�`���y��K���K���X���b����Y�E�q������n�����g����R����;�������G���J���g���v�����k���E�}�������G���@���4�a�����H���-���$����c������;�r����V���Q����q���i�l����R���%���e��=���A������&�)��0���p�!_��G		-
P
�
�
�
�)Mx�
)
R
t
�
o���t�h�t�k��1����D�A�>]���%7���J��4N�&N��2Y���Eo���E�\ � � � !4!b!�!�!�!"9"="s"�"�"%#`#�#�#I$�$�$�$6%^%�%�%�%:&V&�&�&�&';''�')(h(�(A)�)�*�*�*#+�+�+",h,�,X-�-.?.q.�.�.�./A/�/'0�0&1�1�1n2�2�23M3�3�3+4P4�4�4)5_5�5�56!6O6X6c6�6�6%7y7�7�7888)8p8�8�8�8909U9x9�9�9-:c:�:�:;`;�;�;�;�;]<�<�<�</=�=�=?V?�?"@j@DA�AYBB�B�B�B"CJCfC�C�CDEWEyE�EF7F�F�F�F1G`G�G�GNHOI�I�I�ITJ�J�J�J)KVK�KL<L�L�LMUM~M�M�M
N/NZN{N�NO O_O�O�O	P6PkP�P�PQQ!Q1QOQ�QSSVS�SxTLU�U�U�UVGVyV�V�V�V.WPWqW�W�W�W-X@XWXrX�X�X!YXY�Y�YZ Z;ZkZ�Z�Z�Z[8[e[�[�[�[\>\g\�\�\]3]T]h]�]�]^E^�^�^_R_|_�_�_` `G`m`�`�`�`
a[a�a�aEb�b�bCc|c�c:d�d:ete�evf�f$g�g�i�ij�j3kik�k�k
lQl�l�l.mUm�mn$n�nEo�op4p�p�pdq�q�q�q1rHrpr�r�rs3sbs�s�s>t�t�t�tu}u�uJv�vwhw�w�w�wxKx�x�x(ypy�yIztz�z#{O{�{�{/|o|�|�|
}�}�~pT�������+�B��������7�j�ނ���	���ф�/�p�������3��������ڈ�����?�q���'�]���ً�q���F�t����H���Ԏ%�y���Ώ�ېN�����Ñ�B�����Z�y���!�G�Z���Ӕ�5�_�~��(�W���ݖ0�v����7���f���Y��������!�]�z�����K�g���ܜ�s����5�]�������Q������9�T������k�&�D�d���Ԣ4�~�Ƥ�c����
�e��������Q�w���©���n��������ĭ���>���Ͱ1�h�����ܱ��Ͳ
�I�w�"�8�������P�o�ݵL�6�h���A�߸,���ܹl��A�Y�u�û����½��-��׾���1�s����)���������+�]��������E�j���,�[������L����f������D�o�����S�|�����C����I������N�}�����	�{�����]���=������������9�m��������_���1������l������3�_�����*�_�v�������;�c��������5�i�����2�]����������0�[�������"�M�t��������8�U���������������*�}�������"�R�����.�M�j��������A�h�������&�=�T��������5�b��������;�w�����4�t�����8�Z�������@��������P�����g�����-�W�p���������v����2������������F�o����w��������r�����*�]��\���A������,�s����$�[������D�������H�����\����<�[������A����U�v��7��\�d�o�������\�{�u��O�� 9r�k����,T� @a	�	�	�	"
�
(��&Te���
�
�����R����8v�Xe�����
��R���8o����$�(Y��37j��r�T��$n��6z�� g � � (!n!�!�!;"h"�"�"�"E#�#�#D$�$�$�$�$,%m%�%�%�%&i&�&�&G'q'�'�'(<(d(�()8)[)�)�)�)**y*�*�*�*+[+�+b,�,A-�-).H.^.~.�.U/�/-0p0�01N1v1�1242�23�3H4�455\5z5�5�5�5�5�5�5�5�56 636�6�677A7b7�7�7�7�7L8�89�9�9:*:H:�:�:;5;j;�;<]<�<�<=L=�=>�>?@>@s@�@�A�A�A.BRB�B�B�B�BCPC�C�C�C�CDED`D�D�D�D�D�D�D EWE�E�E�E�E%FNF�F�F�F�FGXG�G�G�GH%HJHqH�H�HIkI�I�IJGJ�J�JK1KKKnK�K�KL8LuL�L�LM1M]MwM�M�M-N�N�N�N�N OoO�O�OP(PUP}P�P�PQ Q8QSQVQ�QZR+S�S�S�ST_T�T�T�TUHU�U�U�UVYV�V�V�VW+WKWkW�W�W�W	X8XVXqX�X�XY6Y~Y�Y�Y�Y�Y�Y�Y*ZmZ�Z�Z�Z`[�[\R\v\�\�\�\�\�\�\r]�]�]^Q^j_	`F`�`�a�b�b:cXc�c�c
d.d=dmd�d�d�d*e[e�e�e�efSf�f�f�f�f geg�g�gLh}h�h�h�h�h�hiFiei�i�ij,jnj�j�jkPkvk�k�klPlql�l�l�lm6m^m�m�mnEnln�n�n�n�no.oHomo�o�opBp`p�p�p�p	q5qoq�qrr;r�r�stZtt�t�t�t+uu�uvOv�v�vw
wNwnw�w�w�w�x�y�y�yzhz�z�z{5{T{t{�{�{�{|$|@|^|�|�|}}?}[}�}�}~B~�~�~7�=�������I�݂u�Ã(����������(�I�������$�r������H�U�ԉ�I������B�s����a���
�u��Y�����T���׏8�������ݑF���5���ޓ��Ք#�i��,�T��x������$�K���Ԙ�E���ř�*�h��3�e�����
���8�[�����&�Q����$�U���ԡ��L������f�٤M�ͥ�N���#�§���@�֩�Z�� �V���Ŭ���%���5����j���˰�(���ܱA����6����8����g�ŵ7�}�F�����η��E�f���ظN�Ĺ�R���ĺ�g�����P����W����������}�����M����b���?������`���1���#�a�����M�����1�o���&�����f����]�����D�����k���z���%�x���+�U��������c�����
����(�U���I������;�u������E������4�f���%�`����L������������,�����������V���/���9����B�w���*�t����O����`����j����M��`������7�a�����$����R�����_���+�^������M�����1�����H�������&�k��������$�K�h�������M�{������X�p�������5�f�����t�����P�����W������*�h����
�-�Z������D�G�y�����+U}��I��C��5o���C����=@CFILORUX[^adgjmpsvy|��������������������������������KNQTWZ]`cfilorux{~������������������������������										 	#	&	)	,	/	2	5	8	;	>	A	D	G	J	M	P	S	V	Y	\	_	b	e	h	k	n	q	t	w	z	}	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	�	D
G
J
M
P
S
V
Y
\
_
b
e
h
k
n
q
t
w
z
}
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�
�

"%(+.147:=@CFILOR��Kv�������Ai�r��P�D��[���*\��"%(\_behknqtwz}����������������������������twz}��������������������������������P������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|�����������������!$'*-0369<?BEHKNQTWZ]`cfilorux{~��������������������������������TWZ������������ #&��Y� S � � .!o!�!�!�!""m"p"�"�"�"�"/#n#�#7$d$�$�$�$8%n%�%>&�&�&�'�'h(&))),)s)�)+*Y*\*_*v*y*|**�*�*�*5+�+�+;,e,�,-5-l-�-�-�-).�.�.�.,/0z0�0Q1�1�1�1�1�1�1�1�1�1�12222222222 2#2&2)2,2/2225282;2>2A2D2G2J2M2P2S2V2Y2\2_2b2e2h2k2n2q2t2w2z2}2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2333
3
333333;3>3A3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�34444444444 4#4&4)4,4/4245484;4>4A4D4G4J4M4P4S4V4Y4\4_4b4e4h4k4n4q4t4w4z4}4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4555
5
5555555"5%5(5+5.5154575:5=5@5C5F5I5L5O5R5U5X5[5^5a5d5g5j5m5p5s5v5y5|55�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5~6�67p7�7808}8�8�89L9�9�9�9�9
:<:�:�:;;A;b;�;�;�;<3<^<�<�<=+=�=�=�=�=>2>�>�>?X?w?�?@]@�@9A~A�A�A�AB,BtB�B,C[C�C�C�CeD�D�D�D�D�D�D�D�D�D�DEE�E�E�EyF|F�F�F�F?GjG�GH�I>J[J�J�J�K�L8MSM�M�M�M�M
N0O�O�P�P	Q/QpQ�Q�Q�Q�Q�Q�Q�Q�Q�Q�Q�QRFRIRgRjR�R�R�R�R�R�R�RSSS
S
SSSSSSS"SRSUSXS[S^SaSdSgSjSmSpSsSvSyS|SS�S�S�S�S�STT(TKTNTUUUU"U%U(U+U.U1U4U7U:U=U@UCUFUIU�U�UqV�VWWWWGWqW�W�W�WX#XhX�X�X	Y�Y�Y�Y�Y�Y�Y�Y�Y�Y�Y�Y�Y5Z8ZD[G[J[y[\�\�]�]�^v_�_�`0aEama�b
c�c�c�cd�d"eme�e�e�e�e	f$f@f�f�fg:gHgigh�h�h�hi;idi�i�i�i2jZj�j>k�k�k�kAl�l�lKm�m�m�m�mn0nMnqn�n�n�n�opvp�p�p�pq@q�q�qr\r�r�r?s�s�s>tct�t�t�t�t	uRu�u�u�u�uvvKvv�v�v�v�v�v�v�v�vwNw�w�w x�xy�y�yzWz�z�z�za{�{�{r|�|[}�}~H~�~�~(�_���ǀ�.�����"�J�k����T����
���/����Q�ćه��C���Ȉ��7�:������2�T�o���Z����������P������L����������!�Z�����U�����4�p��]����f�ד�E�|�Ĕ0�������g�ח8���ؘ�g�Ǚ
�4���ݚ����ڛ&�p����&�����#�[���
�A�k���ǟ֟:�f�۠���(�h�����F�g���Ԣ���'�O�����N�ޤ
�]��$�������
����N��������E�����߬���r�����ҭ���ծ��.�n����-�r����/���U�~�ղ
�)�f���ų�V�����i�õ�]���ѶA�����=�o���ƹ�h�����=�\�|�����N����<���ý��<�������;�R�����
������;����O�������C���o�����s�����W�������b���������%�H���0�t���������_�$�[����b���4�y��|���T���P�����U���	�R�����*�H������,�b���[��������&�b���Q�}������������������ �#�&�)�,�/�2�5�8�;�>�A�D�������=�@�C�F�I�L������6�X�[�~������I�q���D�G��v�����\���}���|����q���a�*�}���>�����9�����5�����)����������������������������������������������������������������������W������[�������=�����w���#�&�����L�j����:�l���������\�����������]���esvy|�M�}�,	Z	�	�	�	�	%
n
�
G�5��1
w
�
8g��[��f�����[������=e�z��i�o&^� x � �!�!�"#8#;#�#�$�%@&�&O'�'i(�(�()O)�)�)�*�+�,�-�./�/G0�0\1�1�12'2A2t2�2-3`3�3�3�34%4F4�4S6p6�6�6	7D7g7�7�7Q8�89o9�9#:<2<F>�>j?�?
@�@�@�AlB�BC^C�CLD�D�D�E0F�F�F�FG)G�G�G�G�G�G�H�HI"I%I
J�J8KfK�K�K.LvL�LM�MNAN�NOeO�ObPQ�Q�RYS.TzT�TU@U�U�U�UV5VZV�V�V�VW�W?X�X�XYUY{Y�Y�Y�Y.ZtZ�Z�[B\]�_*bSb�b�b�bKc�c�cXd�d�d,e�erfg�gTh�h/i�i�ijj=jkkRkvk�klcl�l�l�l	m<mxm�m�m�m�m�mn7nJn�nPo�opVp�p�q(smsRudutu�u�u�uvGv�v w�wxmx�x yky�yzkz�z�z>{�{�{�|�|�}c~�~�~H��C�ŀF���7����W������n���v�݆�M���(�Q�z�����J����5���	�k�ˋ-���ی<�Z�|�������֍����9�g�������3�~������Ǒ��,���@�ޓR�����ה�1����Ֆ	�2���ӗk��Ι>������Z������K�(�Ğ,�hashchkisamchkNÃOSIMNão pode criar o arquivo '%-.200s' (erro no. %d - %s)Não pode criar a tabela '%-.200s' (erro no. %d - %s)Não pode criar o banco de dados '%-.192s' (erro no. %d - %s)Não pode criar o banco de dados '%-.192s'; este banco de dados já existeNão pode eliminar o banco de dados '%-.192s'; este banco de dados não existeErro ao eliminar banco de dados (não pode eliminar '%-.192s' - erro no. %d - %s)Erro ao eliminar banco de dados (não pode remover diretório '%-.192s' - erro no. %d - %s)Erro na remoção de '%-.192s' (erro no. %d - %s)Não pode ler um registro numa tabela do sistemaNão pode obter o status de '%-.200s' (erro no. %d - %s)Não pode obter o diretório corrente (erro no. %d - %s)Não pode travar o arquivo (erro no. %d - %s)Não pode abrir o arquivo '%-.200s' (erro no. %d - %s)Não pode encontrar o arquivo '%-.200s' (erro no. %d - %s)Não pode ler o diretório de '%-.192s' (erro no. %d - %s)Não pode mudar para o diretório '%-.192s' (erro no. %d - %s)Registro alterado desde a última leitura da tabela '%-.192s'Disco cheio (%s). Aguardando alguém liberar algum espaço... (erro no. %d - %s)Não pode gravar. Chave duplicada na tabela '%-.192s'Erro ao fechar '%-.192s' (erro no. %d - %s)Erro ao ler arquivo '%-.200s' (erro no. %d - %s)Erro ao renomear '%-.210s' para '%-.210s' (erro no. %d - %s)Erro ao gravar arquivo '%-.200s' (erro no. %d - %s)'%-.192s' está com travamento contra alteraçõesOrdenação abortadaVisão '%-.192s' não existe para '%-.192s'Obteve erro %d - '%-.192s' no manipulador de tabelasManipulador de tabela para '%-.192s' não tem esta opçãoNão pode encontrar registro em '%-.192s'Informação incorreta no arquivo '%-.200s'Arquivo de índice incorreto para tabela '%-.200s'; tente repará-loArquivo de índice desatualizado para tabela '%-.192s'; repare-o!Tabela '%-.192s' é somente para leituraSem memória. Reinicie o programa e tente novamente (necessita de %d bytes)Não há memória suficiente para ordenação. Considere aumentar o tamanho do retentor (buffer) de ordenação.Encontrado fim de arquivo inesperado ao ler arquivo '%-.192s' (erro no. %d - %s)Excesso de conexõesSem memória. Verifique se o mysqld ou algum outro processo está usando toda memória disponível. Se não, você pode ter que usar 'ulimit' para permitir ao mysqld usar mais memória ou você pode adicionar mais área de 'swap'Não pode obter nome do 'host' para seu endereçoNegociação de acesso falhouAcesso negado para o usuário '%-.48s'@'%-.64s' ao banco de dados '%-.192s'Acesso negado para o usuário '%-.48s'@'%-.64s' (senha usada: %s)Nenhum banco de dados foi selecionadoComando desconhecidoColuna '%-.192s' não pode ser vaziaBanco de dados '%-.192s' desconhecidoTabela '%-.192s' já existeTabela '%-.129s' desconhecidaColuna '%-.192s' em '%-.192s' é ambígua'Shutdown' do servidor em andamentoColuna '%-.192s' desconhecida em '%-.192s''%-.192s' não está em 'GROUP BY'Não pode agrupar em '%-.192s'Cláusula contém funções de soma e colunas juntasContagem de colunas não confere com a contagem de valoresNome identificador '%-.100s' é longo demaisNome da coluna '%-.192s' duplicadoNome da chave '%-.192s' duplicadoEntrada '%-.192s' duplicada para a chave %dEspecificador de coluna incorreto para a coluna '%-.192s'%s próximo a '%-.80s' na linha %dConsulta (query) estava vaziaTabela/alias '%-.192s' não únicaValor padrão (default) inválido para '%-.192s'Definida mais de uma chave primáriaEspecificadas chaves demais. O máximo permitido são %d chavesEspecificadas partes de chave demais. O máximo permitido são %d partesChave especificada longa demais. O comprimento de chave máximo permitido é %dColuna chave '%-.192s' não existe na tabelaColuna BLOB '%-.192s' não pode ser utilizada na especificação de chave para o tipo de tabela usadoComprimento da coluna '%-.192s' grande demais (max = %lu); use BLOB em seu lugarDefinição incorreta de tabela. Somente é permitido um único campo auto-incrementado e ele tem que ser definido como chave%s: Pronto para conexões
Version: '%s'  socket: '%s'  port: %d%s: 'Shutdown' normal
%s: Obteve sinal %d. Abortando!
%s: 'Shutdown' completo
%s: Forçando finalização da 'thread' %ld - usuário '%-.48s'
Não pode criar o soquete IPTabela '%-.192s' não possui um índice como o usado em CREATE INDEX. Recrie a tabelaArgumento separador de campos não é o esperado. Cheque o manualVocê não pode usar comprimento de linha fixo com BLOBs. Por favor, use campos com comprimento limitado.Arquivo '%-.128s' tem que estar no diretório do banco de dados ou ter leitura possível para todosArquivo '%-.200s' já existeRegistros: %ld - Deletados: %ld - Ignorados: %ld - Avisos: %ldRegistros: %ld - Duplicados: %ldSub parte da chave incorreta. A parte da chave usada não é uma 'string' ou o comprimento usado é maior que parte da chave ou o manipulador de tabelas não suporta sub chaves únicasVocê não pode deletar todas as colunas com ALTER TABLE; use DROP TABLE em seu lugarNão se pode fazer DROP '%-.192s'. Confira se esta coluna/chave existeRegistros: %ld - Duplicados: %ld - Avisos: %ldYou can't specify target table '%-.192s' for update in FROM clause'Id' de 'thread' %lu desconhecidoVocê não é proprietário da 'thread' %luNenhuma tabela usada'Strings' demais para coluna '%-.192s' e SETNão pode gerar um nome de arquivo de 'log' único '%-.200s'.(1-999)
Tabela '%-.192s' foi travada com trava de leitura e não pode ser atualizadaTabela '%-.192s' não foi travada com LOCK TABLESColuna BLOB '%-.192s' não pode ter um valor padrão (default)Nome de banco de dados '%-.100s' incorretoNome de tabela '%-.100s' incorretoO SELECT examinaria registros demais e provavelmente levaria muito tempo. Cheque sua cláusula WHERE e use SET SQL_BIG_SELECTS=1, se o SELECT estiver corretoErro desconhecido'Procedure' '%-.192s' desconhecidaNúmero de parâmetros incorreto para a 'procedure' '%-.192s'Parâmetros incorretos para a 'procedure' '%-.192s'Tabela '%-.192s' desconhecida em '%-.32s'Coluna '%-.192s' especificada duas vezesUso inválido de função de agrupamento (GROUP)Tabela '%-.192s' usa uma extensão que não existe nesta versão do MySQLUma tabela tem que ter pelo menos uma (1) colunaTabela '%-.192s' está cheiaConjunto de caracteres '%-.64s' desconhecidoTabelas demais. O MySQL pode usar somente %d tabelas em uma junção (JOIN)Colunas demaisTamanho de linha grande demais. O máximo tamanho de linha, não contando BLOBs, é %ld. Você tem que mudar alguns campos para BLOBsEstouro da pilha do 'thread'. Usados %ld de uma pilha de %ld. Use 'mysqld --thread_stack=#' para especificar uma pilha maior, se necessárioDependência cruzada encontrada em junção externa (OUTER JOIN); examine as condições utilizadas nas cláusulas 'ON'Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNão pode carregar a função '%-.192s'Não pode inicializar a função '%-.192s' - '%-.192s'Não há caminhos (paths) permitidos para biblioteca compartilhadaFunção '%-.192s' já existeNão pode abrir biblioteca compartilhada '%-.192s' (erro no. %d '%-.128s')Não pode encontrar a função '%-.128s' na bibliotecaFunção '%-.192s' não está definida'Host' '%-.255s' está bloqueado devido a muitos erros de conexão. Desbloqueie com 'mysqladmin flush-hosts''Host' '%-.255s' não tem permissão para se conectar com este servidor MySQLVocê está usando o MySQL como usuário anônimo e usuários anônimos não têm permissão para mudar senhasVocê deve ter privilégios para atualizar tabelas no banco de dados mysql para ser capaz de mudar a senha de outrosNão pode encontrar nenhuma linha que combine na tabela usuário (user table)Linhas que combinaram: %ld - Alteradas: %ld - Avisos: %ldNão pode criar uma nova 'thread' (erro no. %d). Se você não estiver sem memória disponível, você pode consultar o manual sobre um possível 'bug' dependente do sistema operacionalContagem de colunas não confere com a contagem de valores na linha %ldNão pode reabrir a tabela '%-.192sUso inválido do valor NULLObteve erro '%-.64s' em regexpMistura de colunas agrupadas (com MIN(), MAX(), COUNT(), ...) com colunas não agrupadas é ilegal, se não existir uma cláusula de agrupamento (cláusula GROUP BY)Não existe tal permissão (grant) definida para o usuário '%-.48s' no 'host' '%-.255s'Comando '%-.128s' negado para o usuário '%-.48s'@'%-.64s' na tabela '%-.64s'Comando '%-.16s' negado para o usuário '%-.48s'@'%-.64s' na coluna '%-.192s', na tabela '%-.192s'Comando GRANT/REVOKE ilegal. Por favor consulte no manual quais privilégios podem ser usados.Argumento de 'host' ou de usuário para o GRANT é longo demaisTabela '%-.192s.%-.192s' não existeNão existe tal permissão (grant) definido para o usuário '%-.48s' no 'host' '%-.255s', na tabela '%-.192s'Comando usado não é permitido para esta versão do MySQLVocê tem um erro de sintaxe no seu SQLDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useConexão %ld abortou para o banco de dados '%-.192s' - usuário '%-.48s' (%-.64s)Obteve um pacote maior do que a taxa máxima de pacotes definida (max_allowed_packet)Obteve um erro de leitura no 'pipe' da conexãoObteve um erro em fcntl()Obteve pacotes fora de ordemNão conseguiu descomprimir pacote de comunicaçãoObteve um erro na leitura de pacotes de comunicaçãoObteve expiração de tempo (timeout) na leitura de pacotes de comunicaçãoObteve um erro na escrita de pacotes de comunicaçãoObteve expiração de tempo ('timeout') na escrita de pacotes de comunicação'String' resultante é mais longa do que 'max_allowed_packet'Tipo de tabela usado não permite colunas BLOB/TEXTTipo de tabela usado não permite colunas AUTO_INCREMENTINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESNome de coluna '%-.100s' incorretoO manipulador de tabela usado não pode indexar a coluna '%-.192s'Todas as tabelas contidas na tabela fundida (MERGE) não estão definidas identicamenteNão pode gravar, devido à restrição UNIQUE, na tabela '%-.192s'Coluna BLOB '%-.192s' usada na especificação de chave sem o comprimento da chaveTodas as partes de uma chave primária devem ser não-nulas. Se você precisou usar um valor nulo (NULL) em uma chave, use a cláusula UNIQUE em seu lugarO resultado consistiu em mais do que uma linhaEste tipo de tabela requer uma chave primáriaEsta versão do MySQL não foi compilada com suporte a RAIDVocê está usando modo de atualização seguro e tentou atualizar uma tabela sem uma cláusula WHERE que use uma coluna chave. %sChave '%-.192s' não existe na tabela '%-.192s'Não pode abrir a tabelaO manipulador de tabela não suporta %sNão lhe é permitido executar este comando em uma transaçãoObteve erro %d - '%-.192s' durante COMMITObteve erro %d - '%-.192s' durante ROLLBACKObteve erro %d durante FLUSH_LOGSObteve erro %d durante CHECKPOINTConexão %u abortada para banco de dados '%-.192s' - usuário '%-.48s' - 'host' '%-.255s' ('%-.64s')O manipulador de tabela não suporta 'dump' binário de tabelaBinlog fechado. Não pode fazer RESET MASTERFalhou na reconstrução do índice da tabela 'dumped' '%-.192s'Erro no 'master' '%-.64s'Erro de rede lendo do 'master'Erro de rede gravando no 'master'Não pode encontrar um índice para o texto todo que combine com a lista de colunasNão pode executar o comando dado porque você tem tabelas ativas travadas ou uma transação ativaVariável de sistema '%-.64s' desconhecidaTabela '%-.192s' está marcada como danificada e deve ser reparadaTabela '%-.192s' está marcada como danificada e a última reparação (automática?) falhouAviso: Algumas tabelas não-transacionais alteradas não puderam ser reconstituídas (rolled back)Transações multi-declaradas (multi-statement transactions) requeriram mais do que o valor limite (max_binlog_cache_size) de bytes para armazenagem. Aumente o valor desta variável do mysqld e tente novamenteEsta operação não pode ser realizada com um 'slave' em execução. Execute STOP SLAVE primeiroEsta operação requer um 'slave' em execução. Configure  o 'slave' e execute START SLAVEO servidor não está configurado como 'slave'. Acerte o arquivo de configuração ou use CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logNão conseguiu criar 'thread' de 'slave'. Verifique os recursos do sistemaUsuário '%-.64s' já possui mais que o valor máximo de conexões (max_user_connections) ativasVocê pode usar apenas expressões constantes com SETTempo de espera (timeout) de travamento excedido. Tente reiniciar a transação.O número total de travamentos excede o tamanho da tabela de travamentosTravamentos de atualização não podem ser obtidos durante uma transação de tipo READ UNCOMMITTEDDROP DATABASE não permitido enquanto uma 'thread' está mantendo um travamento global de leituraCREATE DATABASE não permitido enquanto uma 'thread' está mantendo um travamento global de leituraArgumentos errados para %sNão é permitido a '%-.48s'@'%-.64s' criar novos usuáriosDefinição incorreta da tabela. Todas as tabelas contidas na junção devem estar no mesmo banco de dados.Encontrado um travamento fatal (deadlock) quando tentava obter uma trava. Tente reiniciar a transação.O tipo de tabela utilizado não suporta índices de texto completo (fulltext indexes)Não pode acrescentar uma restrição de chave estrangeiraNão pode acrescentar uma linha filha: uma restrição de chave estrangeira falhouNão pode apagar uma linha pai: uma restrição de chave estrangeira falhouErro conectando com o master: %-.128sErro rodando consulta no master: %-.128sErro quando executando comando %s: %-.128sUso errado de %s e %sOs comandos SELECT usados têm diferente número de colunasNão posso executar a consulta porque você tem um conflito de travamento de leituraMistura de tabelas transacional e não-transacional está desabilitadaOpção '%s' usada duas vezes no comandoUsuário '%-.64s' tem excedido o '%s' recurso (atual valor: %ld)Acesso negado. Você precisa o privilégio %-.128s para essa operaçãoVariável '%-.64s' é uma SESSION variável e não pode ser usada com SET GLOBALVariável '%-.64s' é uma GLOBAL variável e deve ser configurada com SET GLOBALVariável '%-.64s' não tem um valor padrãoVariável '%-.64s' não pode ser configurada para o valor de '%-.200s'Tipo errado de argumento para variável '%-.64s'Variável '%-.64s' somente pode ser configurada, não lidaErrado uso/colocação de '%s'Esta versão de MySQL não suporta ainda '%s'Obteve fatal erro %d: '%-.512s' do master quando lendo dados do binary logSlave SQL thread ignorado a consulta devido às normas de replicação-*-tabelaVariable '%-.192s' is a %s variableDefinição errada da chave estrangeira para '%-.192s': %sReferência da chave e referência da tabela não coincidemOperand should contain %d column(s)Subconsulta retorna mais que 1 registroDesconhecido manipulador de declaração preparado (%.*s) determinado para %sBanco de dado de ajuda corrupto ou não existenteReferência cíclica em subconsultasConvertendo coluna '%s' de %s para %sReferência '%-.64s' não suportada (%s)Cada tabela derivada deve ter seu próprio aliasSelect %u foi reduzido durante otimizaçãoTabela '%-.192s' de um dos SELECTs não pode ser usada em %-.32sCliente não suporta o protocolo de autenticação exigido pelo servidor; considere a atualização do cliente MySQLTodas as partes de uma SPATIAL index devem ser NOT NULLCOLLATION '%s' não é válida para CHARACTER SET '%s'O slave já está rodandoO slave já está paradoTamanho muito grande dos dados des comprimidos. O máximo tamanho é %d. (provavelmente, o comprimento dos dados descomprimidos está corrupto)ZLIB: Não suficiente memória disponívelZLIB: Não suficiente espaço no buffer emissor (provavelmente, o comprimento dos dados descomprimidos está corrupto)ZLIB: Dados de entrada está corruptoRow %u was cut by GROUP_CONCAT()Conta de registro é menor que a conta de coluna na linha %ldConta de registro é maior que a conta de coluna na linha %ldDado truncado, NULL fornecido para NOT NULL coluna '%s' na linha %ldOut of range value for column '%s' at row %ldDado truncado para coluna '%s' na linha %ldUsando engine de armazenamento %s para tabela '%s'Combinação ilegal de collations (%s,%s) e (%s,%s) para operação '%s'Cannot drop one or more of the requested usersNão pode revocar todos os privilégios, grant para um ou mais dos usuários pedidosIlegal combinação de collations (%s,%s), (%s,%s), (%s,%s) para operação '%s'Ilegal combinação de collations para operação '%s'Variável '%-.64s' não é uma variável componente (Não pode ser usada como XXXX.variável_nome)Collation desconhecida: '%-.64s'SSL parâmetros em CHANGE MASTER são ignorados porque este escravo MySQL foi compilado sem o SSL suporte. Os mesmos podem ser usados mais tarde quando o escravo MySQL com SSL seja iniciado.Servidor está rodando em --secure-auth modo, porêm '%s'@'%s' tem senha no formato antigo; por favor troque a senha para o novo formatoCampo ou referência '%-.192s%s%-.192s%s%-.192s' de SELECT #%d foi resolvido em SELECT #%dParâmetro ou combinação de parâmetros errado para START SLAVE UNTILÉ recomendado para rodar com --skip-replica-start quando fazendo replicação passo-por-passo com START SLAVE UNTIL, de outra forma você não está seguro em caso de inesperada reinicialição do mysqld escravoThread SQL não pode ser inicializado tal que opções UNTIL são ignoradasIncorreto nome de índice '%-.100s'Incorreto nome de catálogo '%-.100s'Falha em Query cache para configurar tamanho %lu, novo tamanho de query cache é %luColuna '%-.192s' não pode ser parte de índice FULLTEXTKey cache desconhecida '%-.100s'MySQL foi inicializado em modo --skip-name-resolve. Você necesita reincializá-lo sem esta opção para este grant funcionarMotor de tabela desconhecido '%s''%s' é desatualizado. Use '%s' em seu lugarA tabela destino %-.100s do %s não é atualizávelO recurso '%s' foi desativado; você necessita MySQL construído com '%s' para ter isto funcionandoO servidor MySQL está rodando com a opção %s razão pela qual não pode executar esse commandoColuna '%-.100s' tem valor duplicado '%-.64s' em %sTruncado errado %-.64s valor: '%-.128s'Incorreta definição de tabela; Pode ter somente uma coluna TIMESTAMP com CURRENT_TIMESTAMP em DEFAULT ou ON UPDATE cláusulaInválida cláusula ON UPDATE para campo '%-.192s'This command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionEntrada '%-.64s' duplicada para a chave '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComentário para a tabela '%-.64s' é longo demais (max = %lu)Comentário para o campo '%-.64s' é longo demais (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAcesso negado para o usuário '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setParticion '%-.64s' n?o existeFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Número de condição inválidoSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionEntrada duplicada para a chave '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�6��E�E�romanian/errmsg.sysnu�[�����1��	K}��<��D}��(_��c��I|���/i��@]�k��	�	
_
�
�
�
0Ml���9p���"
N
}
�
�
�
.]��d�4x���"w�(��"A�T���!8h��Q~�?Nj���?����EX�}�No���,Vv�+�M�P��� � � 8!�!"A"d"�"%#D#�#�#�#4$e$�$�$�$?%�%�%&M&�&�&"'D'�'�'!(�()>)q)�) *O*`*�*�*�*+9+X+�+�+,>,Z,x,�,�,&-G-�-�-
.�.�.3/�/080�0�0�0 1f1�1�12=2�2�2�2!3b3�3�3�3484v4�4�45^5�5�5G6v6�6�67*7Y7�7�78D8r8�8�8�8979\9�9�9�9:~:�:�:�:;�;�;<<?<l<�<=4=^=�=�=�=8>>�>??�?S@�@�@�A�AB0BpB�B�B+CGC�C�CDpD�D�DJExE�E�EF.F`F�F�F�F*G?GTGiG�G�G�G�G�G0HUH|H�HVIvI�I�I�IJ-JNJcJzJ�J�J�J�JK,KDKYKoK�K�KL/LQLyL�L�LMYM�M�M�MNKNpN�N�NSO�O�OkP�P�P�PQ6QeQ�Q�Q�QR2RgR�R�R�R+SPSqS�S�S�S�STFTgT�T�T�T"UMU�U�U�U�U"V<V�V�V�VW4WkW�WX^X�X�XYPYyY�Y�Y
Z=ZsZ�Z�Z:[g[�[i\.]�];^c^�^�^4_u_�_`T`�`�`Ba�a�a.bFb�b�bcQctc�c)dyde_e~efQf�f�fghg�g	hNh�h%iFi�i�ijEj{j�j�jk>kHkRk�k�kl?l[l�lmrm�mn\n�n�noKo�o�o#pep�p�p"qWq�q�qrAr�r�r
sls�s�s4tat�t�tu@u{u�u@v{v�v�vw?w`w�w�wOx�x�xy%yGyoy�y�y�y�yGz�z�z�z {�{�{�{|5|G|r|�|�|�|}l}�}�}�}~6~v~�~
/�.���ڀ,�Z�����Ɂ���d�͂�(�T�q���ƃ
�j��������҅�L�������r���*�Z���Ј���8�a���Ɖ�5�s�����O�w�ԋ��,�N���׌�3�d�|���ҍ�~����N�����������������������>�a�����ߑ
�+�j�����В.�����
�'�Q����+�d����A����������H��D���������?�z�����9����6�q���ߠ�7����-�o���Ȣ��D���أ���P�ӥ?���Ӧ�K��������k�9�������`�p�p�Ư�,���ǰ
�r���� �\�����ٲ_����C�a�������ӵ�1�N���Ͷ �W�۷����Ӹ�3�T�к=���ܻ&�u��0�l�ս"�M�j���
�����d����T�����1��R�r�`�>������W��\������������^���E������4�Y�u���������[�m�����.�����<�e�����-�x���1�����X����������]����E�{��F�o������#�T�����%�^���������V�����m�����<�v���,�{���%�B���|�����^�����>�h�
������[��O����.�o���8�j����7�z�����?�u����������@�[����������!������-�W������c������7�]��������/�T�{����-���'�x�������H��J�����<�����
�/�~��F�{���u�� �\��&���.u�5�=�]��c��Hu��+	�	�	E
�
g�Qu����
c
�
�
�
���Nr�p��Dv�4��z�r��>v��@m��a���Bu���@�$i���Iz��0���P}� ] � !"{"�"6#H#o#�#�#�#	$&$�$2%�%�%,&m&�&�&�&	'3'^'a'~'�'�'�'(8()~)�)"*W*+�+�+,b,-�-
.^.�./6/e/�/�/�/0H0j0�0�0�0p1�1�1
2�2�273�3�3414[4w4�45<5n5�5�5�5N6�6�6%7e7�78T8�89p9�9�9!:S:�:�:�:$;U;�;�;�;�;�;<c<�<=[=�=�=
>~>�>�>:?�?�?:@�@0A�A�B�B�BCNC�C�CDRD�DEE�EF1F�F�F7G~G�GHUH�H�H:IoI�I�INJzJ�JK6KpK�K�K4L\L�L�L)MzM�M�MN=N�N�N"OqO�OlP�P�PQIQ�Q�Q$R�R�RS�S�STfTAU�UzV�V�WXGXgX�X�X�XY2YMYlY�Y�Y�YZ:ZcZ�Z�Z[<[�[�[\N\�\�\�]�]�]^�^�^_�_�_�`�`�`%aWa�a�a#bQb�b�b�b/coc�c�c!dfdeKeYe�e�eCf_ff�fgQg�g�g�gnh�h�hi�i�j�jk\kzk�lmxm�m�m9n�n*olo�oWpqCq�q�q0r^r�r�rLs�s�touBv�v�w)xdx�x�x�y�yzbz�z�z�zJ{�{�{|�|"}t}�}~M~�~�~o����h�́0���C������U�Є�%�]���ȅ����D�����@�y���Ј�X��2�*���2����
�V����,�T���Α��{�Ȓ�g�ۓI�ΔR���Ǖ��
�M�Ζ���З�3�~�ؘ!����c�����ޚ�G�s�țg�؜I����Ԟ�^�����z���Ӡ$�T�����<�?���ɢ�T����+�A����$�K���ߥ3�z��9�����r���èS�z�����N���ת&�p���ѫF�Ϭ������\����)�Q����r����A�{���ڲ�B�F���!�{��V�{�-�����?�����M�����Z���¹,����c�����`�"�Ͻ'����:�{������\�����&�����X�����.�e���
����������#�������P�r����&�?�r������������T��������u���)���)���4���p�
���������-�d�����$���F�b����^�����R��������#������	�O���J������D��������������:���*�����z��Y����'�j�������0���K�����,���K������]����{�
���#�������u�-��|�'���9����"�u�4�w��B������&\�a��g���a	�	�	
U
�
>�r�
b
�
�
D��'�@a�����t��8l{��/[��@��8|��F���!s���Il�G��.\����4b���{��9�� . � � � � :!�!�!�!	";"o"�"�" ##�#�#�$%�%
&1&y&�&@'x'�'S(�(D)i)�)�)�)*=*[*�*(+}+,|,-D-�-.:.k.�.�.	/�/�/�/�/0�0�021Y1w1�1�1�1�12{2�2D3O3Z3g3t33�3�3E4S4t4�4�4�45N5�5�5656[6�6�6787M7�7�78S8�899\:�:M;x;�;�<1=�=�=�=>E>x>�>�>?D?g?g@�@�@9A[A�A�AB8B�B�B�BC�C�D�DEME�E�E5FSFF�F�FhG�G�GHeH�H�HI>I`I�I�I�I%JYJvJ�J K6K_K�K�KL9L[LiLwL�L�L8MYNuN�N�N�O�P�PQAQ[Q�Q�QR'RTR�R�R�R�R1STS�S�S�S�S�S5TwT�TU+UWUvU�U�U�UV<VaV�V�V�VWHWqW�W�W�W$XVX�X�X�XY:YWY�YZCZuZ�Z�Z[2[W[v[�[�[�[\<\`\�\
]K]�]�]S^�^�^_�_`�`�`Na�aBbzbc�d9ete-f�f�f�f1gcg�g�g=h�h�hiVizi�i�jBkik�k�k@l�lm"m;m�m�m�m�mnkn�n�n�nGo�o�op9pbp�pKq�qrnr�r�rsDsjs�s�s.t~t�t
u�u�u<vyv�v�vCw�w�w�w.xcxMyz�z�{�{|I|h|�|�|�|}}H}�}�}4~m~�~_�'�]���ƀ��R���ڂ��>�0�܄�^���ǅ�}�����/�f�Ǉ8�j���ʈ�W����*�{�ϊ�$�:�1���݌��b����E�d���ώ��w������)�a�����Ԑ8�~����3���̒�9������D�n�����A�T�w���Ж�D�l������2�p�ɘ��E�������6�b����R�j�����՛��C�^���|������*���ԟ�n����:�`���8�֢�t�q���ͤ���e�ޥĦA�q��m���S�Z�����#�������2��#�`���ͮx�����<�k���Ű3�������޲��5����2�µ>�����˶�=�A���Q���չ-���?���ɻ���ݼ��3�Y�������A�l����������ٿ�a�����V�����&�j������J������1����r�����:�k������4�_����T���7�����!�0�3�6�q��������A�f�������8�m������g�������"���������@���������9�W�������+���������"�C�f��������M�x������h���(��������6�Z����=�W������$�K�x���%�K����������.�a�������
�E�|���������'�X��������F�h������F�������C�����������������]�����:���8�M����������2�Z�m���+�[�����6�]���
�O�������e���3���1�W�����J�����r���7�����8�g������M�z������a������K�����#�l�����X������)�K����@����k���X���������@�f����\����9����7�v�����m���t�HO�@��v���?x�~N|���	B	�	C
�
U��+Z�7
e
�
�
	q��8�-`1f��3^���(Oz2~�N����#X�M��8z�?h��4k��L~�A���G��<�� ' N � � � !6!l!�!"E"�"�"#I#n#�#�#%$n$�$�$�$%5%�%�%&#&U&[&�&�&�'(�())�)�)�)/*�*(+�+�+!,Y,�,�,�,r-�-�-l.�.�/*0�0�0�01111111=1s1v1�1�1.2j2m2�2�2�2
3 3@3�3/4u4�435f5�5�5�576b6�6�67^7�7�7D8m8�8�8s9�9�:W;�;�;�;�<'=R=�=�=�=�=>J>e>�>�>?'?I?s?�?�?�?�?@!@4@B@v@�@�@A5ALA{A�A�AB6BGBtB�B�BC9CYC{C�C�C�CDuD�D�DEoE�E�E
FVF�F�F�FG5GpG�G�G
H:H\H�H�H�H7IGI�I�I�IJMJvJ�J�J5KXK~K�K�KL=L\LvL�L�L�LQM�M�N�NO,OrO�O�OP?PpP�P�P�P%QlQ�Q�QR?RfR�R�R�R�RS'S_S�S�S�ST8ThT�T�T�T�TU!U+UUU�U�U�UOVRV�V5WoW�W�W�W�W�W�WXNX�X�X%YdY�Y�Z_[�[I\]^I^�^�^�^_c_�_�_�_�_`N`�`�`�`a8apa�a�ab0bGbvb�b�bDc�c�c�cd*dAdDdfd�d�d�deZe�e�e�e6fsf�f�f�f=geg�g�g�g�gEhhh�h�h�hIiui�i�i�ijj/jZj�j�j�j�jkWk�k�k�kl;l_l�l�l�lVmgm�mnobo�o�op8pOp�p�pqrq�q�q�q]r`r�r�r�rsOs�s�t6uGuqu�u�u8v]v�v�v�v�vwEwawzw�w�w�w7xWxqx�x�x�x�xfy�y�y%z�z{�{�{|�|G}�}3~�~~��I�t�n��~���݂�P�z�ȃ߃�e�����*�h���م�J���Ɇ�Z����c�ˈ@�����P�����-����P�׌3�������4�ߏ+�y���a�����J�Β��@�z����*�Z���ޔ�B�����9��������c���������|����>�z����*�T���ޝ7�՞i���/���#�u����y��t����,�a���8�v�����m���{�
����B�����!�Z�~�٬2����G�����g�����l������ӱ����$�E�e������.����\�����l���������[����o��N��Ӽ�<�n����t���#����7�p������'�y�����T�����4�����
�|���6����d����H�����A������"�{�����������p�����?�c��V�~���*�����%�]�������)�e�����
�X�����@�{�����Z������0�g��M�����j�����!�r������#�����Z�����+�����"�\����q�����[���g�(���d�����8�l������M�z���2��������>�������5�g���+�.�����?������L�|������)�C�]�z��������,�[������*�S�������S�������-�^���Z�t����&�m�����B�s�������,�`������
�l�������)�G������������ ���"�S�����9m��8[C������������������������������������� #&),/25�����������������������������"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?B����������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~���������������#W���+.147:t	�	�	
p
s
�
R��
3
r
�
�
F���rux{~��������������������������	!$'��������������"%(+.147:=@CFILORU���

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~�������������������������������������������behknqtwz}�������������������������������������������

"%(+.14���47:=@CFILORUX[^adgjmpsvy|��o��
���#Cx���� J������ J � � � �!�!"#4#�#|$$�$�$%�%�%�%�%�%�%�%�%�%�%�%�&�&5'�'�'�'[(�(�(�(�(<))�)*<*�*W+�+
,�,�,
-@-C-F-I-L-O-R-U-X-[-^-a-d-g-j-m-p-s-v-y-|--�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-...	........!.$.'.*.-.0.3.6.9.<.?.B.E.H.K.N.Q.T.W.Z.].`.c.f.i.l.o.r.�.�.�.�.�.///
/
///////"/%/(/+/./1/4/7/:/=/@/C/F/I/L/O/R/U/X/[/^/a/d/g/j/m/p/s/v/y/|//�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/000	00000000!0$0'0*0-000306090<0?0B0E0H0K0N0Q0T0W0Z0]0`0c0f0i0l0o0r0u0x0{0~0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�01111111111 1#1&1)1,1/1215181;1>1A1D1G1J1M1P1�1?2g2�23V3�3�34A4r4�4�45!525c5�5�56W6r6�6�6�6777X7�7�7�78V8�8�8�8979a9�9�9K:r:�:�:9;o;�;<�<�<�<=B=b=�=�=>�>�>�>�>?�?�?=@@@C@F@I@L@O@R@U@X@[@A%A(A�A�A�A"BCB�B�B�B]CE�E�E�ELFGH�H�H�H�HII`I�J�JLAL_L�L�L�LMMMMMM M#M&M)MrM�M�M�M�M�M�M!N$NNNQNTNWNZN]N`NcNfNiNlNoNrNuNxN�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�NaOdO~O�O�OlPoPrPuPxP{P~P�P�P�P�P�P�P�P�P�P�P�PQQ�QURXR[R^RaR�R�R�RSLSaSyS�S�S%T_T�T�TUUU
U
UUUUU;U�U�U�V�V�V�VmW	X�X*YJZ�ZL[6\�\�\�\�]`^�^_A_j_,`x`�`�`�`aBa_aza�a�a1beb�b�b�bfc�cd7drd�d�d�deOe�e�ef�f�f�f:g�g�g=h�hiii@iei�i�i�ij-jQjk]k�k�klClhl�l�lmnm�m�mn�n�n5o�o�o�o�opp_p�p�p�p q>qaqdq�q�q�q�q�q�q�q�q�q�qir�rs:svs�sjt�tJusu�u�uv9v�vwTw�wTx�x:yWy�y�yEz~z�z�{�{|V|�|�|}x}�}�}�}r~�~Z�`������r����/�K�����B�f������P�i�����Ņ�������J�Z�j���ۇ�]����8�o���?�w����N����K���ƌ>�����e���-�d���ҏ����p�ۑC���-���ۓ.�m����c�����3�Q���0�|�Ɨ�8�|�טD�G�y���
�`��������,�����1�M�i�~����N�������*�@�U�}���՞�]���4�`���:�z��M��c��s����K�٦G������5�Q�g�Ȩ��(�]��+�Q���ĪڪH���ȫ��j�������ԭ+�`����ۮ�g�����;�e����n����'�����p�ճ��Ŵ��q���	�>�n�����Ҷ�U����:�����S���ֹK�<�f�������`�"�%�(�+�]����b���ݾ@�O���6����H���+�C����F�\�s��������+�{���%���������C�����z���G�i��������m���C���!�����R�����_�����6������d�������k�n������F�a�|������������$�'�*�K�g�j�m�p�s�v�y�|�����������������������<���������������3�X������������f�����(�����t�����B���U���N����p��� �������4�����O�����A�����.�������
�
�������"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�����?�r������1�����R����y�|��n�/�������#��������1�X�����l�(��&�I�1��k���$�8�������m���S���� 6{�+q�4��)��G	�	�	K
�
l��	�$
j
5�!��BS�6��3i�/%�H�]|��\�S�Q�h���7 !�!3"�"@#�#$F$o$�$�$%�%�&
(�(�)^*+�+T,�,�,N-i-}-�-�-.�.�.�./7/l/{/�/S0�1�1�12_2�2�2�2R3�34d4�4&5y5]7�7�9N:�:�:`;�;<?=�=>s>�>�>�?�?@�@�A�ABCBaBB�BC"C&C*C�CDuDxD{DcE�E�F�FGQG�G�GHjH�H\I�I�IlJ�JK�KnLM�M�N�O�OPdP�P�PQCQgQ�Q�Q�QRERsRBS�S�S<TeT�T�T�T*UTU�U�U	V�V�WZX[�]�]�]
^?^�^_N_�_�_`�`"a�a^bc�cDd�d�d�dYeje�eWfZf�f�fgjg�g�gh>h_h�h�h�hi*iRiUioi�i�i�i�j�jYk�klBm~n�n�p�p�pq"qKqmq�qrvr�rjs�stvt�tumu�uvDv�v�vw�wxHy�y@zCz�z�z�z�{|�|�|�}~h~�~P��Ā:�g�́3�i����K�~���Ѓ�H�t���ۄ?�����_���!����1�����҈݈��,�K�V�l�����؉@��W���ԋ�d���N������4���׏�-�Z���6�֑+�_����)���B�$�������\����D�����~����hashchkisamchkNUDANu pot sa creez fisierul '%-.200s' (Eroare: %d - %s)Nu pot sa creez tabla '%-.200s' (Eroare: %d - %s)Nu pot sa creez baza de date '%-.192s' (Eroare: %d - %s)Nu pot sa creez baza de date '%-.192s'; baza de date exista dejaNu pot sa drop baza de date '%-.192s'; baza da date este inexistentaEroare dropuind baza de date (nu pot sa sterg '%-.192s', Eroare: %d - %s)Eroare dropuind baza de date (nu pot sa rmdir '%-.192s', Eroare: %d - %s)Eroare incercind sa delete '%-.192s' (Eroare: %d - %s)Nu pot sa citesc cimpurile in tabla de system (system table)Nu pot sa obtin statusul lui '%-.200s' (Eroare: %d - %s)Nu pot sa obtin directorul current (working directory) (Eroare: %d - %s)Nu pot sa lock fisierul (Eroare: %d - %s)Nu pot sa deschid fisierul: '%-.200s' (Eroare: %d - %s)Nu pot sa gasesc fisierul: '%-.200s' (Eroare: %d - %s)Nu pot sa citesc directorul '%-.192s' (Eroare: %d - %s)Nu pot sa schimb directorul '%-.192s' (Eroare: %d - %s)Cimpul a fost schimbat de la ultima citire a tabelei '%-.192s'Hard-disk-ul este plin (%s). Astept sa se elibereze ceva spatiu... (Eroare: %d - %s)Nu pot sa scriu (can't write), cheie duplicata in tabela '%-.192s'Eroare inchizind '%-.192s' (errno: %d - %s)Eroare citind fisierul '%-.200s' (errno: %d - %s)Eroare incercind sa renumesc '%-.210s' in '%-.210s' (errno: %d - %s)Eroare scriind fisierul '%-.200s' (errno: %d - %s)'%-.192s' este blocat pentry schimbari (loccked against change)Sortare intreruptaView '%-.192s' nu exista pentru '%-.192s'Eroarea %d - '%-.192s' obtinuta din handlerul tabeleiHandlerul tabelei pentru '%-.192s' nu are aceasta optiuneNu pot sa gasesc recordul in '%-.192s'Informatie incorecta in fisierul: '%-.200s'Cheia fisierului incorecta pentru tabela: '%-.200s'; incearca s-o repariCheia fisierului e veche pentru tabela '%-.192s'; repar-o!Tabela '%-.192s' e read-onlyOut of memory. Porneste daemon-ul din nou si incearca inca o data (e nevoie de %d bytes)Out of memory pentru sortare. Largeste marimea buffer-ului pentru sortare in daemon (sort buffer size)Sfirsit de fisier neasteptat in citirea fisierului '%-.192s' (errno: %d - %s)Prea multe conectiuniOut of memory;  Verifica daca mysqld sau vreun alt proces foloseste toate memoria disponbila. Altfel, trebuie sa folosesi 'ulimit' ca sa permiti lui memoria disponbila. Altfel, trebuie sa folosesi 'ulimit' ca sa permiti lui mysqld sa foloseasca mai multa memorie ori adauga mai mult spatiu pentru swap (swap space)Nu pot sa obtin hostname-ul adresei taleProst inceput de conectie (bad handshake)Acces interzis pentru utilizatorul: '%-.48s'@'%-.64s' la baza de date '%-.192s'Acces interzis pentru utilizatorul: '%-.48s'@'%-.64s' (Folosind parola: %s)Nici o baza de data nu a fost selectata incaComanda invalidaColoana '%-.192s' nu poate sa fie nullBaza de data invalida '%-.192s'Tabela '%-.192s' exista dejaTabela '%-.129s' este invalidaColoana: '%-.192s' in %-.192s este ambiguaTerminarea serverului este in desfasurareColoana invalida '%-.192s' in '%-.192s''%-.192s' nu exista in clauza GROUP BYNu pot sa grupez pe (group on) '%-.192s'Comanda are functii suma si coloane in aceeasi comandaNumarul de coloane nu este acelasi cu numarul valoareiNumele indentificatorului '%-.100s' este prea lungNumele coloanei '%-.192s' e duplicatNumele cheiei '%-.192s' e duplicatCimpul '%-.192s' e duplicat pentru cheia %dSpecificandul coloanei '%-.192s' este incorect%s linga '%-.80s' pe linia %dQuery-ul a fost golTabela/alias: '%-.192s' nu este unicValoarea de default este invalida pentru '%-.192s'Chei primare definite de mai multe oriPrea multe chei. Numarul de chei maxim este %dPrea multe chei. Numarul de chei maxim este %dCheia specificata este prea lunga. Marimea maxima a unei chei este de %dColoana cheie '%-.192s' nu exista in tabelaColoana de tip BLOB '%-.192s' nu poate fi folosita in specificarea cheii cu tipul de tabla folositLungimea coloanei '%-.192s' este prea lunga (maximum = %lu). Foloseste BLOB mai bineDefinitia tabelei este incorecta; Nu pot fi mai mult de o singura coloana de tip auto si aceasta trebuie definita ca cheie%s: sint gata pentru conectii
Version: '%s'  socket: '%s'  port: %d%s: Terminare normala
%s: Semnal %d obtinut. Aborting!
%s: Terminare completa
%s: Terminare fortata a thread-ului %ld  utilizatorului: '%-.48s'
Nu pot crea IP socketTabela '%-.192s' nu are un index ca acela folosit in CREATE INDEX. Re-creeaza tabelaArgumentul pentru separatorul de cimpuri este diferit de ce ma asteptam. Verifica manualulNu poti folosi lungime de cimp fix pentru BLOB-uri. Foloseste 'fields terminated by'.Fisierul '%-.128s' trebuie sa fie in directorul bazei de data sau trebuie sa poata sa fie citit de catre toata lumea (verifica permisiile)Fisierul '%-.200s' exista dejaRecorduri: %ld  Sterse: %ld  Sarite (skipped): %ld  Atentionari (warnings): %ldRecorduri: %ld  Duplicate: %ldComponentul cheii este incorrect. Componentul folosit al cheii nu este un sir sau lungimea folosita este mai lunga decit lungimea cheiiNu poti sterge toate coloanele cu ALTER TABLE. Foloseste DROP TABLE in schimbNu pot sa DROP '%-.192s'. Verifica daca coloana/cheia existaRecorduri: %ld  Duplicate: %ld  Atentionari (warnings): %ldYou can't specify target table '%-.192s' for update in FROM clauseId-ul: %lu thread-ului este necunoscutNu sinteti proprietarul threadului %luNici o tabela folositaPrea multe siruri pentru coloana %-.192s si SETNu pot sa generez un nume de log unic %-.200s.(1-999)
Tabela '%-.192s' a fost locked cu un READ lock si nu poate fi actualizataTabela '%-.192s' nu a fost locked cu LOCK TABLESColoana BLOB '%-.192s' nu poate avea o valoare defaultNumele bazei de date este incorect '%-.100s'Numele tabelei este incorect '%-.100s'SELECT-ul ar examina prea multe cimpuri si probabil ar lua prea mult timp; verifica clauza WHERE si foloseste SET SQL_BIG_SELECTS=1 daca SELECT-ul e okayEroare unknownProcedura unknown '%-.192s'Procedura '%-.192s' are un numar incorect de parametriProcedura '%-.192s' are parametrii incorectiTabla '%-.192s' invalida in %-.32sColoana '%-.192s' specificata de doua oriFolosire incorecta a functiei groupTabela '%-.192s' foloseste o extensire inexistenta in versiunea curenta de MySQLO tabela trebuie sa aiba cel putin o coloanaTabela '%-.192s' e plinaSet de caractere invalid: '%-.64s'Prea multe tabele. MySQL nu poate folosi mai mult de %d tabele intr-un joinPrea multe coloaneMarimea liniei (row) prea mare. Marimea maxima a liniei, excluzind BLOB-urile este de %ld. Trebuie sa schimbati unele cimpuri in BLOB-uriStack-ul thread-ului a fost depasit (prea mic):  Folositi: %ld intr-un stack de %ld.  Folositi 'mysqld --thread_stack=#' ca sa specifici un stack mai mareDependinta incrucisata (cross dependency) gasita in OUTER JOIN.  Examinati conditiile ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNu pot incarca functia '%-.192s'Nu pot initializa functia '%-.192s'; %-.192sNici un paths nu e permis pentru o librarie sharedFunctia '%-.192s' exista dejaNu pot deschide libraria shared '%-.192s' (Eroare: %d %-.128s)Nu pot gasi functia '%-.128s' in librariaFunctia '%-.192s' nu e definitaHost-ul '%-.255s' e blocat din cauza multelor erori de conectie. Poti deploca folosind 'mysqladmin flush-hosts'Host-ul '%-.255s' nu este permis a se conecta la aceste server MySQLDumneavoastra folositi MySQL ca un utilizator anonim si utilizatorii anonimi nu au voie sa schime paroleleTrebuie sa aveti privilegii sa actualizati tabelele in bazele de date mysql ca sa puteti sa schimati parolele altoraNu pot gasi nici o linie corespunzatoare in tabela utilizatoruluiLinii identificate (matched): %ld  Schimbate: %ld  Atentionari (warnings): %ldNu pot crea un thread nou (Eroare %d). Daca mai aveti memorie disponibila in sistem, puteti consulta manualul - ar putea exista un potential bug in legatura cu sistemul de operareNumarul de coloane nu corespunde cu numarul de valori la linia %ldNu pot redeschide tabela: '%-.192s'Folosirea unei value NULL e invalidaEroarea '%-.64s' obtinuta din expresia regulara (regexp)Amestecarea de coloane GROUP (MIN(),MAX(),COUNT()...) fara coloane GROUP este ilegala daca nu exista o clauza GROUP BYNu exista un astfel de grant definit pentru utilzatorul '%-.48s' de pe host-ul '%-.255s'Comanda %-.128s interzisa utilizatorului: '%-.48s'@'%-.64s' pentru tabela '%-.64s'Comanda %-.16s interzisa utilizatorului: '%-.48s'@'%-.64s' pentru coloana '%-.192s' in tabela '%-.192s'Comanda GRANT/REVOKE ilegala. Consultati manualul in privinta privilegiilor ce pot fi folosite.Argumentul host-ului sau utilizatorului pentru GRANT e prea lungTabela '%-.192s.%-.192s' nu existaNu exista un astfel de privilegiu (grant) definit pentru utilizatorul '%-.48s' de pe host-ul '%-.255s' pentru tabela '%-.192s'Comanda folosita nu este permisa pentru aceasta versiune de MySQLAveti o eroare in sintaxa RSQLDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useConectie terminata %ld la baza de date: '%-.192s' utilizator: '%-.48s' (%-.64s)Un packet mai mare decit 'max_allowed_packet' a fost primitEroare la citire din cauza lui 'connection pipe'Eroare obtinuta de la fcntl()Packets care nu sint ordonati au fost gasitiNu s-a putut decompresa pachetul de comunicatie (communication packet)Eroare obtinuta citind pachetele de comunicatie (communication packets)Timeout obtinut citind pachetele de comunicatie (communication packets)Eroare in scrierea pachetelor de comunicatie (communication packets)Timeout obtinut scriind pachetele de comunicatie (communication packets)Sirul rezultat este mai lung decit 'max_allowed_packet'Tipul de tabela folosit nu suporta coloane de tip BLOB/TEXTTipul de tabela folosit nu suporta coloane de tip AUTO_INCREMENTINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESNume increct de coloana '%-.100s'Handler-ul tabelei folosite nu poate indexa coloana '%-.192s'Toate tabelele din tabela MERGE nu sint definite identicNu pot scrie pe hard-drive, din cauza constraintului unic (unique constraint) pentru tabela '%-.192s'Coloana BLOB '%-.192s' este folosita in specificarea unei chei fara ca o lungime de cheie sa fie folositaToate partile unei chei primare (PRIMARY KEY) trebuie sa fie NOT NULL; Daca aveti nevoie de NULL in vreo cheie, folositi UNIQUE in schimbResultatul constista din mai multe liniiAceast tip de tabela are nevoie de o cheie primaraAceasta versiune de MySQL, nu a fost compilata cu suport pentru RAIDYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The handler for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionCimpul '%-.64s' e duplicat pentru cheia '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAcces interzis pentru utilizatorul: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setPartition '%-.64s' nu existaFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionCimpul e duplicat pentru cheia '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\��+�+russian/errmsg.sysnu�[��������k���Y�&��;��8�<��B��'	M	�	�	]
�
�
i�-�T
�
�
i��a�d��"R��R���.i��Fr��7y�� v��E��C�^��N } �!?"�")#�#�#=$y$�$4%�%&�&�&�&S(w(�()b)�)�)%*�*	+9+l+�+,-.�.+/l/�/*0_0�0+1^1F2�2{3V4�4(5�67L7�7�79~9�9�:J;�;�;x<�<�=�=�=m>�>?F?�?@�@A�A*B~B�BMC�C�CaD�D2E�E�FG|G�G�HIII�I�IBJ�J�JK�K1L�L
MHM�MBN�N�OP�P<QRS�StT>U�U7V�VW�WX�XVY�Y	ZpZ[�[M\�\c]&^v^�^_N_�_y`aPa�aMb�b�c�ccd�d#e�e�e�f�fg6gdg�g�g&hQh�h�hi/i~i�i$jRj�j�j�j0kHk�k�k�kl^l�l�lm+mlm�m�m%nRn�n�nso�p�pEqrAr`r�rs8sTs�s�s/tot�tuGusu�uv_v~v�v�vw'wkw�w�w�w�wx"x@xTxox�x�x�xy�y�yzUzmz�z�z�z�z{{/{G{k{�{�{�{�{�{|.|^|�|�|�|E}�}�}<~�~:���;�t������"����[���������:�g�u����.���ǅ��D�e�����Ɔ��:�[�������A���������r������"�Y��=���̌$�Y�����ȍ
�I�y�����v������j���w����7�p����?������~��,�j���
�4�Q�����ٗe���[�����=���К�Z���ܛE����a���֝�U�������B�z�����ϟ	�V�{����O�����Q���Ϣ�D���ͣ.�_���Ҥ2�^���٥�K�}�˦�F���ϧ�p���ݨ!�G�|����|������C�{���ѫ���ͬ�B�a�����ڭ��6���ۮ�"�\�ݯ��9�Q�q�����ְ�.�N�����8�T�r����F�k�ٳj�ʴ�h���͵��7�P���	�%�d�������F���˸��/�˹�L���Ǻ�J�ǻK�����%�@�\�p�������[���Ⱦ�>�n���̿)�R������,�W�������'�e�����g�����
�=�p����������
��=�s�������	�4�_��������%�������5�_�|�����9�����D�����D���i���r�����;�����g�����Z�������5�l�����B�������4�U�����I��������i�����C�����>����>���������������w�L��j�������1�[�����2�u����S��������D���+�q������e���>�k�������<�����J��
�B�[�����?����K�����S�����D��������y���d���
�s���j�����������2�|�������*�i���#�:�Q���y��3c���)Mj���-l�+���e��m�F��Vv�r��?	�	�	
�
�
%e���@���
>
Z�n�V��&p�+w���,��b����H����/m�Z�k��*T��% 8 W � �!p"�"�"#e#�#3$v%�%�%C&�&�&�&'0'w'�'(g(�(�(�(
)=)i)�)�)�)*+*V*�*�*V+�+(,`,�,�,�,�,�-�-_.s.�.�.;/h/�/�/.0s0�0+11�1%2�2�23�3�4�5D6�6�6%8�8�879�9_:�:
;V;�;�;<l<�<�<%=o=�=�=?>>�>S?�?@�@�@A%AHAbA�A�A�AB@BmB�B5CbC�C�C"DxD ETErE�E&FlF�F�F4GvG�G*HEH�H"I[I�I�I&JiJ�J�JKOK�KLOLsL�L�L�L%MbMyM�M�M�MhN�NOiOlP�P�P�P*Q�Q�Q�Q�QXRzR�RiST-TT�T
U�U/V�V+WJW�W�WX]XsX�X�X�X�Y�YQZ}Z�Z[G[][t[�[�[\\.\D\i\�\�\�\�].^]^�^_�_4`z`�`a�alb�bc_c�c�cdGdqd�d�d�deOepe�e f=fzf�f0gbg�gph�h�h�hi'iVi�i�ijIjtj�j�jNk�k�klSl�lm~m�m nrn�n�no0oko�o�op0pFpSpYp�p�pqcq�qr>r�r�r.sZs�s�sUt�t�tku�u�v0whw�w�w�wMx�x�xyLy�y/z�z�z�zO{�{�{.|h|�|}j}�}�}~W~�~�~*��� �e�����@���ف*�S���Ȃ�5���҃!�r��T���Ņ��?�{�Ԇ=�k�̇K�i�Ȉ����*�����Ȍ���@�R�k�������<�Z�t�����L�y�ď�4�k�����d���3�m���͒Q�z���Y���E�y���Օ�D�x�Ӗ�0�n���ߗ�o���ј�ƙ��	�Y�����/�U����;�u����b���ĝp�2������*�<�á(�\����b�ڣ�������H�����:�������e���J���٬�j���6�c�ή�>�i�����B���ΰ4�ұ$�l�����L��������E�˵�|��j��8���θ�����չ
�F�x�˺A����P����)�K���ý�����������/�j����_������H�~���+�x��������~��:�w�������~���>�������.�����0�r����4�V�������#�x������r���i������K�����*�M������Q���������9�y����q�������k�������<�����*�����V���"�D�s��*�e�����Z����� �=��������0�a����U������8���"���b���+�X���������o���+����+���K�����@�����V�����
�H�r���b����K���������O�����+�Y�0������X��Q����{�����D���H�w�A�z������v�0"l���"�e�P�7f�%Q�Q	�	^
�h 
�
_Kw��t��m�X�A��M�P�m�|��q�K����M�F�:g��N � 3!�!*"�"	#i#�$�$%A%x%�%�%\&�&W'�'�'w(�(o)r)�)
*X*�*++�+k,�,C-�-G.�.%/�/�0,1�1/2�2�263�3�3%4�5v6�6'7e7�8�8M9�93:V:�:�:�:;�;</<S<~<�<=/=X=z=�=>u>�>�>?z?�?n@�@"AzA�ABqB�B�B7C�C�C�D�DEJE�EGF�FDG$HcH�H�H�HI+I=I�I�I�IJPJ�J�J:KTK�K,LTL�L�L8M_M�M�M�M#NKNuN�N�N�NOKO�ObP�P�P�PQ:QhQ�Q�Q�QR?RCRyR�R�R+SfS�S�SOT�T�T�T<UdU�U�U�U@V\V�V�V�VWAW�W�W/XnX�XGY�Y�Z�Z�Z)[�[�[(\n\]^]�]^E^w^�^�^�^_G_�_-`�`,a�a�atb�b�bcSc�c�c1dVd�d�d/eee�e�e	f'fUf^fif�f�f+gg�g�g
hh$h/hvh�h�hi$i6i[i~i�i�i3jij�j�jkfk�k�k�k�kcl�l�lm5m�m�mo\o�o(pppJq�q_r�r�r�r�r(sPsls�s�stu]uu�uv=v�v�v�v7wfw�w�wTxUy�y�y�yZz�z�z{/{\{�{|B|�|�|}[}�}�}�}~5~`~�~�~	&e���<�q����'�7�U��	�%�\���~�R���Ʌ��M����׆�4�V�w�����3�F�]�x����'�^���ۉ�&�A�q���Ŋ��>�k���ϋ��!�D�m���Ԍ�9�Z�n�����K����%�X���ŏ��&�M�s���ǐ��a�����K����I���ʓ@���@�z���|��*�ė���$�ݚ9�o�����W����4�[�Ɲ�*���K���:����j���ҡ�7�N�v������9�h�����D�����������P����n���˧��Q���ި.�v���O�z��)�U����5�u���ެ���̮v�Z���Ű���1�H���������=�p��������״
�5�v���Ķ�9�����Ƿ����Ź�E�w���-�c���߻�w���L�z����N���ھ+����Կ��T�������H������`����'�M�`������;�e�����.�]�����6�|�����=���l����_��������'�c��������Q�m����� �y�������;�c��������W�����?�Z��������q�,�J�j�����:������i������k�������$�!�W�}��������t���!���������
�D�����7�n������������O�}�(�>��������V�u���R�<�n���G���2�����r���G�_�{������������3���������7�y�����/���������	�1�c��������K�p���2�a������R����l�����J�u�����Y������I���"�O�����T������������c��C�������!�?�s�����e�7��r��9e��0e|���Ai���;o��8c����	6	a	�	�	�	(
S
z
�
��>[���

�
�
�
0����(X��4Sp���Gn���,CZ���;h���A}��:z��>`���F���
V��m��3]v���
|�8��
���Lu�}�� � !x!�!�!0"c""#b#�#G$�$�$%2%y%�%�%*&a&�&�&'J'�'�'�'N(�(�()b)�)*B*a*�*�*�*G+�+�+[,|,-=-.b.j.u.�.�.�./b/�/0{0�0�0U1�1�1&2?2x2�24q4$5�5�5�5�6�627Z7�7&8F8g9�9�9�9(:�:.;�;�;,<Z<k<�<�<�=�=�>�>�?�?@X@�@�@
A�A�AB>B|B�B!C^CkC�C�C�C�D�DE�E�EFXF�F�F�FG>GuG�G�G�G�G*H�H.I_I�I�J9K=KpK�K�KLxL�LZM�M�M*NtN�N�NO<O�O�O�OPmP�P�P.QtQ�Q�QARnR�R�R�RKS�S�SJT�T�T�T�T2UsU�U�U�UVoV�V�VMWwW�W�WXBXjX�XY>YaY�Y�Y�Y0ZZ�Z�Z[[a[�[h\�\G]�]/^N^d^�^�^[_�_3`v`�`	aTa|a�a"b:b�bc�cNd�d;ebe�e�e�e�e�e�e�e�e�e#f&f9f�f�fggGghg�g�g�g�gRh�h%i�i�ij0jNj�j�jk;kpk�klcl�l�lmRm�m#n�n�opDpyp�p�q�qr4rXr�r�r�r�rsVs�s�s�s�s#tKtft�t�t�t�t�t�t&u]u�u�u�u�u+vTv�v�v�v�v$w^w�w�w�w	x+xPxwx�x�x%yqy�y�yzMz�z�z{7{Q{t{�{�{ |>|{|�|�|}7}c}}}�}�}3~�~�~�~�~&u���.�[�������&�>�Y�\��`�1�����܃"�e������ �N�����Յ�_�������1�Q�q�����ׇ�>�\�w�����<�������ɉщۉ�0�s������f���X�|���������̌��x���Ս�W�p��L�����͒��@�^���Ó�4�C�s���̔��0�a������ �Y������&�k����R�������ژ���L�k���ϙ
�2�t����#�V�|�����V�w��������<�d�����%�K�r�����̞ߞ
�4�N�s������H�f���Š��;�u�����A�â���`��������1�����"�U�����
��T�t���Χ���������!�n����
�;�Z�z��������*�F�d�����!�E�a������H���ծ=���C���������O��{�ɳ.���Ǵ��$����.�O������*�x������N�[�ڹ�O�������H�y���
�g����{��_����Z���ݿ>�������L���;���������)�o��2�Z���~�������*�Q�����
�K�������0�n���9�k��������>�a�����,�W�����*�[������R��������l���S���%�T���)���$���F����`���&�\��������+���;�����p�����
�.�����G�����<����>����m���=���L����������K�l�����T����X������m�����V����]�����������������S���$�h���E����� �f��7��)�g����S����7�u���,����l����c�����J����q������+~�1[�� �i���.[�O��
A{��K��	:	l	�	+
f
�
R���
�
�
2����"\�5�?�
H}�0z�U�!f�p�Sf��=g��*��X��e � 1!d!�!�!"S"�"�"7#�#�#N$�$�$�$,%q%�%�%�%�%
&*&Q&n&�&�&�&'S'�'�'�'(^(v(�(�();)l)�)�)*z*�*
+$+V+�+�+,],�,�,�,#-0-n-�-�-.3.`.�.�./J/M//�/�/�/10[0�0�0�0O1�1�1I3�34;4u4�4�4�45I5�5�5�56�6C7F7I7L7O7R7U7X7[7^7a7d7g7j7m7p7s7v7y7|77�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7�7Q8T8W8Z8]8`8c8f8i8l8o8r8u8x8{8~8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�8�89999999999 9#9&9)9,9/9295989;9>9A9D9G9J9M9P9S9V9Y9\9_9b9e9h9k9n9q9t9w9z9}9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9�9J:M:P:S:V:Y:\:_:b:e:h:k:n:q:t:w:z:}:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:�:;;;
;
;;;;;;;";%;(;+;.;1;4;7;:;=;@;C;F;I;L;O;R;U;X;�;�;<Q<|<�<�<�<�<�<�<�<$>G>o>�> ?#?x?�?@V@�@JA�A�A"BaB�B�B�C0EbE�E�E"F%F(F+F.FbFeFhFkFnFqFtFwFzF}F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�F�FzG}G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�G�GHHVH�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�H�HIIIIIIIIII I#I&I)I,I/I2I5I8I;I>IAIDIGIJIMIPISIVIYI\I_IbIeIhIkInIqItIwIzI}I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�IJJJ
J
JJJJJJJ"J%J(J+J.J1J4J7J:J=J@JCJFJIJLJOJRJUJXJ[J^JaJdJgJjJmJpJsJvJyJ|JJ�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�JKKKKK!K$K'K*K-K0K3K6K9K<K?KBKEKHKKKNKQKTKWKZK]K`KcKfKiKlKoKrKuKxK{K~K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�KZL]L`L�L�L�L�L�L�L�L�L�L�LMMMMMMMMMM M#M&M)M,M�M�M_N�NPYP�P�P4QuQ�Q�Q�Q(RsRvR�R�R�R�R5StS�S=TjT�T�T�T>UtU�UDV�V�V�W�WnX,Y/Y2YyY�Y1Z_ZbZeZ|ZZ�Z�Z�Z�Z�Z;[�[�[A\k\�\];]r]�]�]�]/^�^�^�^2_`�`�`Wa�a�a�a�a�a�a�a�abbbbbbbbbb b#b&b)b,b/b2b5b8b;b>bAbDbGbJbMbPbSbVbYb\b_bbbebhbkbnbqbtbwbzb}b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�b�bccc
c
ccccccc"cAcDcGc�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�c�cdddddddddd d#d&d)d,d/d2d5d8d;d>dAdDdGdJdMdPdSdVdYd\d_dbdedhdkdndqdtdwdzd}d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�d�deee
e
eeeeeee"e%e(e+e.e1e4e7e:e=e@eCeFeIeLeOeReUeXe[e^eaedegejemepeseveye|ee�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�e�ef�f�fgvg�gh6h�h�h�h"iRi�i�i�i�ijBj�j�jk"kGkhk�k�k�kl9ldl�l�lm1m�m�m�m�mn8n�n�n"o^o}o�opcp�p?q�q�q�q�qr2rzr�r2sas�s�s�skt�t�t�t�t�t�t�t�tuuuu�u�u�uv�v�v�v�vEwpw�w
x�yDzaz�z�z�{�|>}Y}�}�}�}�}~6�̀��5�v�������āǁʁ́ЁӁցف"�L�O�m�p�����тԂ�����
�
�������"�%�(�X�[�^�a�d�g�j�m�p�s�v�y�|������������������.�Q�T���"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�����w������M�w���Ƈ���)�n���Ո�����������������ÉƉɉ�;�>�J�M�P�������ڍ��|����6�K�s����������ܔ(�s���������*�F�����@�N�o����ʘ�"�A�j���ș��8�`���D������G����Q�����ĝ��6�S�w�Ǟݞ�ɟ
�|�������F������b���̢E����D�i�����ĤǤ�X�����Х���Q��������������������T����&��������#�]������g�ë�x��a���N�����.���e���Ͱ�4���ı(�P�q���"�Z�
������5���"�W�ʷ߷��I���θ��=�@�����8�Z�u���`�����»��
��V���¼
�R�ý�������'�`�����[�����:�v��c����l����K�����6��� �����m���>������m����:����������,�v�����,�������)�a����G�q�������@�l������.�n�����L�m��������-�U�����
�T����c���*����������#�T���������K���������x�������
������4�t�����3�x����5���[������/�l������\������o����c�����G��� ���C�u�����!�n������C�b������T�����B������B��������A�X��������������
�A����U�������I��u�����y���]������#�h��������+�N��6�z��������e*a�h�:��Z�V�[�	X	�	�	0
N
�
�2h

a
�
��,h�W������� #&),/258;>ADGJ���CFILOR��<^a���Ow�JM$|��b���� w�g0��D��?��;��/ � � � � � � � � � � � � � � � � � � � � � � � � � � � � !!!!!!!!!! !]!�!�!""a"�"�"�"C#�#$}$�$)%,%�%&�&R'p'�'�'@(r(�(�(�()�)b*+�+�,�,�,�-�./c/�1�2k3y4|44�45�5S6�6�7929`9�9�9�9�9+:t:�:!;M;�;;<�<�<7=}=�=>>m>�>�?@a@�@�@lA�AB�B�C�C�DaE�E�FG�G�H�HCIkI�IJ�J�J�KoL�LuM
N,OdO�OP~PQ�QR�RS>SAS�S�T�UFV�VUW�WoX�X�XYUY�Y�Y�Z�[�\�]�^_�_M`aba�a�ab-bGbzb�b3cfc�c�c�cd+dLdeYfvf�f�fgJgmg�ghWh�hiui�i)j
l8lLn�npo�op�p�p�qrr�r#sds�sRt�t�t�u6v�v�v�vw/w�w�w�w�w�w�x�x%y(y+yz�z>{l{�{|4|||�|}�}~G~�~k�h��ʁ��_�4������F�������;�`�������#��E�����[�����ډ�4�z�����H�
�ȏ0�Y������Q�����^���ǔ2�ҕx����Z��5�����	��C��
�X�|�̛�i���Ĝ��B�~�����ڝ���=�P���V���	�\�ˠ�.�s�X�j�z�¥ҥ���M���&����s�Ψ&�q����q����D���ϫ������i���N�����I�˰L���=����]����Ŵt���|���S�ȷ��.�W�������$�P����;����q�ѻ3����B�`���������ܽ����?�m�������9�����������2���F���X�������
�7��������8�����q�����D������`�������Q�.���2�hashchkisamchkНЕТДАНевозможно создать файл '%-.200s' (ошибка: %d - %s)Невозможно создать таблицу '%-.200s' (ошибка: %d - %s)Невозможно создать базу данных '%-.192s' (ошибка: %d - %s)Невозможно создать базу данных '%-.192s'. База данных уже существуетНевозможно удалить базу данных '%-.192s'. Такой базы данных нетОшибка при удалении базы данных (невозможно удалить '%-.192s', ошибка: %d - %s)Невозможно удалить базу данных (невозможно удалить каталог '%-.192s', ошибка: %d - %s)Ошибка при удалении '%-.192s' (ошибка: %d - %s)Невозможно прочитать запись в системной таблицеНевозможно получить статусную информацию о '%-.200s' (ошибка: %d - %s)Невозможно определить рабочий каталог (ошибка: %d - %s)Невозможно поставить блокировку на файле (ошибка: %d - %s)Невозможно открыть файл: '%-.200s' (ошибка: %d - %s)Невозможно найти файл: '%-.200s' (ошибка: %d - %s)Невозможно прочитать каталог '%-.192s' (ошибка: %d - %s)Невозможно перейти в каталог '%-.192s' (ошибка: %d - %s)Запись изменилась с момента последней выборки в таблице '%-.192s'Диск заполнен. (%s). Ожидаем, пока кто-то не уберет после себя мусор... (ошибка: %d - %s)Невозможно произвести запись, дублирующийся ключ в таблице '%-.192s'Ошибка при закрытии '%-.192s' (ошибка: %d - %s)Ошибка чтения файла '%-.200s' (ошибка: %d - %s)Ошибка при переименовании '%-.210s' в '%-.210s' (ошибка: %d - %s)Ошибка записи в файл '%-.200s' (ошибка: %d - %s)'%-.192s' заблокирован для измененийСортировка прерванаПредставление '%-.192s' не существует для '%-.192s'Получена ошибка %d - '%-.192s' от обработчика таблицОбработчик таблицы '%-.192s' не поддерживает эту возможностьНевозможно найти запись в '%-.192s'Некорректная информация в файле '%-.200s'Некорректный индексный файл для таблицы: '%-.200s'. Попробуйте восстановить егоСтарый индексный файл для таблицы '%-.192s'; отремонтируйте его!Таблица '%-.192s' предназначена только для чтенияНедостаточно памяти. Перезапустите сервер и попробуйте еще раз (нужно %d байт)Недостаточно памяти для сортировки. Увеличьте размер буфера сортировки на сервереНеожиданный конец файла '%-.192s' (ошибка: %d - %s)Слишком много соединенийНедостаточно памяти; удостоверьтесь, что mysqld или какой-либо другой процесс не занимает всю доступную память. Если нет, то вы можете использовать ulimit, чтобы выделить для mysqld больше памяти, или увеличить объем файла подкачкиНевозможно получить имя хоста для вашего адресаНекорректное приветствиеДля пользователя '%-.48s'@'%-.64s' доступ к базе данных '%-.192s' закрытДоступ закрыт для пользователя '%-.48s'@'%-.64s' (был использован пароль: %s)База данных не выбранаНеизвестная команда коммуникационного протоколаСтолбец '%-.192s' не может принимать величину NULLНеизвестная база данных '%-.192s'Таблица '%-.192s' уже существуетНеизвестная таблица '%-.129s'Столбец '%-.192s' в %-.192s задан неоднозначноСервер находится в процессе остановкиНеизвестный столбец '%-.192s' в '%-.192s''%-.192s' не присутствует в GROUP BYНевозможно произвести группировку по '%-.192s'Выражение содержит групповые функции и столбцы, но не включает GROUP BY. А как вы умудрились получить это сообщение об ошибке?Количество столбцов не совпадает с количеством значенийСлишком длинный идентификатор '%-.100s'Дублирующееся имя столбца '%-.192s'Дублирующееся имя ключа '%-.192s'Дублирующаяся запись '%-.192s' по ключу %dНекорректный определитель столбца для столбца '%-.192s'%s около '%-.80s' на строке %dЗапрос оказался пустымПовторяющаяся таблица/псевдоним '%-.192s'Некорректное значение по умолчанию для '%-.192s'Указано несколько первичных ключейУказано слишком много ключей. Разрешается указывать не более %d ключейУказано слишком много частей составного ключа. Разрешается указывать не более %d частейУказан слишком длинный ключ. Максимальная длина ключа составляет %d байтКлючевой столбец '%-.192s' в таблице не существуетСтолбец типа BLOB '%-.192s' не может быть использован как значение ключа в таблице такого типаСлишком большая длина столбца '%-.192s' (максимум = %lu). Используйте тип BLOB или TEXT вместо текущегоНекорректное определение таблицы: может существовать только один автоинкрементный столбец, и он должен быть определен как ключ%s: Готов принимать соединения.
Версия: '%s'  сокет: '%s'  порт: %d%s: Корректная остановка
%s: Получен сигнал %d. Прекращаем!
%s: Остановка завершена
%s: Принудительно закрываем поток %ld  пользователя: '%-.48s'
Невозможно создать IP-сокетВ таблице '%-.192s' нет такого индекса, как в CREATE INDEX. Создайте таблицу зановоАргумент разделителя полей - не тот, который ожидался. Обращайтесь к документацииФиксированный размер записи с полями типа BLOB использовать нельзя, применяйте 'fields terminated by'Файл '%-.128s' должен находиться в том же каталоге, что и база данных, или быть общедоступным для чтенияФайл '%-.200s' уже существуетЗаписей: %ld  Удалено: %ld  Пропущено: %ld  Предупреждений: %ldЗаписей: %ld  Дубликатов: %ldНекорректная часть ключа. Используемая часть ключа не является строкой, указанная длина больше, чем длина части ключа, или обработчик таблицы не поддерживает уникальные части ключаНельзя удалить все столбцы с помощью ALTER TABLE. Используйте  DROP TABLEНевозможно удалить (DROP) '%-.192s'. Убедитесь что столбец/ключ действительно существуетЗаписей: %ld  Дубликатов: %ld  Предупреждений: %ldНе допускается указание таблицы '%-.192s' в списке таблиц FROM для внесения в нее измененийНеизвестный номер потока: %luВы не являетесь владельцем потока %luНикакие таблицы не использованыСлишком много значений для столбца %-.192s в SETНевозможно создать уникальное имя файла журнала %-.200s.(1-999)
Таблица '%-.192s' заблокирована уровнем READ lock и не может быть измененаТаблица '%-.192s' не была заблокирована с помощью LOCK TABLESНевозможно указывать значение по умолчанию для столбца BLOB '%-.192s'Некорректное имя базы данных '%-.100s'Некорректное имя таблицы '%-.100s'Для такой выборки SELECT должен будет просмотреть слишком много записей и, видимо, это займет очень много времени. Проверьте ваше указание WHERE, и, если в нем все в порядке, укажите SET SQL_BIG_SELECTS=1Неизвестная ошибкаНеизвестная процедура '%-.192s'Некорректное количество параметров для процедуры '%-.192s'Некорректные параметры для процедуры '%-.192s'Неизвестная таблица '%-.192s' в %-.32sСтолбец '%-.192s' указан дваждыНеправильное использование групповых функцийВ таблице '%-.192s' используются возможности, не поддерживаемые в этой версии MySQLВ таблице должен быть как минимум один столбецТаблица '%-.192s' переполненаНеизвестная кодировка '%-.64s'Слишком много таблиц. MySQL может использовать только %d таблиц в соединенииСлишком много столбцовСлишком большой размер записи. Максимальный размер строки, исключая поля BLOB, - %ld. Возможно, вам следует изменить тип некоторых полей на BLOBСтек потоков переполнен:  использовано: %ld из %ld стека.  Применяйте 'mysqld --thread_stack=#' для указания большего размера стека, если необходимоВ OUTER JOIN обнаружена перекрестная зависимость. Внимательно проанализируйте свои условия ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerНевозможно загрузить функцию '%-.192s'Невозможно инициализировать функцию '%-.192s'; %-.192sНедопустимо указывать пути для динамических библиотекФункция '%-.192s' уже существуетНевозможно открыть динамическую библиотеку '%-.192s' (ошибка: %d %-.128s)Невозможно отыскать символ '%-.128s' в библиотекеФункция '%-.192s' не определенаХост '%-.255s' заблокирован из-за слишком большого количества ошибок соединения. Разблокировать его можно с помощью 'mysqladmin flush-hosts'Хосту '%-.255s' не разрешается подключаться к этому серверу MySQLВы используете MySQL от имени анонимного пользователя, а анонимным пользователям не разрешается менять паролиДля того чтобы изменять пароли других пользователей, у вас должны быть привилегии на изменение таблиц в базе данных mysqlНевозможно отыскать подходящую запись в таблице пользователейСовпало записей: %ld  Изменено: %ld  Предупреждений: %ldНевозможно создать новый поток (ошибка %d). Если это не ситуация, связанная с нехваткой памяти, то вам следует изучить документацию на предмет описания возможной ошибки работы в конкретной ОСКоличество столбцов не совпадает с количеством значений в записи %ldНевозможно заново открыть таблицу '%-.192s'Неправильное использование величины NULLПолучена ошибка '%-.64s' от регулярного выраженияОдновременное использование сгруппированных (GROUP) столбцов (MIN(),MAX(),COUNT(),...) с несгруппированными столбцами является некорректным, если в выражении есть GROUP BYТакие права не определены для пользователя '%-.48s' на хосте '%-.255s'Команда %-.128s запрещена пользователю '%-.48s'@'%-.64s' для таблицы '%-.64s'Команда %-.16s запрещена пользователю '%-.48s'@'%-.64s' для столбца '%-.192s' в таблице '%-.192s'Неверная команда GRANT или REVOKE. Обратитесь к документации, чтобы выяснить, какие привилегии можно использоватьСлишком длинное имя пользователя/хоста для GRANTТаблица '%-.192s.%-.192s' не существуетТакие права не определены для пользователя '%-.48s' на компьютере '%-.255s' для таблицы '%-.192s'Эта команда не допускается в данной  версии MySQLУ вас ошибка в запросе. Изучите документацию по используемой версии MySQL на предмет корректного синтаксисаDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useПрервано соединение %ld к базе данных '%-.192s' пользователя '%-.48s' (%-.64s)Полученный пакет больше, чем 'max_allowed_packet'Получена ошибка чтения от потока соединения (connection pipe)Получена ошибка от fcntl()Пакеты получены в неверном порядкеНевозможно распаковать пакет, полученный через коммуникационный протоколПолучена ошибка в процессе получения пакета через коммуникационный протокол Получен таймаут ожидания пакета через коммуникационный протокол Получена ошибка при передаче пакета через коммуникационный протокол Получен таймаут в процессе передачи пакета через коммуникационный протокол Результирующая строка больше, чем 'max_allowed_packet'Используемая таблица не поддерживает типы BLOB/TEXTИспользуемая таблица не поддерживает автоинкрементные столбцыINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESНеверное имя столбца '%-.100s'Использованный обработчик таблицы не может проиндексировать столбец '%-.192s'Не все таблицы в MERGE определены одинаковоНевозможно записать в таблицу '%-.192s' из-за ограничений уникального ключаСтолбец типа BLOB '%-.192s' был указан в определении ключа без указания длины ключаВсе части первичного ключа (PRIMARY KEY) должны быть определены как NOT NULL; Если вам нужна поддержка величин NULL в ключе, воспользуйтесь индексом UNIQUEВ результате возвращена более чем одна строкаЭтот тип таблицы требует определения первичного ключаЭта версия MySQL скомпилирована без поддержки RAIDВы работаете в режиме безопасных обновлений (safe update mode) и попробовали изменить таблицу без использования ключевого столбца в части WHERE. %sКлюч '%-.192s' не существует в таблице '%-.192s'Невозможно открыть таблицуОбработчик таблицы не поддерживает этого: %sВам не разрешено выполнять эту команду в транзакцииПолучена ошибка %d - '%-.192s' в процессе COMMITПолучена ошибка %d - '%-.192s' в процессе ROLLBACKПолучена ошибка %d в процессе FLUSH_LOGSПолучена ошибка %d в процессе CHECKPOINTПрервано соединение %u к базе данных '%-.192s' пользователя '%-.48s' с хоста '%-.255s' (%-.64s)Обработчик этой таблицы не поддерживает двоичного сохранения образа таблицы (dump)Двоичный журнал обновления закрыт, невозможно выполнить RESET MASTERОшибка перестройки индекса сохраненной таблицы '%-.192s'Ошибка от головного сервера: '%-.64s'Возникла ошибка чтения в процессе коммуникации с головным серверомВозникла ошибка записи в процессе коммуникации с головным серверомНевозможно отыскать полнотекстовый (FULLTEXT) индекс, соответствующий списку столбцовНевозможно выполнить указанную команду, поскольку у вас присутствуют активно заблокированные таблица или открытая транзакцияНеизвестная системная переменная '%-.64s'Таблица '%-.192s' помечена как испорченная и должна пройти проверку и ремонтТаблица '%-.192s' помечена как испорченная и последний (автоматический?) ремонт не был успешнымВнимание: по некоторым измененным нетранзакционным таблицам невозможно будет произвести откат транзакцииТранзакции, включающей большое количество команд, потребовалось более чем 'max_binlog_cache_size' байт. Увеличьте эту переменную сервера mysqld и попробуйте еще разЭту операцию невозможно выполнить при работающем потоке подчиненного сервера. Сначала выполните STOP SLAVEДля этой операции требуется работающий подчиненный сервер. Сначала выполните START SLAVEЭтот сервер не настроен как подчиненный. Внесите исправления в конфигурационном файле или с помощью CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logНевозможно создать поток подчиненного сервера. Проверьте системные ресурсыУ пользователя %-.64s уже больше чем 'max_user_connections' активных соединенийВы можете использовать в SET только константные выраженияТаймаут ожидания блокировки истек; попробуйте перезапустить транзакциюОбщее количество блокировок превысило размеры таблицы блокировокБлокировки обновлений нельзя получить в процессе чтения не принятой (в режиме READ UNCOMMITTED) транзакцииНе допускается DROP DATABASE, пока поток держит глобальную блокировку чтенияНе допускается CREATE DATABASE, пока поток держит глобальную блокировку чтенияНеверные параметры для %s'%-.48s'@'%-.64s' не разрешается создавать новых пользователейНеверное определение таблицы; Все таблицы в MERGE должны принадлежать одной и той же базе данныхВозникла тупиковая ситуация в процессе получения блокировки; Попробуйте перезапустить транзакциюИспользуемый тип таблиц не поддерживает полнотекстовых индексовНевозможно добавить ограничения внешнего ключаНевозможно добавить или обновить дочернюю строку: проверка ограничений внешнего ключа не выполняетсяНевозможно удалить или обновить родительскую строку: проверка ограничений внешнего ключа не выполняетсяОшибка соединения с головным сервером: %-.128sОшибка выполнения запроса на головном сервере: %-.128sОшибка при выполнении команды %s: %-.128sНеверное использование %s и %sИспользованные операторы выборки (SELECT) дают разное количество столбцовНевозможно исполнить запрос, поскольку у вас установлены конфликтующие блокировки чтенияИспользование транзакционных таблиц наряду с нетранзакционными запрещеноОпция '%s' дважды использована в выраженииПользователь '%-.64s' превысил использование ресурса '%s' (текущее значение: %ld)В доступе отказано. Вам нужны привилегии %-.128s для этой операцииПеременная '%-.64s' является потоковой (SESSION) переменной и не может быть изменена с помощью SET GLOBALПеременная '%-.64s' является глобальной (GLOBAL) переменной, и ее следует изменять с помощью SET GLOBALПеременная '%-.64s' не имеет значения по умолчаниюПеременная '%-.64s' не может быть установлена в значение '%-.200s'Неверный тип аргумента для переменной '%-.64s'Переменная '%-.64s' может быть только установлена, но не считанаНеверное использование или в неверном месте указан '%s'Эта версия MySQL пока еще не поддерживает '%s'Получена неисправимая ошибка %d: '%-.512s' от головного сервера в процессе выборки данных из двоичного журналаReplica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchОперанд должен содержать %d колонокПодзапрос возвращает более одной записиUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existЦиклическая ссылка на подзапросПреобразование поля '%s' из %s в %sСсылка '%-.64s' не поддерживается (%s)Every derived table must have its own aliasSelect %u был упразднен в процессе оптимизацииTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedСервер запущен в режиме --secure-auth (безопасной авторизации), но для пользователя '%s'@'%s' пароль сохранён в старом формате; необходимо обновить формат пароляПоле или ссылка '%-.192s%s%-.192s%s%-.192s' из SELECTа #%d была найдена в SELECTе #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Кеш запросов не может установить размер %lu, новый размер кеша зпросов - %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadТаблица %-.100s в %s не может изменятсяThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementСлишком большой конфигурационный файл '%-.192s'Неверный заголовок типа файла '%-.192s'Неожиданный конец файла в коментарии '%-.200s'Ошибка при распознавании параметра '%-.192s' (строка: '%-.192s')Неожиданный конец файла при пропуске неизвестного параметра '%-.192s'EXPLAIN/SHOW не может быть выполненно; недостаточно прав на такблицы запросаФайл '%-.192s' содержит неизвестный тип '%-.64s' в заголовке'%-.192s.%-.192s' - не %sСтолбец '%-.192s' не обновляемыйView SELECT содержит подзапрос в конструкции FROMView SELECT содержит конструкцию '%s'View SELECT содержит переменную или параметрView SELECT содержит ссылку на временную таблицу '%-.192s'View SELECT и список полей view имеют разное количество столбцовАлгоритм слияния view не может быть использован сейчас (алгоритм будет неопеределенным)Обновляемый view не содержит ключа использованных(ой) в нем таблиц(ы)View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION для необновляемого VIEW '%-.192s.%-.192s'проверка CHECK OPTION для VIEW '%-.192s.%-.192s' провалилась%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0Проверка контрольной суммы текста VIEW провалиласьНельзя изменить больше чем одну базовую таблицу используя многотабличный VIEW '%-.192s.%-.192s'Нельзя вставлять записи в многотабличный VIEW '%-.192s.%-.192s' без списка полейНельзя удалять из многотабличного VIEW '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: эту команду нельзя выполнять когда глобальная транзакция находится в состоянии '%.64s'XAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionДублирующаяся запись '%-.64s' по ключу '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTДоступ закрыт для пользователя '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Неизвестное имя формата команды EXPLAIN: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionДублирующаяся запись по ключу '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\C�**����serbian/errmsg.sysnu�[��������I~��h��Z���*g��2w��"Oo���
0Z���P����	E	�	�	�	
&
?
]
x
�
�
�
&H����,W{���
R
�
�
r�J����:��p��4Q�Y|���1��
*I1b���Qy��!�4��%[���0S�}�,jP{��? � � 4!�!�!"o"�"�"#;#�#�#$,$O$w$�$�$�$+%�%�%&h&�&�&'K'�'&(M(�(�(O)~)�)�)*@*�*�*�*P+�+�+,/,p,�,�,O-x-�-".f.�.v/�/z0
1\1�12f2�23k3�3�324�45:5d5�5�56<6i6�6�67�7�7�7=8�8�8�889e9�9�9�9.:v:�:�:�:#;D;z;�;�;�;<;<e<�<=9=l=�=�=>/>�>�>�>�>E?�?�?�?@S@�@�@A9A�A�AZB�B8C�C@D}D�D�D�D/EKE�E�E&FZF�F�F2G^G�GHJHiH�H�H�HIVI�I�I�I�I�I
J+J?JZJ�J�J�J	KkK�KL@LXLwL�L�L�L�LMM2MVM�M�M�M�M�M�MNIN�N�N�NO3OjO�O�O.PeP�P�P�P�P,Q`Q�Q.RvR�R4SfS}S�S�S�ST@TNT�T�T�TU`U�U�U�U�U0VBV_V�V�V�V�V>WPW�W�W�WXAXWX�X�X�XY[Y�Y�Y�Y�YSZ�Z�Z[u[�[�[\\^\�\�\]7]d]�]�]8^�^�_N`�`�`:a�a�ab@b�b�bcpc�c5d}d�d�d^e�e�e�ef*f�fg�g�gh�h�h!i]i�i�i-j�j�j>k�k�k'lWl�l�lm<mim�m�m�m�m nZn�n�n�n_o�o�oHp�p�p qUq�q�qrr�r�r#s�s�s�s*tbt�t�tu\u�u�u vRv�v�v.wrw�w�wxcx�xyFyky�y�y�y"zjz�z{X{�{�{�{�{+|?|Q|�|�|,}@}s}�}.~M~�~�~�~�~�~'d��4�`�����À�X�����*����g�����E�V������Z�v������2�S������N����_���و�C�{���|����F�V�q���������L�������8�o���Ս��Z�����Ԏ�]�������%�X����+���ԑ�;�n������'�4�>�F�n���ē��:�e�������=�V����.�f�����ז�j����u��Ǚu����&���(�Νl�ʞ0����.���Š�*�f������s�����*�e������z������N��ť�Y���/�ѧT����T���̩��2�������b�������G�q����H����/�i���ݴ
�,�Z��A���Ķ�-�{��T�����и�O���ٹ]���U�n���ּR���!�^�����f����W���������w��������#�}�������������E�g����������T����%�<���d����N����������8�U����������W���������P�{�����X���1�|���A�a�{�]�����*��������������P�������+�w������)��%�����9�[���!�U�����;�����B�����[���Z�x���-�c����������}�����������8�����%�����6��������R������"�����;�������0�����A�t����P�{�������B����2�[�������4�\��������!�M���!����+�S�s����R��*�>�l����3�������>�����J����^��Q�u[��a��*��!	X	�	�	7
w
�
�
:i�
J�
�
�
Q���-Ok��8W-\��C�=��7���A����&\��4z��s�>b���-DW��3��47c���Kl��# E } 4!�!�!J"�"�"n#�#�$�$%�%�%�%(&>&c&�&�&i'�'(H(�(�()()?)�)�)�)�)�)*4*k*�*�*�+�+(,�,�,�-�-E.�.�.�/70�0�0*1�1�1�12<2g2�2�2�23;3x3�34E4�4�4-5�5;6c6�6�6�6�6!7�7�7�78?8z8�89V9�9�9:�:�:I;�;�;=<h<�<�<�<6=r=�=�=�=>>$>T>�>�>.?|?�?	@V@�@�@%ASA�A BwB�B6C�CmD�D3ETE�E�EF_F�F�FG�G�GbH�H�HITI�I�I3J�J�J5KuK�K�K"LLL�L�LWM}M�M�M0NmN�N�NOXO�O�OP\P�P�PQNQ�Q�Q=R�RS]S�S�S
TFT�TU6U�UV4V�V�V�WsX�XuY_Z�Z�Z�Z[[6[�[�[�[�[\%\?\|\�\�\]D]�]�]�]6^|^�^/_O_�_8`k`�`aEa�a$b^bcDcnc�c�cdCd�d�d�d9ege�e�e:fnf�f�f�g�g�g$hth�h�h�h i|i�ij@jZj�j-kPk�k;l�lMm�m�m�mo�o�o'pbp�p-q�q�qVr�r�s�stQt�t�tugu�umv0w�w�xypz�z�z5{x{|.|�|�|	}4}n}�}
~N~�~�~��7���Ȁ�V����K�����G���5����t���ІK�e���؇�C����a����z�����K���Ӌc�����i�������5���ђ*�b���ϓ�I�t���C�|��V�ĖI�͗�B�t���ȘI���	�K�n�����S�����=���ޜ��!�Y�~��C��S�ğ=���4�O���١�_������N���ϣ�^��������D���ϥ<�]�����6�[���Ƨ�Z�����]���!�t���>�Ϋ��0�p�ɬ%�R�����L���J�����,���װ �e���̱�`��c�-�����#�U�������:�����m�ѷ�����q����q�Ⱥ!�����ջ�=���-���޽�s�۾��J���������$���a���d�#����_���F�u���������B��E�|���X�A�������7���������o�0�l��J������1���J���������)���3�����*��B�t�����?�n���8�����#������x���x�������8�~�G�����<����N�����Q��������2����������Y�������4��������C�z���'���"�w���B��:�=����#������6����n��U������������U�Q���A��0g�P�!Ry��e	�	�	
I
}
�
�
#Eu�@h��E
�
9��E��<k�h�Z��sR�.p���W���n���d�*a��@m����-]~��3gy��
  D | � � 1!f!�!"V"�"�"#/#]#c#�#$'$V$�$�$�$%P%�%�%9&v&'�'a(�(�(�(r)�)�)9*�*)+�+�+,B,p,�,�,�,-�-�-�.�.|/�/?00�0�01R1�1�1!2W2t2�203u3�3�3�3 4)444_4�4�4J5�5�5�5�5�5�5A6_6�6�6�67&7I7}7�7�748�8�8�819[9�9�9�9.:g:�:�:;|;�;�<'=�=�=;>?�?*@P@t@�@�@�@A7A�A�A�A�B(CJC�C�CDXD�D�DE1E`E�EF GyG|G�G%HyH�H�H�H'IvI�I
JRJ�J�J&KOK�K�K�KL+LLL�L�L�L0M�M�M�MN<N�N�N�N�N�NO O�O�P�P'QoQIRSnS�S�S�STJT�T�T�T�T!UBUzU�U�U�UV(VCVpV�V�V)W�W�W�W�WX<XdX�X�X�X	Y6YoY�Y�Y�YZ8ZkZ�Z�Z[%[9[�[�[�[\�\�\�\#]M]�]�]�]�]^>^c^�^�^�^,_�_�_`s`�`aMa�ab�bcEc�cGd�d�d�eqg�g�g�hi:iii�i�i"jpj�j�j&k�k�k�kjlm�m�mn`n�n5o�o�o�oppApbp�p�pq3qwq�qrRr�r�r�rNs�st�t�t9udu�u�u�uvcv�v�vAw�wxEx�x�x yvy�yz@zxz�z�z�{�|A}%~[~�~�~�~�~q|��;����T�ځR���؂�A�j���̈́�U���������W���ه�B�~���.�t����B�����E���ҋ�k�����J���������X�}���ݏ�l���ߐ+�J�q���+�����ܒ�0�O�����(�e����G��������7����*�j�����Ϙ�.�K�������8�j����D�l������.�^�����ݜ"�h�͝�
�%�P�r���ٞ<����5�j����O����4�{���ۣ6���Q�����"�H�t����Y�?����j��j���Ϋլ�r����9�h�����[���۰�H��	�k������!�@�����9�Y������d���=����*�F�������c���̻��P���q����D�k�����X�l�����Կ��.�_�������;�����,�T������v���7�t������@�����$�M�~����}����p������N�}�����L�����.����b�����������
�>�Y�������0����������=�p������0�c�����0�G�m������4�T�|������:�t����.�R�r��������,�U��������E�����]���	�&�X�������T���������N���������#��������;�c�|������9�`��������%�U�u������3�i��������H�~����E�s���	�+�R�s����[�q�����!�g���8�������(�A�t���������G������v�����V������@�l���H���n�����C�k�����.���-����U�������D�������,�Z������S�����[����-�\��
�,�������^���&�G����-�5�@�y������-�L��F�p��� ������
C��<�P��w��%��2m���s��	�	�	%
6
g
�
��n�f
�
�
#a��^��	G��)6|��j�����#b���	@e������*��;v��C�%]��?���K|��8f��?�� 9 j � � !e!�!"U"~"�"�"�">#g#�#�#�#:$�$�$%B%�%�%�%
&5&�&�&	','`'�'�'�'J({(�(�(�(,)a)3*|*+�+�+,/,O,�,&-�-�-A.�.�./G/x/�/0o0�0x12�23-3K33�3�3�3�3�3�3�3�3�34b4�4�4�4535n5�5�5�56�6�6\7�7�7�78Z8�8�89;9�9�9.:i:�:�:;x;�;t<P=�=>D>m>l?�?�?�?#@S@Y@{@�@�@!AbA�A�A�A�AB1BWBzB�B�B�B�B�B(CkC�C�C�C�CDWD�D�D�D�D)EWE�E�E�E�EFBFdF�F�F<G`G�G�GHbH�H�HII?I�I�I�I	JFJ�J�J�JK.KHK�K�K�KYLnL�L�L�L@MoM�M�M�M&NNN�N�N�N�N	O$O'O�O+P�P]Q~Q�Q�Q0R[R�R�R�RSmSpS�S�S*T_T�T�T�T�TU<UgU�U�U�U	V'VBV�V�V�VWOWRWuW�W�W�W�W�W>X[X�X�X1Y�Y�Y#ZGZgZjZmZpZ�Z�ZC[v[�[�["\;]�]^�^�_�`�`a)ava�a�a�ab>bYb�b�b�b,cYc�c�c�c$dld�d�d�d�d6e]e�efNfdf�f�f�f�f�fg6ghg�g�g�g?hqh�h�h!iGixi�i�i!jBjZjrj�j�jk/kvk�k�kl=ljl|l�l�l�l�lm>mbm�m�mn1ncn�n�n�no@oto�o�op�p�q�q+rPr{r�r�r�rPs�s�s tVtgt�t�tu?uhu�u�ubvbw�w�w�w9xrx�x�xy%yEyiy�y�y�y�yz/zzz�z�z�z{,{b{y{�{|g|�|}�}~P~�~h����F�����[���Ă��o����X�|�˅��C�Z�����&�����T���ň�D�l�Չ2�m�ފF���*�y�ˌ%�t���	�o�ˎR�������}���Z����:�ܓ��%�ŔI�k��������_���Ֆ�Y�������9����6�d�t�ޛ�	�,�q�����"�\�����&�i���ϟ�Y���P��7��������~�����k����ܨ+����'�a����v������f���;�v���ծ��T����l�°�s��	�v��8����N��f���������7�f������׷#�h����8�����!�z�ֻ(�g��f�ɽ��N�~�����}��3����{�����1��������2�k����b����@�����b���7�����.������`���<���K�����I�|���&�S�������4�������������&����h������F�z������R������7�����1�c����Q�~�����������t���U�g�����'������
�Q����H�����E����� �����1�i���;��������1�y������2������P���#�k���0�����/�l�����������\����j�������<�y������������9�a��������L������)�A�{�����7�k����E�o���!�a����(�P��������9�r������+�W������J��������&�N�p����a�����@\���q���� #&),/258;>ADGJMPSVY\_behknqtwz}�����������������"%(+.147:=@CFILORUX[^adgjmp����������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~���������������������!$'*-0369<?BEHKNQTWZ]`cfilorux{~�������������������������������������������										 	#	v	�	�	
G
o
�
�
�
�
�
�
�:���C
�
�
!����,f~��-R������-0369<?BEHKNQTWZ]`cfilorux{~������������EHKNQTWZ]`cfil����������������������!vy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������

"%(+.147:=@CFILORUX[^adgjmpsvy|����������������%(+�������������������������_�*}�$R��@o���> A V m � � !?!l!"5"k"�"�"	#?#x#$e$�$|%�%9&�&�&�&D'�'�'*(-(0(G(J(M(P(S(V(Y()X)�)*6*h*�*+=+a+z+�+�+t,�,�,�,�-K.�."/\/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/000	00000000!0$0'0*0-000306090<0?0B0E0H0K0N0Q0T0W0Z0]0`0c0f0i0l0o0r0u0x0{0~0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0111v1y1|11�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1222	22222222!2$2'2*2-202326292<2?2B2E2H2K2N2Q2T2W2Z2]2`2c2f2i2l2o2r2u2x2{2~2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�23333333333 3#3&3)3,3/3235383;3>3A3D3G3J3M3P3S3V3Y3\3_3b3e3h3k3n3q3t3w3z3}3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3O4�4�4A5�5�56N6�6�6�67d7�7�7�7�7
8R8�8�8�8939v9�9�9�9:/:S:�:�:�:Y;w;�;�;�;<f<�<�<)=H=�=�=.>�>
?O?j?�?�?�?�?E@~@�@,AZAwA�A6BqB�B�B�B�B�B�B�B�B�B�B�B�C�C�CJDMDrD�D�DE;EcE�E�GH,HqH�HI�J	K$KSKzK}K�K�KMaM�N�N�NOAOnO�O�O�O�O�O�O�O�O�O�O�OPP8P;PpPsP�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P#Q&Q)Q,Q/Q2Q5Q8Q;Q>QAQDQGQJQMQPQSQVQYQ\Q_Q�Q�Q�QRR�R�R�R�R�R�R�R�R�RSSSSSSSSS|SSBT�T�T�T�T�TUBUqU�U�U�U�U9VdV�V�VvWyW|WW�W�W�W�W�W�W�W�WX	XYYYJY�Y�Zg[�[�\G]�]�^__>_a`�`^a�a�a�a�b�b>cRcbc�c�c�c�cd`d�d�dee:e�eTf�f�f�fg5gdg�g�gh+h�hifihi�ijZj�jk|k�k�k�k�kllBl�l�l�l�m�mGnqn�n�n�noRo�o�o-php�pqTq�qr4rWrur�r�r�r#sVsts�s�s�s�stPtStVtYt\t_tbtetht�tu�u�u�uYv�v_w�w�w(xTx�x�x2y�y�yCz�z,{�{�{|l|�|�|]}0~W~�~�~�~^���<�_��%�ՁQ�ۂ��s��"�����ƅ�f����������ˇ��%�@�t�+�k�n���ŉՉ�!�V���؊������e�����+�~�ɍ&���Ǝ�A���.�x��7���ߑ�M�������V���8���	�V����8���ޗ�v���̘r�����A�������R����,���ۜ�<�t������7���Ȟ���9���ɟ�8�p�����Р�� �P���ء���ۣ.�����b�ȥh�ަ^���n�ƨT�©�q�����̪�C�]�����ث^���̬��?�U�í��C�x���p�&�O���۰��7�V����'�y����:����.������s��P��@�k����9�������-�M�n�й�l���
�h���λ
�Q�Ƽ����#�\���۾��������ؿ�k�� �X��������@�r���D�����(���������3�]�|�r���������E�v�y���f�0���,�����3����J���M���%���!�v���&�[���#�d������{���m���3�����,�n���������3���"�N�Q�t��������������������������������	�����j�����������v������)�,�O�p������B�������G�o���-���N���M�����B���2���N����h���
�c����T�����R�|��������������������������������������������������������������������������(�p�����,�l������v���H��������������;�Y����=�Y������s�-����W������}��.����6DGJM��cN��+il���?��	�	
U
�
H�	8�V
�
,^�7���V�f,�{��U�6��K��:�@��/p�I�f�` � 	!!R!�"{#$�$ %�%:&�&�&�& 'k'�'z(i)�*`+w,�,�-.�.-/u/�/�/�/0E0�0�011k1�1�1�1�12�2$4A4h4�4�4585s5�5"6~6�6@7�7�7�9:<�<;=i=�=[>�>�?=@�@�@/AzAB[B�BwCDkD�D�D�D�DdE�E�E�E�EXF�F�F�F�F�GtH	I7I�I�I�IGJ�J�JjK�KLzL�L6M�M3N�N�ORP*Q�QKR|R�RSSS�S�S�ST+T^T�T�T�T�UVbV�V�V&WLWkW�W�W�WEX�XSYZ�Z�]�_$`U`�`�`a|a�a)bbb�b�b�cCd�de%f�fgfgkg�g�gh�h�h#iGi�i�i4jnj�j�j�j
kIkik�k�k�k�k�kllsl!mum�m'n�n�o�p>q#s5sEs�s�s�s�st~t�teu�u>v�v�v<w�w�w<xx�xyhy�yYz�z�{4|�|�|}T}W}~�~w����(�ˁP���?����G�������ƅ��"�K�o�Æ��V����r�ڈ<�����^���
�+�M�X�k�����Ƌы�
�8�S���f�ҍ�O�o�ߎc���ɏ�������#�R�����Ւ���Q���ڔ�k���<������w�z�ט+����s��������hashchkisamchkNEDANe mogu da kreiram file '%-.200s' (errno: %d - %s)Ne mogu da kreiram tabelu '%-.200s' (errno: %d - %s)Ne mogu da kreiram bazu '%-.192s' (errno: %d - %s)Ne mogu da kreiram bazu '%-.192s'; baza već postoji.Ne mogu da izbrišem bazu '%-.192s'; baza ne postoji.Ne mogu da izbrišem bazu (ne mogu da izbrišem '%-.192s', errno: %d - %s)Ne mogu da izbrišem bazu (ne mogu da izbrišem direktorijum '%-.192s', errno: %d - %s)Greška pri brisanju '%-.192s' (errno: %d - %s)Ne mogu da pročitam slog iz sistemske tabeleNe mogu da dobijem stanje file-a '%-.200s' (errno: %d - %s)Ne mogu da dobijem trenutni direktorijum (errno: %d - %s)Ne mogu da zaključam file (errno: %d - %s)Ne mogu da otvorim file: '%-.200s' (errno: %d - %s)Ne mogu da pronađem file: '%-.200s' (errno: %d - %s)Ne mogu da pročitam direktorijum '%-.192s' (errno: %d - %s)Ne mogu da promenim direktorijum na '%-.192s' (errno: %d - %s)Slog je promenjen od zadnjeg čitanja tabele '%-.192s'Disk je pun (%s). Čekam nekoga da dođe i oslobodi nešto mesta... (errno: %d - %s)Ne mogu da pišem pošto postoji duplirani ključ u tabeli '%-.192s'Greška pri zatvaranju '%-.192s' (errno: %d - %s)Greška pri čitanju file-a '%-.200s' (errno: %d - %s)Greška pri promeni imena '%-.210s' na '%-.210s' (errno: %d - %s)Greška pri upisu '%-.200s' (errno: %d - %s)'%-.192s' je zaključan za upisSortiranje je prekinutoView '%-.192s' ne postoji za '%-.192s'Handler tabela je vratio grešku %d - '%-.192s'Handler tabela za '%-.192s' nema ovu opcijuNe mogu da pronađem slog u '%-.192s'Pogrešna informacija u file-u: '%-.200s'Pogrešan key file za tabelu: '%-.200s'; probajte da ga ispraviteZastareo key file za tabelu '%-.192s'; ispravite gaTabelu '%-.192s' je dozvoljeno samo čitatiNema memorije. Restartujte MySQL server i probajte ponovo (potrebno je %d byte-ova)Nema memorije za sortiranje. Povećajte veličinu sort buffer-a MySQL server-uNeočekivani kraj pri čitanju file-a '%-.192s' (errno: %d - %s)Previše konekcijaNema memorije; Proverite da li MySQL server ili neki drugi proces koristi svu slobodnu memoriju. (UNIX: Ako ne, probajte da upotrebite 'ulimit' komandu da biste dozvolili daemon-u da koristi više memorije ili probajte da dodate više swap memorije)Ne mogu da dobijem ime host-a za vašu IP adresuLoš početak komunikacije (handshake)Pristup je zabranjen korisniku '%-.48s'@'%-.64s' za bazu '%-.192s'Pristup je zabranjen korisniku '%-.48s'@'%-.64s' (koristi lozinku: '%s')Ni jedna baza nije selektovanaNepoznata komandaKolona '%-.192s' ne može biti NULLNepoznata baza '%-.192s'Tabela '%-.192s' već postojiNepoznata tabela '%-.129s'Kolona '%-.192s' u %-.192s nije jedinstvena u kontekstuGašenje servera je u tokuNepoznata kolona '%-.192s' u '%-.192s'Entitet '%-.192s' nije naveden u komandi 'GROUP BY'Ne mogu da grupišem po '%-.192s'Izraz ima 'SUM' agregatnu funkciju i kolone u isto vremeBroj kolona ne odgovara broju vrednostiIme '%-.100s' je predugačkoDuplirano ime kolone '%-.192s'Duplirano ime ključa '%-.192s'Dupliran unos '%-.192s' za ključ '%d'Pogrešan naziv kolone za kolonu '%-.192s''%s' u iskazu '%-.80s' na liniji %dUpit je bio prazanTabela ili alias nisu bili jedinstveni: '%-.192s'Loša default vrednost za '%-.192s'Definisani višestruki primarni ključeviNavedeno je previše ključeva. Maksimum %d ključeva je dozvoljenoNavedeno je previše delova ključa. Maksimum %d delova je dozvoljenoNavedeni ključ je predug. Maksimalna dužina ključa je %dKljučna kolona '%-.192s' ne postoji u tabeliBLOB kolona '%-.192s' ne može biti upotrebljena za navođenje ključa sa tipom tabele koji se trenutno koristiPreviše podataka za kolonu '%-.192s' (maksimum je %lu). Upotrebite BLOB poljePogrešna definicija tabele; U tabeli može postojati samo jedna 'AUTO' kolona i ona mora biti istovremeno definisana kao kolona ključa%s: Spreman za konekcije
Version: '%s'  socket: '%s'  port: %d%s: Normalno gašenje
%s: Dobio signal %d. Prekidam!
%s: Gašenje završeno
%s: Usiljeno gašenje thread-a %ld koji pripada korisniku: '%-.48s'
Ne mogu da kreiram IP socketTabela '%-.192s' nema isti indeks kao onaj upotrebljen pri komandi 'CREATE INDEX'. Napravite tabelu ponovoArgument separatora polja nije ono što se očekivalo. Proverite uputstvo MySQL server-aNe možete koristiti fiksnu veličinu sloga kada imate BLOB polja. Molim koristite 'fields terminated by' opciju.File '%-.128s' mora biti u direktorijumu gde su file-ovi baze i mora imati odgovarajuća prava pristupaFile '%-.200s' već postojiSlogova: %ld  Izbrisano: %ld  Preskočeno: %ld  Upozorenja: %ldSlogova: %ld  Duplikata: %ldPogrešan pod-ključ dela ključa. Upotrebljeni deo ključa nije string, upotrebljena dužina je veća od dela ključa ili handler tabela ne podržava jedinstvene pod-ključeveNe možete da izbrišete sve kolone pomoću komande 'ALTER TABLE'. Upotrebite komandu 'DROP TABLE' ako želite to da uraditeNe mogu da izvršim komandu drop 'DROP' na '%-.192s'. Proverite da li ta kolona (odnosno ključ) postojiSlogova: %ld  Duplikata: %ld  Upozorenja: %ldYou can't specify target table '%-.192s' for update in FROM clauseNepoznat thread identifikator: %luVi niste vlasnik thread-a %luNema upotrebljenih tabelaPreviše string-ova za kolonu '%-.192s' i komandu 'SET'Ne mogu da generišem jedinstveno ime log-file-a: '%-.200s.(1-999)'
Tabela '%-.192s' je zaključana READ lock-om; iz nje se može samo čitati ali u nju se ne može pisatiTabela '%-.192s' nije bila zaključana komandom 'LOCK TABLES'BLOB kolona '%-.192s' ne može imati default vrednostPogrešno ime baze '%-.100s'Pogrešno ime tabele '%-.100s'Komanda 'SELECT' će ispitati previše slogova i potrošiti previše vremena. Proverite vaš 'WHERE' filter i upotrebite 'SET OPTION SQL_BIG_SELECTS=1' ako želite baš ovakvu komanduNepoznata greškaNepoznata procedura '%-.192s'Pogrešan broj parametara za proceduru '%-.192s'Pogrešni parametri prosleđeni proceduri '%-.192s'Nepoznata tabela '%-.192s' u '%-.32s'Kolona '%-.192s' je navedena dva putaPogrešna upotreba 'GROUP' funkcijeTabela '%-.192s' koristi ekstenziju koje ne postoji u ovoj verziji MySQL-aTabela mora imati najmanje jednu kolonuTabela '%-.192s' je popunjena do krajaNepoznati karakter-set: '%-.64s'Previše tabela. MySQL može upotrebiti maksimum %d tabela pri 'JOIN' operacijiPreviše kolonaPrevelik slog. Maksimalna veličina sloga, ne računajući BLOB polja, je %ld. Trebali bi da promenite tip nekih polja u BLOBPrepisivanje thread stack-a:  Upotrebljeno: %ld od %ld stack memorije.  Upotrebite 'mysqld --thread_stack=#' da navedete veći stack ako je potrebnoUnakrsna zavisnost pronađena u komandi 'OUTER JOIN'. Istražite vaše 'ON' usloveTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNe mogu da učitam funkciju '%-.192s'Ne mogu da inicijalizujem funkciju '%-.192s'; %-.192sNe postoje dozvoljene putanje do share-ovane bibliotekeFunkcija '%-.192s' već postojiNe mogu da otvorim share-ovanu biblioteku '%-.192s' (errno: %d %-.128s)Ne mogu da pronadjem funkciju '%-.128s' u biblioteciFunkcija '%-.192s' nije definisanaHost '%-.255s' je blokiran zbog previše grešaka u konekciji.  Možete ga odblokirati pomoću komande 'mysqladmin flush-hosts'Host-u '%-.255s' nije dozvoljeno da se konektuje na ovaj MySQL serverVi koristite MySQL kao anonimni korisnik a anonimnim korisnicima nije dozvoljeno da menjaju lozinkeMorate imati privilegije da možete da update-ujete određene tabele ako želite da menjate lozinke za druge korisnikeNe mogu da pronađem odgovarajući slog u 'user' tabeliOdgovarajućih slogova: %ld  Promenjeno: %ld  Upozorenja: %ldNe mogu da kreiram novi thread (errno %d). Ako imate još slobodne memorije, trebali biste da pogledate u priručniku da li je ovo specifična greška vašeg operativnog sistemaBroj kolona ne odgovara broju vrednosti u slogu %ldNe mogu da ponovo otvorim tabelu '%-.192s'Pogrešna upotreba vrednosti NULLFunkcija regexp je vratila grešku '%-.64s'Upotreba agregatnih funkcija (MIN(),MAX(),COUNT()...) bez 'GROUP' kolona je pogrešna ako ne postoji 'GROUP BY' iskazNe postoji odobrenje za pristup korisniku '%-.48s' na host-u '%-.255s'%-.128s komanda zabranjena za korisnika '%-.48s'@'%-.64s' za tabelu '%-.64s'%-.16s komanda zabranjena za korisnika '%-.48s'@'%-.64s' za kolonu '%-.192s' iz tabele '%-.192s'Pogrešna 'GRANT' odnosno 'REVOKE' komanda. Molim Vas pogledajte u priručniku koje vrednosti mogu biti upotrebljene.Argument 'host' ili 'korisnik' prosleđen komandi 'GRANT' je predugačakTabela '%-.192s.%-.192s' ne postojiNe postoji odobrenje za pristup korisniku '%-.48s' na host-u '%-.255s' tabeli '%-.192s'Upotrebljena komanda nije dozvoljena sa ovom verzijom MySQL serveraImate grešku u vašoj SQL sintaksiDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in usePrekinuta konekcija broj %ld ka bazi: '%-.192s' korisnik je bio: '%-.48s' (%-.64s)Primio sam mrežni paket veći od definisane vrednosti 'max_allowed_packet'Greška pri čitanju podataka sa pipe-aGreška pri izvršavanju funkcije fcntl()Primio sam mrežne pakete van redaNe mogu da dekompresujem mrežne paketeGreška pri primanju mrežnih paketaVremenski limit za čitanje mrežnih paketa je istekaoGreška pri slanju mrežnih paketaVremenski limit za slanje mrežnih paketa je istekaoRezultujuči string je duži nego što to dozvoljava parametar servera 'max_allowed_packet'Iskorišteni tip tabele ne podržava kolone tipa 'BLOB' odnosno 'TEXT'Iskorišteni tip tabele ne podržava kolone tipa 'AUTO_INCREMENT'INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESPogrešno ime kolone '%-.100s'Handler tabele ne može da indeksira kolonu '%-.192s'Tabele iskorištene u 'MERGE' tabeli nisu definisane na isti načinZbog provere jedinstvenosti ne mogu da upišem podatke u tabelu '%-.192s'BLOB kolona '%-.192s' je upotrebljena u specifikaciji ključa bez navođenja dužine ključaSvi delovi primarnog ključa moraju biti različiti od NULL;  Ako Vam ipak treba NULL vrednost u ključu, upotrebite 'UNIQUE'Rezultat je sačinjen od više slogovaOvaj tip tabele zahteva da imate definisan primarni ključOva verzija MySQL servera nije kompajlirana sa podrškom za RAID uređajeVi koristite safe update mod servera, a probali ste da promenite podatke bez 'WHERE' komande koja koristi kolonu ključa. %sKljuč '%-.192s' ne postoji u tabeli '%-.192s'Ne mogu da otvorim tabeluHandler za ovu tabelu ne dozvoljava %s komandeNije Vam dozvoljeno da izvršite ovu komandu u transakcijiGreška %d - '%-.192s' za vreme izvršavanja komande 'COMMIT'Greška %d - '%-.192s' za vreme izvršavanja komande 'ROLLBACK'Greška %d za vreme izvršavanja komande 'FLUSH_LOGS'Greška %d za vreme izvršavanja komande 'CHECKPOINT'Prekinuta konekcija broj %u ka bazi: '%-.192s' korisnik je bio: '%-.48s' a host: '%-.255s' (%-.64s)Handler tabele ne podržava binarni dump tabeleBinarni log file zatvoren, ne mogu da izvršim komandu 'RESET MASTER'Izgradnja indeksa dump-ovane tabele '%-.192s' nije uspelaGreška iz glavnog servera '%-.64s' u klasteruGreška u primanju mrežnih paketa sa glavnog servera u klasteruGreška u slanju mrežnih paketa na glavni server u klasteruNe mogu da pronađem 'FULLTEXT' indeks koli odgovara listi kolonaNe mogu da izvršim datu komandu zbog toga što su tabele zaključane ili je transakcija u tokuNepoznata sistemska promenljiva '%-.64s'Tabela '%-.192s' je markirana kao oštećena i trebala bi biti popravljenaTabela '%-.192s' je markirana kao oštećena, a zadnja (automatska?) popravka je bila neuspelaUpozorenje: Neke izmenjene tabele ne podržavaju komandu 'ROLLBACK'Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againOva operacija ne može biti izvršena dok je aktivan podređeni server. Zadajte prvo komandu 'STOP SLAVE' da zaustavite podređeni server.Ova operacija zahteva da je aktivan podređeni server. Konfigurišite prvo podređeni server i onda izvršite komandu 'START SLAVE'Server nije konfigurisan kao podređeni server, ispravite konfiguracioni file ili na njemu izvršite komandu 'CHANGE MASTER TO'Nisam mogao da inicijalizujem informacionu strukturu glavnog servera, proverite da li imam privilegije potrebne za pristup file-u 'master.info'Nisam mogao da startujem thread za podređeni server, proverite sistemske resurseKorisnik %-.64s već ima više aktivnih konekcija nego što je to određeno 'max_user_connections' promenljivomMožete upotrebiti samo konstantan iskaz sa komandom 'SET'Vremenski limit za zaključavanje tabele je istekao; Probajte da ponovo startujete transakcijuBroj totalnih zaključavanja tabele premašuje veličinu tabele zaključavanjaZaključavanja izmena ne mogu biti realizovana sve dok traje 'READ UNCOMMITTED' transakcijaKomanda 'DROP DATABASE' nije dozvoljena dok thread globalno zaključava čitanje podatakaKomanda 'CREATE DATABASE' nije dozvoljena dok thread globalno zaključava čitanje podatakaPogrešni argumenti prosleđeni na %sKorisniku '%-.48s'@'%-.64s' nije dozvoljeno da kreira nove korisnikePogrešna definicija tabele; sve 'MERGE' tabele moraju biti u istoj bazi podatakaUnakrsno zaključavanje pronađeno kada sam pokušao da dobijem pravo na zaključavanje; Probajte da restartujete transakcijuUpotrebljeni tip tabele ne podržava 'FULLTEXT' indekseNe mogu da dodam proveru spoljnog ključaCannot add or update a child row: a foreign key constraint failsNe mogu da izbrišem roditeljski slog: provera spoljnog ključa je neuspelaError connecting to source: %-.128sError running query on source: %-.128sGreška pri izvršavanju komande %s: %-.128sPogrešna upotreba %s i %sUpotrebljene 'SELECT' komande adresiraju različit broj kolonaNe mogu da izvršim upit zbog toga što imate zaključavanja čitanja podataka u konfliktuMešanje tabela koje podržavaju transakcije i onih koje ne podržavaju transakcije je isključenoOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesPromenljiva '%-.192s' je %s promenljivaIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDupliran unos '%-.64s' za ključ '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTPristup je zabranjen korisniku '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setPartition '%-.64s' ne postojiFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDupliran unos za ključ '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�������slovak/errmsg.sysnu�[��������	W��P��3e��O��O��Q��Ap���6k��g���B	�	�	�	�	�	
6
\
�
�
�
�
&P����?b���*
w
�
�
*u�I`��
\�!f��8��'Gi��M���z����$Gj���Vk�c�#J~��Ns�u�
<��.M�F��)O���C c � � !!4!]!�!�!�!"?"u"�"#(#\#�#�#$t$�$�$�$c%�%�%�%
&4&]&|&�&�&.'Q'�'�'�'�'(p(�(�()T)�)+*}*�*J+�+�+�+4,j,�,�,8-R-�-�-.I.k.�.�./</e/�/�/0B0f0�0�0H1�1�1�1&2R2t2�2�273[3�3�3�3474b4�4�4�4�4"5c5�5�5)6D6e6�6�6M7h7�7�78P8~8�8�89?9�9�9�9J:f:;�;�;><�<:=Y=z=�=�=>u>�>�>?g?�?�?@�@�@A&AOAxA�A�AB?BtB�B�B�B�B�B�BC>CzC�C�C(D�D�D�DE4EUEwE�E�E�E�E�EFGF_FvF�F�F�F�FGLGyG�G�G�G'HaH�H�H"I>I`I�I�I�IJ�J�J3K�K�K#L:LQL�L�L�L�LMLM|M�M�MN?NuN�N�N�N�NOFOeO�O�O�O
P?PlP�P�P�PQFQlQ�Q�QRHRgR~R�RSKS�S�S2TgT�T�T�TUWU�U�U�U!V�V�V�V�WxXY�Y�Y�YEZ~Z�Z�ZM[�[�[-\�\�\:]x]�]^B^_^�^�^�^s_�_i`�`�`Ka�a�abhb�b�bSc�c�cod�d�dece�e�e�e&fPf�f�f�f�fgdg�g�gh]h�hi_i�i�ijRj�j�j<kmk�k�k@lll�l�lmYm�m�mnTn�n�no~o�o�o/pUp�p�p q�q�qr(rQr�r�r�r's�s�stPtot�t�t�t�tuDu�u�u�u0vjv�v
wGw_ww�w�w�w!x<x\x�x�xyFyby�y�yzTzyz�zx{�{$|v|�|�|}}E}^}�}~3~r~�~�~�~T���=�ـ�Z���Ձ�F�ÂG�{����!�<�X�l�������W���ą�:�j���Ȇ%�N�}���߇(�S�����͈�#�a�ω��c���ӊ�9�l�ً�����	��9�o�����܌�0�[�|�����!��Ў��1�[�x����5�|���@����@��e��n����7�����c����V���˙��1�h����>�����0�Q���ӜE�~�����Q����+�g����&����&�i���Ң��ף����_�4��R���éê�C����]�Ŭ�;�s���ܭ��,����Y�������M��&�S������$�w���2���*�C�����'�����3�}�̷;���ø,�y������a��L����[�����R���k���ɿ�����<�q���s�����)�g��������9�����#�v���������
�*�\�o�������,�����T�����%�P�����-����Q����6�P�2�q�����h�����m�������%�X�z����L�|����������r����>����8����������%�����>���=�[����F�����k�o���`�u���{����������������r������5��������}�p��i������v���$�W����3�^�������%�r����>�o��������?�d��������0���������6�V�w���5���
�!�O�����h����!����-�f��A�~���4���X��>����D�����
t�;}�Z��L��-�e�4r���2Nm��	:	�	
?
�
�
&� ��
e
�
�
$q��u�	?��]���V��!Ei��':n���Fo��.Os�(`��-j�Q�u�����!Fg�L � � +!�!�!�!"""g"�"�"�"�"�"#N#r#�#c$�$%�%�%j&�&('w'�'o()h)�)
*s*�*�*�*+J+u+�+�+�+,[,�,�,(-h-�-.�./F/o/�/�/�/0f0�0�0�0"1]1�1�192�2�23|3�3,4q4�4 5K55�5�56U6�6�6�6�67777x7�78_8�8�899h9�9:6:�:;Z;�;<�<P=�=>7>n>�>�>B?z?�?�?s@�@EAqA�A�A7B�B�BCqC�CDXD�D�DE/E�E�E:F`F�F�FGPG�G�G�G;H�H�HI?IvI�I�I1J�J�J K�KL@LsL�L�L)M�M�MNzN�NOvO�O�PVQ�QXRBSvS�S�S�STToT�T�T�T�TU"U_U�U�U�U'VrV�V�VW_W�WX2X�XYNY{Y�Y(ZdZ[A[�['\Q\�\�\�\&]�]�]�]^J^�^�^_Q__�_t`�`�`aWa�a�a�ab_b�b�b#c=c�cd3drde�e0fmf�f�f�gqh�h
iEi�ij�j�j9k�kdl�l�l4m�m�m�mJn�nPop�p�q�qSs�s�st[t�tu|u�u�uvQv�v�v1w|w�w�x�xyfy�y�y9znz�z.{�{y|�|*}�}~�~�~W|�.�H������&�y��D�����]���׃��.�q���F�����L�d���݊�h���
�E�������,�W�ٍ&�_�Ŏ9���,����%�W�k���,�|��.�Q���ܓ6��ޔ �e�����<�a���і&�ŗ6��� �m��2�j�����B�}�؛��1�������A�q������'�n����@������>������=���ء@����W�У�!���ؤ�S����5���Φ�/���-�|�ި�d����H������C�ЫF����٭�8�m�������ٯP���ٰ����T����T����j�x����� ����v�����V�����-�����b���ٻ�޼D���G������B���)�X�����h���%���(�_���;�$��������c�������R��O���-�c������i�-�����������������h�
���%�W�����"�Q���������|�����[���[���j������a�*�g��������1�q���4���p���o����m���������<���f����m�������&�]���
����Z���%���� �f����b���h������Q���8����r�����8����4������$�m���J�����3�5\��H��,`��(X�#Kk�(�u�(s�	N	�	�	K
�
=���V�5
�
�Sb����:c���Q����G��
Db��#P|����@a���J\����'_x�I��9c��@F��
9g���3~�Y�} D!k!�!�!U"�"�"#�#$�$�$�$%%S%m%�%�%�%�&�&w'�'_(�(")b)�)�)*5*g*�*+:+W+�+,X,�,�,�,---B-x-�--.�.�.�.�.�.�.$/B/�/�/�/�/	0,0`0�0�01q1�1�12>2w2�2�23J3}3�3�3_4x4�5
6�6�67�7�8
939W9}9�9�9�9:z:�:�:�;<-<�<�<�<;=e=�=�=>C>x>?@\@_@�@A\A�A�A�A
BYB�B�B5CzC�C	D2DfD�D�D�DE/E�E�E�EF~F�F�F�FGpG�G�G�G�G�GH�H�I�I
JRJ,KLQLwL�L�L�L-McM�M�M�MN%N]N�N�N�N�NO&OSO�O�OPiP�P�P�P�PQGQsQ�Q�Q�QRRR}R�R�R�RSNS�S�S�STTfT�T�T�TnU�U�UV0VsV�V�V�V�V!WFWuW�W�WXkX�X�XVY�Y�Y0ZxZ�Zf[�[(\�\*]�]�]r^T`�`�`�a�abLb�b�bcSc�c�c	dtd�d�dMe�e�f�f�fCg�ghih�h�h�h�h$iEini�i�ijZj�j�j5klk�k�k1l�l�ldm�mnGnyn�n�n�nFo�o�o$pkp�p(q�q�qrYr�r�r#s[s�s�s�tzu$vw>wsw�w�w�w�wTx_xbx�x�xy�y�y7z�z5{�{�{�{$|M}r}�}�}8~i~u~�~�:�s����%�a�ہ�W���Ă%���ȃ��(�c�����N���م-�b��������;�`�w�����O����-�T�Պ���i�������2���܌�H����*�d����l����̐
�M�u�����Ց�.�q���ʒ���M���Γ'�O�v�����A�r������K���Ȗ��3�U������ژ���M����2�z�̛�^��������4�p�Ҟϟ�+�W�v�à<�"���ϢM�ˣM�x������U�����K�u���>�������+�֪�N�o���ɫ�#������<������G��� �����
�)�w�����F�v����3���T����'�N�x�ݷ;�O�c�����߸�B�o���ʹ���y���7�x����Y����W���Ƚ��#�n����0�a�����`����S�����1�`�����/�e��������E������������!�<�q������j���o����� �S�r������F������*�P���w����7�_��������W������5�U����������8�p������(�q���@�����	�;�p�����7�f�������1�c����������������F�_��������C�k��������8�X��������L�q�������+�a�����(�V������5�V�w���>�T�j����J�����������$�W�x�������*�������Y�����9�h�����#�O���+���Q�����&�N�������������8�������'�v������=�t�����6�o�����>������?������e�������A���	�*���������#�\�t�����/���)�S����d�����&�n����3�����Z�����r���Pu��V�v��Jqi�Q�I}�D��A���*	g	�

_
y
�
M��t��
E
m
�
�
�
#Hs�����
w���Y��&�@��"e���._��I��"f��M}��H��8a���!Jr��q��%}������ C m � � -!^!�!�!�!"D"#_#�#z$�$�$%2%�%	&�&�&$''�'(*([(�(�(R)�)[*�*�+�+,.,b,f,j,n,r,v,z,�,�,�,�,E-�-�-�-�-.Q.k.~.�./�/�/?0�0�0�0�0=1�1�1�12o2�23L3�3�34[4�4W536�6�6'7P7O8�8�8�8969<9^9�9�9:E:d:�:�:�:�:;:;];l;;�;�;�;<N<q<�<�<�<=:=m=�=�=�=>:>{>�>�>�>�>%?G?r?�?@C@s@�@�@EAkA�A�A�A"BuB�B�B�B)ChC�C�C�CD+D�D�D�D<EQE}E�E�E#FRF�F�F�F	G1GjG�G�G�G�GH
H�HI�I@JaJ�J�JK>KmK�K�K�KPLSL�L�L
MBMmM�M�M�M�MNJNcN�N�N�N
O%OjO�O�O�O2P5PXPwPP�P�P�P!Q>Q�Q�QR�R�RS*SJSMSPSSSzS�S&TYT�T�TUV�V�V�WiX{Y�Y�YZYZqZ�Z�Z�Z![<[z[�[�[\<\i\�\�\]O]p]�]�]�]^@^�^_1_G_f_�_�_�_�_�_`K`}`�`�`"aTa�a�ab*b[b�b�bc%c=cUc�c�c�cdYd�d�d�d eMe_eze�e�e�e�e!fEfmf�f�fgFgsg�g�g�g#hWh�h�h�hqioj�jk3k^k�k�k�k3lll�lm9mJm�m�mn"nKn|n�nEoEp�p�p�pqUq�q�q�qr(rLrer�r�r�r�rs]s�s�s�s�stEt\t�t�tJu�u�ufv�v3wcwKx�x�x�y)zwz�z>{u{�{�{�|R}�}�};~_~�~�~&=o��	���ƀ��7�n�����'�O����P���)���
�\����W����R���5�����t��`���=���׋�������,�N�t���؎��B�������<�y���ސ�����G�W���b���T�q�ږ�?���ؗ	�L������<���3�ǚ������Ӝ�a�םv�ҞN���������Ԣ
�D�y�ˣY�٤h��I����Y����ܧ7�����O����V�Ū�Y�ʫ�y��1���I�e�����î���I����x����K�x�ʱ�u�f��]����J�͵I���m�1�a���̸�`�ҹ����^���λ�}����׽�N����E����#�k��E����n����d�����C����m�.�����,�_���	�6�c���}��d�����x�����	�����K�������)�]�������5�k�����������F����4�a�����z�����W���8�J����
�r�������4�����+�����(������f����L������������\��������b�����3����N�p�������O������������?�����M�v������\�s������������D�c������/�d������$�^�s������N�����(�R������D������3�e��������U��������:�h������-�f������	�1�S�p���D�~��������#�?�c������T�u������������������	��������!�$�'�*�-�0�3�6�9�<�?�B�E�H�K�N�Q�T�W�Z�]�`�c�f�i�l�o�r�u�x�{�~��������������������������� �#�&�)�,�/�2�5�8�;�>�A�D�G�J�M�P�S�}����������������������������������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|��������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������Y���*R��������p��&y�v�q��	I	a	�
�5i�����

"
%
(
+
.
1
4
7
:
=
@
C
F
I
L
O
R
U
X
[
^
a
d
g
j
m
p
s
v
y
|

�
�
(+.147:=@CFILOtwz}������������������Y\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|������������������������������������������	!$'*-0369<?BEHKNQTWZ]`cf���������������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������������������������Bt
`�5h�#R���!$9P~��"O�N{��"[�Hx_����' w � 
!!!*!-!0!3!6!9!<!�!;"�"�"#K#�#�# $D$]$�$�$W%o%�%�%�&.'k'(?(h(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�(�()))
)
)))))))")%)()+).)1)4)7):)=)@)C)F)I)L)O)R)U)X)[)^)a)d)g)j)m)p)s)v)y)|))�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)Y*\*_*b*e*h*k*n*q*t*w*z*}*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++
+
+++++++"+%+(+++.+1+4+7+:+=+@+C+F+I+L+O+R+U+X+[+^+a+d+g+j+m+p+s+v+y+|++�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,	,,,,,,,,!,$,',*,-,0,3,6,9,<,?,B,E,H,K,N,Q,T,W,Z,],`,c,f,i,l,o,r,u,x,{,~,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,2-�-�-$.t.�.�.1/o/�/�/0G0f00�0�0�051t1�1�1�12Y2u2�2�2�2363w3�3�3<4Z4u4�4�4�4I5�5�56+6�6�67q7�728M8}8�8�8�8(9a9�9:=:Z:{:;T;�;�;�;�;�;�;�;�;�;�;�;e<�<�<-=0=U=�=�=�=>F>�>m@�@ATA�AbBjC�CD6D]D`DcD�D�EDFzG�G�G�G$HQHlHoHrHuHxH{H~H�H�H�H�H�H�HIISIVII�I�I�I�I�I�I�I�I�I�I�I�I�I�I�I�IJ	JJJJJJJJ!J$J'J*J-J0J3J6J9J<J?JBJ�J�J�J�JK�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K�K_LbL%M�M�M�M�M�M�M%NTNtN�N�N�NOGO�O�OYP\P_PbPePhPkPnPqPtPwP�P�P�P�Q�Q�Q-R�RgSJT�T�U*V�V�W�W�W!XDY�YAZfZ�Z�Z�[�[!\5\E\l\�\�\�\�\C]�]�]�]�]^�^7_x_�_�_�_`G`v`�`�`ada�aIbKb�b�b=c�c�c_dodrd�d�d�de%eue�e�ewf�f*gTgjg�g�g�g5hih�hiKizi�i7j�j�jk:kXkrkuk�kl9lWl~l�l�l�l�l3m6m9m<m?mBmEmHmKm�mncn�n�n<o�oBp�p�pq7qdq�qrqr�r&s�st�t�t�tOu�u�u@vw:w{w�w�wAxrx�x�xyBy�yz�z4{�{b|�|V}�}~x~�~�~�~I|����e���ǀ��#�W��N�Q�p�����Ȃ�9�p����q���̈́H�b���Յ�a���	�o����$����[�É�����0�x��c�Ό9�������9���ˏ�{����Y�����U���ڒ$�d���ړ5�����ה�k������W�{���������Ǘܗ�l������S�������ۙ�3�i�����������؝E���K���A�Ѡ�Q���7�����T�n�����ţ&�@�i�����A������"�8����&�[�ȧ�S�	�2�����ݩ�9�y�Ū
�\���ë�w�̬�j�����V�ή3��#�N�z�ϰ�g���̱��0�Q����O����K�w����4�����Ķ��?�j��������������N����;���������#�U���'������c�����ѿ�@�_�U�����������(�Y�\���I����������o���-���0������Y���	�>����G�������^���P���������Q�l��������|��1�4�W���������������������������������������������M�q��������������Y���������2�S�|�����%���������*�R������1���0�v���%�~����1�����K�����F�����7�����5�_�b�e�h�k�n�q�t�w�z�}��������������������������������������������������������S������O�n�����Y���+�v�����l�������<����� �<�n�����V������:�������`��������'�*�-�0��f��F�1����LO~��"�����8��+���9�Ag���	9

I�^
�
i8����.���#��S�,�I�C���5�^���n�� N | ]!L"k#C$Z%�%e&�&�'(X(�(�(�(�(()f)�)*N*v*�*�*�*�*�+-$-K-v-�-�-.V.�./a/�/#0�0�0�2�2�4�56L6�6>7v7�8 9|9�9:]:;>;p;Z<�<N=v=�=�=�=G>|>�>�>�>;?w?�?�?�?�@WA�ABtB�B�B*CfC�CMD�D�D]E�EFpFG�GxH5I
J�J.K_K�K�K6LfL�L�L�LMAMdM�M�M�N�NEO�O�O	P/PNP�P�P�P(QgQ6R�R�SvV�XY8YkY�Y�Y_Z�Z[E[u[�[�\&]�]b^_�_�_I`N`�`�`�`�a�ab*bzb�bcQcrc�c�c�c,dLdcd�d�d�d�d�d�dVefXf�f
gyg�h�i!jll(lpl�l�l�l�lam�mHn�n!o|o�oplp�pqbq�q�qKr}r<sis�tu�u�u�u7v:v�vyw�wZx�xiy�yz�z3{s{"|�|�|*}�}�}~v~�~�~.R���9����U������A�����0�;�N�f�������ʄ��6���I����2�R�F�{����m�����5�d��������4������N���������Z�]����b���V���ܔx��hashchkisamchkNIEÁnoNemôžem vytvoriť súbor '%-.200s' (chybový kód: %d - %s)Nemôžem vytvoriť tabuľku '%-.200s' (chybový kód: %d - %s)Nemôžem vytvoriť databázu '%-.192s' (chybový kód: %d - %s)Nemôžem vytvoriť databázu '%-.192s'; databáza existujeNemôžem zmazať databázu '%-.192s'; databáza neexistujeChyba pri mazaní databázy (nemôžem zmazať '%-.192s', chybový kód: %d - %s)Chyba pri mazaní databázy (nemôžem vymazať adresár '%-.192s', chybový kód: %d - %s)Chyba pri mazaní '%-.192s' (chybový kód: %d - %s)Nemôžem čítať záznam v systémovej tabuľkeNemôžem zistiť stav '%-.200s' (chybový kód: %d - %s)Nemôžem zistiť pracovný adresár (chybový kód: %d - %s)Nemôžem zamknúť súbor (chybový kód: %d - %s)Nemôžem otvoriť súbor: '%-.200s' (chybový kód: %d - %s)Nemôžem nájsť súbor: '%-.200s' (chybový kód: %d - %s)Nemôžem čítať adresár '%-.192s' (chybový kód: %d - %s)Nemôžem vojsť do adresára '%-.192s' (chybový kód: %d - %s)Záznam bol zmenený od posledného čítania v tabuľke '%-.192s'Disk je plný (%s), čakám na uvoľnenie miesta... (chybový kód: %d - %s)Nemôžem zapísať, duplikát kľúča v tabuľke '%-.192s'Chyba pri zatváraní '%-.192s' (chybový kód: %d - %s)Chyba pri čítaní súboru '%-.200s' (chybový kód: %d - %s)Chyba pri premenovávaní '%-.210s' na '%-.210s' (chybový kód: %d - %s)Chyba pri zápise do súboru '%-.200s' (chybový kód: %d - %s)'%-.192s' je zamknutý proti zmenámTriedenie prerušenéPohľad '%-.192s' neexistuje pre '%-.192s'Obsluha tabuľky vrátila chybu %d - '%-.192s'Obsluha tabuľky '%-.192s' nemá tento parameterNemôžem nájsť záznam v '%-.192s'Nesprávna informácia v súbore: '%-.200s'Nesprávny kľúč pre tabuľku '%-.200s'; pokúste sa ho opraviťStarý kľúčový súbor pre '%-.192s'; opravte ho!'%-.192s' is čítať onlyMálo pamäti. Reštartujte daemona a skúste znova (je potrebných %d bytov)Málo pamäti pre triedenie, zvýšte veľkosť triediaceho bufferuNeočakávaný koniec súboru pri čítaní '%-.192s' (chybový kód: %d - %s)Príliš mnoho spojeníMálo miesta-pamäti pre vláknoNemôžem zistiť meno hostiteľa pre vašu adresuChyba pri nadväzovaní spojeniaZakázaný prístup pre užívateľa: '%-.48s'@'%-.64s' k databázi '%-.192s'Zakázaný prístup pre užívateľa: '%-.48s'@'%-.64s' (použitie hesla: %s)Nebola vybraná databázaNeznámy príkazPole '%-.192s' nemôže byť nullNeznáma databáza '%-.192s'Tabuľka '%-.192s' už existujeNeznáma tabuľka '%-.129s'Pole: '%-.192s' v %-.192s je nejasnéPrebieha ukončovanie práce serveraNeznáme pole '%-.192s' v '%-.192s'Použité '%-.192s' nebolo v 'group by'Nemôžem použiť 'group' na '%-.192s'Príkaz obsahuje zároveň funkciu 'sum' a poľaPočet polí nezodpovedá zadanej hodnoteMeno identifikátora '%-.100s' je príliš dlhéOpakované meno poľa '%-.192s'Opakované meno kľúča '%-.192s'Opakovaný kľúč '%-.192s' (číslo kľúča %d)Chyba v špecifikácii poľa '%-.192s'%s blízko '%-.80s' na riadku %dVýsledok požiadavky bol prázdnyNie jednoznačná tabuľka/alias: '%-.192s'Chybná implicitná hodnota pre '%-.192s'Zadefinovaných viac primárnych kľúčovZadaných ríliš veľa kľúčov. Najviac %d kľúčov je povolenýchZadaných ríliš veľa častí kľúčov. Je povolených najviac %d častíZadaný kľúč je príliš dlhý, najväčšia dĺžka kľúča je %dKľúčový stĺpec '%-.192s' v tabuľke neexistujeBlob pole '%-.192s' nemôže byť použité ako kľúčPríliš veľká dĺžka pre pole '%-.192s' (maximum = %lu). Použite BLOBMôžete mať iba jedno AUTO pole a to musí byť definované ako kľúč%s: pripravený na spojenie
Version: '%s'  socket: '%s'  port: %d%s: normálne ukončenie
%s: prijatý signál %d, ukončenie (Abort)!
%s: práca ukončená
%s: násilné ukončenie vlákna %ld užívateľa '%-.48s'
Nemôžem vytvoriť IP socketTabuľka '%-.192s' nemá index zodpovedajúci CREATE INDEX. Vytvorte tabulku znovaArgument oddeľovač polí nezodpovedá požiadavkám. Skontrolujte v manuáliNie je možné použiť fixnú dĺžku s BLOBom. Použite 'fields terminated by'.Súbor '%-.128s' musí byť v adresári databázy, alebo čitateľný pre všetkýchSúbor '%-.200s' už existujeZáznamov: %ld  Zmazaných: %ld  Preskočených: %ld  Varovania: %ldZáznamov: %ld  Opakovaných: %ldIncorrect prefix key; the used key part isn't a string or the used length is longer than the key partOne nemôžem zmazať all fields with ALTER TABLE; use DROP TABLE insteadNemôžem zrušiť (DROP) '%-.192s'. Skontrolujte, či neexistujú záznamy/kľúčeZáznamov: %ld  Opakovaných: %ld  Varovania: %ldYou can't specify target table '%-.192s' for update in FROM clauseNeznáma identifikácia vlákna: %luNie ste vlastníkom vlákna %luNie je použitá žiadna tabuľkaPríliš mnoho reťazcov pre pole %-.192s a SETNemôžem vytvoriť unikátne meno log-súboru %-.200s.(1-999)
Tabuľka '%-.192s' bola zamknutá s READ a nemôže byť zmenenáTabuľka '%-.192s' nebola zamknutá s LOCK TABLESPole BLOB '%-.192s' nemôže mať implicitnú hodnotuNeprípustné meno databázy '%-.100s'Neprípustné meno tabuľky '%-.100s'Zadaná požiadavka SELECT by prechádzala príliš mnoho záznamov a trvala by príliš dlho. Skontrolujte tvar WHERE a ak je v poriadku, použite SET SQL_BIG_SELECTS=1Neznámá chybaNeznámá procedúra '%-.192s'Chybný počet parametrov procedúry '%-.192s'Chybné parametre procedúry '%-.192s'Neznáma tabuľka '%-.192s' v %-.32sPole '%-.192s' je zadané dvakrátNesprávne použitie funkcie GROUPTabuľka '%-.192s' používa rozšírenie, ktoré v tejto verzii MySQL nie jeTabuľka musí mať aspoň 1 poleTabuľka '%-.192s' je plnáNeznáma znaková sada: '%-.64s'Príliš mnoho tabuliek. MySQL môže použiť len %d v JOIN-ePríliš mnoho políRiadok je príliš veľký. Maximálna veľkosť riadku, okrem 'BLOB', je %ld. Musíte zmeniť niektoré položky na BLOBPretečenie zásobníku vlákna:  použité: %ld z %ld.  Použite 'mysqld --thread_stack=#' k zadaniu väčšieho zásobníkaV OUTER JOIN bol nájdený krížový odkaz.  Skontrolujte podmienky ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNemôžem načítať funkciu '%-.192s'Nemôžem inicializovať funkciu '%-.192s'; %-.192sNeprípustné žiadne cesty k zdieľanej knižniciFunkcia '%-.192s' už existujeNemôžem otvoriť zdieľanú knižnicu '%-.192s' (chybový kód: %d %-.128s)Nemôžem nájsť funkciu '%-.128s' v knižniciFunkcia '%-.192s' nie je definovanáHost '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'Host '%-.255s' is not allowed to connect to this MySQL serverYou are using MySQL as an anonymous user and anonymous users are not allowed to change passwordsYou must have privileges to update tables in the mysql database to be able to change passwords for othersCan't find any matching row in the user tableRows matched: %ld  Changed: %ld  Warnings: %ldCan't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bugColumn count doesn't match value count at row %ldCan't reopen table: '%-.192sInvalid use of NULL valueGot error '%-.64s' from regexpMixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clauseThere is no such grant defined for user '%-.48s' on host '%-.255s'%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used.The host or user argument to GRANT is too longTable '%-.192s.%-.192s' doesn't existThere is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'The used command is not allowed with this MySQL versionSomething is wrong in your syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)Got a packet bigger than 'max_allowed_packet' bytesGot a read error from the connection pipeGot an error from fcntl()Got packets out of orderCouldn't uncompress communication packetGot an error reading communication packetsGot timeout reading communication packetsGot an error writing communication packetsGot timeout writing communication packetsResult string is longer than 'max_allowed_packet' bytesThe used table type doesn't support BLOB/TEXT columnsThe used table type doesn't support AUTO_INCREMENT columnsINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrect column name '%-.100s'The used table handler can't index column '%-.192s'All tables in the MERGE table are not defined identicallyCan't write, because of unique constraint, to table '%-.192s'BLOB column '%-.192s' used in key specification without a key lengthAll parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE insteadResult consisted of more than one rowThis table type requires a primary keyThis version of MySQL is not compiled with RAID supportYou are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %sKey '%-.192s' doesn't exist in table '%-.192s'Can't open tableThe handler for the table doesn't support %sYou are not allowed to execute this command in a transactionGot error %d - '%-.192s' during COMMITGot error %d - '%-.192s' during ROLLBACKGot error %d during FLUSH_LOGSGot error %d during CHECKPOINTAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)The storage engine for the table does not support binary table dumpBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Error from source: '%-.64s'Net error reading from sourceNet error writing to sourceCan't find FULLTEXT index matching the column listCan't execute the given command because you have active locked tables or an active transactionUnknown system variable '%-.64s'Table '%-.192s' is marked as crashed and should be repairedTable '%-.192s' is marked as crashed and last (automatic?) repair failedSome non-transactional changed tables couldn't be rolled backMulti-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try againThis operation cannot be performed with a running replica; run STOP REPLICA firstThis operation requires a running replica; configure replica and do START REPLICAThe server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logCould not create replica thread; check system resourcesUser %-.64s already has more than 'max_user_connections' active connectionsYou may only use constant expressions with SETLock wait timeout exceeded; try restarting transactionThe total number of locks exceeds the lock table sizeUpdate locks cannot be acquired during a READ UNCOMMITTED transactionDROP DATABASE not allowed while thread is holding global read lockCREATE DATABASE not allowed while thread is holding global read lockIncorrect arguments to %s'%-.48s'@'%-.64s' is not allowed to create new usersIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionThe used table type doesn't support FULLTEXT indexesCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sIncorrect usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied; you need (at least one of) the %-.128s privilege(s) for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchOperand should contain %d column(s)Subquery returns more than 1 rowUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existCyclic reference on subqueriesConverting column '%s' from %s to %sReference '%-.64s' not supported (%s)Every derived table must have its own aliasSelect %u was reduced during optimizationTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Query cache failed to set size %lu; new query cache size is %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadThe target table %-.100s of the %s is not updatableThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionOpakovaný kľúč '%-.64s' (číslo kľúča '%-.385s')Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTZakázaný prístup pre užívateľa: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setPartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionOpakovaný kľúč (číslo kľúča '%-.192s')Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\2�&��spanish/errmsg.sysnu�[��������Hx��9��Az��	@z��P���/g���?k��6��-Cl��	C	a	u	�	�	�	�	&
I
x
�
�
8r���$E[~��
h
�
�
*��"6\t��t�0O��,z��,W���:i���|���>e���@���Y|���8j��I�$c�3u���D��<�� h � � !+!p!�!�!�!"A"u"�"�"#O#�#�#0$W$�$�$!%y%�%&5&m&�&')'_'�'�'�'#(H(�(�(�(:)U)u)�)�)C*l*�*+K+�+&,,�,N-�-�-
./.u.�../�/�/�/F0�0�01J1�1�1�1�12P2�2�2
3N3�3�384d4�4�45>5m5�5646r6�6�6�6*7X7|7�7�7�7'8i8�89H9c9x9
:7:�:�:;E;�;�;%<X<�<�<�<W=�=�=0>P>�>�?�?0@�@=AdA�A�AB7B�B�BC8C�C�C,DXD�DESErE�E�E�EF_F�F�F�F�F�FG4GHGcG�G�G�GHtH�HIIIaI�I�I�I�I�IJ#J;J_J�J�J�J�J�JK"KRK�K�K�KL<LsL�L�L7MnM�M�M�MN5NiN�N7OOP=PoP�P�P�P�PQIQWQ�Q�Q�Q#RiR�R�R�RS9SKShS�S�S�S�SGTYT�T�T�T'UJU`U�U�U�U VdV�V�V�VW\W�W�W&X~X�X�XY"YgY�Y�Y	Z@ZmZ�Z�ZA[�[�\W]�]�]C^�^�^_I_�_�_`y`�`>a�a�a�agb�b�b�b
c3c�cd�d�de�e�e*fff�f�f6g�g�gGh�h�h0i`i�i�ijEjrj�j�j�j�j)kck�k�k�khl�lmQm�m�m)n^n�n�n'o�o�o�o,p�p�p�p3qkq�q�q%rer�rs)s[s�s�s7t{t�t�tulu�uvOvtv�v�v�v+wsw�w'xax�x�x�xy4yHyZy�y�y5zIz|z�z7{V{�{�{�{�{|0|m|�|�|}=}i}�}�}�}~a~�~�~3�$�p��'�N�_�������c������;�\����%�W���%�h����!�T���	������W�g�������ψ��'�]���̉
�I�������k���Ë�%�n���ʌ���6�i����<�����L�����(�.�8�E�O�W����Ր��"�K�v����(�N�g�Œ�?�w������-�{�����-�ؖ��/���7���9�ߚ}�ۛA���.�?���֝�;�w���О/���͟�;�v���Π���ġ�(�_���Ӣ�g���=�ߤb�Υ'�b���ڦ�$�@����ȩ��p�)��������U�����V����=�w�����:�h��O���ҳ�;���#�b�����ݵ�\����j�'�*�b�{�¸�_�̺.�k����s�����d���ܽ�� �������*����0��������������R�t���������"�a����2�I���q���+�[��������!�E�b���������%�d���#�������]������e���>�����N�n���j�����7�����
��������]�������8��������6��:�����N�p���6�j����P����W�����p��o�����B�x���������(������������M�����:�����K�����
�4�g�����7�����P�������E����V�����#�e��������W�����G�p��������I�q��������6�b���6����@�h������g��?�S�����H������S���_����s����f����$p�v��?��6m��L��O~�	_	�	3
�
�
f��(Bd��� 
M
l
Bq�X4R�L��V�
%�;q�I���/��/Sw��BYl��H��ILx��
`���8Z�I�
_��� !�!"*"�"�"�"=#S#x#�#�#~$�$1%]%�%�%'&=&T&�&�&�&�&'$'I'�'�'�'�()=)�)�)�*+Z+�+�+�,L-�-�-?.�.�.�.'/Q/|/�/�/�//0P0�011Z1�12B2�2P3x3�3�3�3464�4�4�4)5T5�5�5.6k6�6�637�7�7^8�89R9}9�9�9:K:�:�:�:;&;3;9;i;�;�;C<�<�<=k=�=>:>h>�>5?�?�?K@�@�ABHBiB�B�B-CtC�C�C,D�DEwE�E�E/FiF�FGHG�G�GJH�H�H�H7IaI�I
JlJ�J�JKEK�K�K�K LmL�L
M3MqM�M�MNcN�NORO�O4PrP�P�PQ[Q�QRKR�R+SIS�S�S�T�U
V�VtW�W�W�W X2XKX�X�X�X�XY:YTY�Y�Y�Y,ZYZ�Z�Z[K[�[�[D\d\]M]�]�]1^Z^�^9_s_%`Y`�`�`�`$aXa�a�abNb|b�b�bOc�c�c�c�d�d�d9e�e�e�ef5f�f�fgUgog�gBheh�hPijbj�j�j
kl�lm<mwm�mBn�n�nko�o�p�p(qfq�q�qr|r�r�sEt�t�u*v�w�w�wJx�xyCy�y�yzIz�z�z"{c{�{|�|}L}�}�},~k~�~�~`%�����\���J�ӂ������`�z����&�X���!�v�Ԇ0���Ї	�+�`����x���~����J����?�w����(�^����X�����k�ٓ^���W�����ݕ^����`���×�h����R�����6�n���ך�X���h�ٜR���I�d����+�t���
�-�c����1�s���̡ϡ�Y����Q�r���ѣK�p���ۤ�o�å
�r�ɦ6����$�S��
�E���ީ:�g�����a�֫_����A����5�z�����u��x�B�ѱ�8�j���ҲֲO����������+���϶ ���ݷ6������(�R���B����+������_���/���ʿ�9��v��y�8���1�t���[�������$���(�W�!�Z�����m�V�����L����������E���0�_������F���_��1���1���>���H����?�+�W�������T�����M�����8�����!�������-���0���M���\�����Q���+�c�����f�-���&����G�����.����n�
�����I�������!�X�����<���7�����W���O�R�����8������K���#���'�j����������j���f�����V�E|�-e6g���z�3^��8Z��U	}	�	�	Z
�
N�Z��Q
�
�
}�o��*�'g$C����l���0��4�4y�?v��+U����+�Br���H|���#Y��F{�/k�� D r x �  !<!k!�!�!�!!"e"�"#N#�#'$�$v%�%�%	&�&�&'N'�'>(�(�(%)W)�)�)�)�)'*�*
+�+,�,�,T-�-�-�-3.g.�./6/l/�/0E0�0�0�0151>1I1t1�12_2�2�2�2�233V3t3�3�344;4^4�4�45I5�5�5�5F6p6�6�6�6C7|7�7�78�8�8�9<:�:;P;*<�<?=e=�=�=�=>0>L>�>�>�>�?=@_@�@�@AmA�A�ABFBuB�B4C5D�D�D�D:E�E�E�EF<F�F�F"GgG�G�G;HdH�H�H�HI@IaI�I�IJEJ�J�J�JKQK�K�K�K�KLL5L�L�MN<N�N^O2P�P�P�P�P-Q_Q�Q�Q�QR6RWR�R�R�RS&S=SXS�S�ST>T�T�T�TU!UQUyU�U�U�UVKV�V�V�VW$WMW�W�W�WX:XNX�X�X�X+Y�Y�YZ8ZbZ�Z�Z�Z[-[S[x[�[�[�[A\�\�\+]�]�])^b^�^ _�_ `Z`�`\a�a
b�b�d�de�efOf~f�f�f7g�g�gh;h�h�h
ii+j�j�jkuk�kJl�l�l�lm.mVmwm�m�mnHn�n�n$ogo�o�o�ocp�p0q�q�qNryr�r�r�r1sxs�stVt�t/uZu�u	v5v�v�vwUw�w�w�w�x�yVz:{p{�{�{�{|(|�|�|�|�|}P}�}�}i~�~g���V������j�����΂��l����%�W���
�C�������W�ȇ��,�Z����.������_�����ʊ��4�m������(���Ս�@�_����-�@�������E�d�Ȑ�=�z�Ñ�\���ɒ���L�Ԕ��?����ѕ��C�`���Ԗ��1�M���Y�����՘�C�s���ƙ�7�}�����:�e���ӛ�Q��*�J�����d�����I���ʠ�K�ȡf�����7�]�������n�T�Ѧ���������$������N�}���¬p����/�]�������̯��6�U�ð2��N�n�'�ų�y�´R�ε'�?�[���Ͷѷx�����e�����Ϻ�Y������m�����ü��C�t���ѽ��+�P����A�i����2����L�������*�U�����9�b�����)����/�������4�c�������a�����C���#�w�����������S�n�������E����������R��������E�x����E�\�������!�I�i��������O������C�g����������A�j������3�Z�����r����;�m�������i��������c��������8������3�P�x�������'�N�u������#�:�j��������H�~�������!�]������Z������@�g�����&�p�������6�|���M������=�V�����������\������������k�����,�U�����]���������X������C��B���'�j������Y�����
�A�o�����*�h�����.�p�����B�q���"�A������'�s��;�\�����B�J�U��������B�a��[����5������X�����Q�e����:�&G������:K|����	�	{
�
�
8v��s��
\
�
>K��������8w���Uz���
�?��P���X�:r�
T���`���M{�T��!N��+z�*j��� S | � � � O!�!�!-"W"�"�"�""#J#�#�#$A$u$�$�$%_%�%�%�%�%A&v&H'�''(�().)D)d)�);*�*+V+�+�+4,\,�,--�-�-�../�/0B0`0�0�0�0�0�0�0�0�0111w1�1�1�1'2H2�2�2�2�223�34q4�4�45.5o5�5�56P6�6�6C7~7�7�728�89�9e:�:$;Y;�;�<�<�<=8=h=n=�=�=�=6>w>�>�>�>?+?F?l?�?�?�?�?�?@=@�@�@�@�@A4AlA�A�A�AB>BlB�B�B�BC0CWCyC�CDQDuD�D�D-EwE�E�EF1FTF�F�FGG[G�G�G�GHCH]H�H�HInI�I�I�IJUJ�J�J�JK;KcK�K�K�KLL9L<L�L@MNrN�N�NOEOpO�O�OP.P�P�P�P�P?QtQ�Q�Q�QR1RQR|R�R�R�RS<SWS�S�S�STdTgT�T�T�T�T�TUSUpU�U�UFV�V�V8W\W|WW�W�W�W�WXX�X�X�X7YPZ�Z,[�[�\�]�] ^>^�^�^�^_#_S_n_�_�_`A`n`�`�`a9a�a�a�a�abKbrb�b2cccyc�c�c�c�c�c,dKd}d�d�deTe�e�ef6f\f�f�f�f6gWgog�g�g�ghDh�h�hi+iRii�i�i�i�ij.jSjwj�j�j(kFkxk�k�k�klUl�l�l�l!m�m�n�n@oeo�o�o�opep�pq5qkq|q�q�q4rTr}r�r�rwswt�t�tuNu�u�u�uv:vZv~v�v�v�v
w&wDw�w�w�wx%xAxwx�x�x(y|y�yz�z#{e{�{}|�|/}�}[~�~p��������/�m����
�X�o�����.�;�����/�i���څ(�Y����G����[�Ј?����:���������g�Ì,������Ďo���	�O���:�ڑ^�����В
�1�t����+�n���Ҕ�N�ɕ�K�y�������A������7�q�Λ
�;�~����2�n�ǝe���L���3����4���	������&����@�Ȧ�<�v�����������{�ҪP�������i�¬'���׭����������M����c�,�{�����ղ��+�L�{���4����8�}�����M�����6����=�|���{�޺��c���̼��3����H���%���ǿ�F������	�G�����3�w����U����w���L�����C�����*�u���Q���`����^����;�h������I������������;���/�}�����!�[�������+�g������L����F�x���2�f����������������j�|����<�������f���(�]����Z�����5����F�~���P�����3���F��������G�����
�e���8�����E����D�������3������q���.�������Q�����������
�1�N�v�������3�a�������>�V��������L�������Z�����6�v�����=�e������N�������@�l�����*�-�_�������;�c�����/�v���)�����U�q������)�����#&),/258;>ADGJMPSVY\_behknqtwz}������������������������147:=@CFILORUX[^adgjmpsvy|�����������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~����������������������������*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258���1\�������	'	O	�

X
�
�
6�*��
A
{
�
�Bg�BEHKNQTWZ]`cfilorux{~�������������������Z]`cfilorux{~�����������������������6���������������������������������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}��������������

"%(+.147:=@CFILORUX[^adgjmpsvy|�����������������������:=@��������������������	t�?��9g�U���SVk���T�J��� T � $!z!�!�"�"N#$$$Y$�$%?%B%E%\%_%b%e%h%k%n%&m&�&!'K'}'�'(R(v(�(�()�)�)�)*�*`+�+7,q,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---	--------!-$-'-*---0-3-6-9-<-?-B-E-H-K-N-Q-T-W-Z-]-`-c-f-i-l-o-r-u-x-{-~-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-.!.$.'.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.�.///	////////!/$/'/*/-/0/3/6/9/</?/B/E/H/K/N/Q/T/W/Z/]/`/c/f/i/l/o/r/u/x/{/~/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/�/0000000000 0#0&0)0,0/0205080;0>0A0D0G0J0M0P0S0V0Y0\0_0b0e0h0k0n0q0t0w0z0}0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0�0d1�1�1V2�2�23c3�3�3424y4�4�4�4�4"5g5�5�56'6H6�6�6�6�67D7h7�7�78n8�8�8�8�89{9�9:>:]:�:�:C;�;<d<<�<�<�<=Z=�=>A>o>�>�>K?�?�?�?�?�?�?�?�?�?�?�?�?�@�@�@_AbA�A�A�A%BPBxB�B�D$EAE�E�E�F�GH9HhH�H�H�H�HJvJ�K�K�KLVL�L�L�L�L�L�L�L�L�L�L�LM,M/MMMPM�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�MNNN8N;N>NANDNGNJNMNPNSNVNYN\N_NbNeNhNkNnNqNtN�N�NO1O4O�O�OPPPPPPPPPP P#P&P)P,P/P�P�PWQ�Q�Q�Q�Q�Q-RWR�R�R�R�R	SNSyS�S�S�T�T�T�T�T�T�T�T�T�T�T�TUU*V-V0V_V�V�W|X�X�Y\Z�Z�[\+\S\v]�]s^�^�^�^�_`S`g`w`�`�`�`
a&aua�a�a b.bOb�bic�c�cd!dJdyd�d�de@e�e$f{f}f�f'gog�g1h�h�h�h�h�hi3iWi�i�i�i�j�j\k�k�k�k�k&lgl�l�lBm}m�m%nin�n$oIolo�o�o�o�o8pkp�p�p�p�p�p1qeqhqkqnqqqtqwqzq}q�q4r�r�rsns�stt�tu=uiu�u�uGv�v�vXw�wAx�x�x.y�y�yzrzE{l{�{�{|s|�|}0}Q}t}~:~�~f�������7�����ۂ)�{���҃��� �������:�U���@�������چ���6�k����2���Ȉ��z���ω�@���ފ;���ۋ�V�ΌC�����L����+�b�������k�ӑM����k�����M�������Õ������V���ȗ�g�Ԙט	�A����'�Q������� �L���ݛ���N���ޜ,�M�����Н�
�5�e����4�ğ�C�ʡ
�w�ݢ}��s��4���ۥi�צ+�����ŧ���X�r������s�����T�j�ت�X��������;�d�����L�k�����<���˯��O�����C�����'����e�#�U������N���ε��#�B�b����4���ʷ"�}����"�f�۹̺��!�8�q�������������!����5�m�о߿)��U����Y�����=��������H�r��������.����Z�������{�E�
�A�����H����_���b���:���6�����;�p���8�y����.��������H�����A����������H���7�c�f��������������������	��������!�$�'�*������#�&�)�,�/�2��������>�A�d�������/�W���*�-��\�����B���c���b����W���G��c���$�}����x����i����g����������������������������������������������������������������������������=������A�������#�����]���	��������2�P�n��� �R�n���������B�����l����������C����K�Y�\�_�b����3xc�@~���T�-�j�]�	M	�	k
�
As�L���
k�{A����j�#K��`��O�U�D��^�{�u�!g�� &!�!5"�"O#�#�#�#5$�$�$�%~&�'u(�)�)�*-+�+B,�,�,�,
-'-Z-�-.F.�.�.�.�./,/�/91V1}1�1�1*2M2�2�273�3�3U4�4	5�67,9�9P:~:�:p;�;�<R=�=>D>�>2?p?�?�@A�A�A�A�AByB�B�B�B�BmC�CDDD�D�EFLF�F�FG\G�G�GH�H'I�I�IKJ�JHK�K�LgM?NO`O�O�O&PhP�P�P�PQ@QsQ�Q�QR�R%SwS�S�S;TaT�T�T�TUZU�UhV(W�W�Z]9]j]�]�]1^�^�^>_w_�_`�`Xa�a�b:c�cd{d�d�d�d#e�e�e8f\f�f�fIg�g�g�g�g"h^h~h�h�h�h�h�hi0i�i6j�j�j<k�k�lnSn8pJpZp�p�p�p�p-q�qrzr�rSs�stQt�t�tQu�u�u$v}v�vnw�w�xIy�y�y.zizlz){�{,|�|}�}�}=~�~e�T�ʀ��\�Á��3���ۂ�7�`���؃�0�k�τ����Q����s���"�@�b�m�������ۈ����M�h�Љ{���d����x���ތ���&�Ď8�g�������Ɛf���������Q�ғ��$������@���Ԗ��1�����hashchkisamchkNOSINo puedo crear archivo '%-.200s' (Error: %d - %s)No puedo crear tabla '%-.200s' (Error: %d - %s)No puedo crear base de datos '%-.192s' (Error: %d - %s)No puedo crear base de datos '%-.192s'; la base de datos ya existeNo puedo eliminar base de datos '%-.192s'; la base de datos no existeError eliminando la base de datos(no puedo borrar '%-.192s', error %d - %s)Error eliminando la base de datos (No puedo borrar directorio '%-.192s', error %d - %s)Error en el borrado de '%-.192s' (Error: %d - %s)No puedo leer el registro en la tabla del sistemaNo puedo obtener el estado de '%-.200s' (Error: %d - %s)No puedo acceder al directorio (Error: %d - %s)No puedo bloquear archivo: (Error: %d - %s)No puedo abrir archivo: '%-.200s' (Error: %d - %s)No puedo encontrar archivo: '%-.200s' (Error: %d - %s)No puedo leer el directorio de '%-.192s' (Error: %d - %s)No puedo cambiar al directorio de '%-.192s' (Error: %d - %s)El registro ha cambiado desde la ultima lectura de la tabla '%-.192s'Disco lleno (%s). Esperando para que se libere algo de espacio... (Error: %d - %s)No puedo escribir, clave duplicada en la tabla '%-.192s'Error en el cierre de '%-.192s' (Error: %d - %s)Error leyendo el fichero '%-.200s' (Error: %d - %s)Error en el renombrado de '%-.210s' a '%-.210s' (Error: %d - %s)Error escribiendo el archivo '%-.200s' (Error: %d - %s)'%-.192s' esta bloqueado contra cambiosOrdeancion canceladaLa vista '%-.192s' no existe para '%-.192s'Error %d - '%-.192s' desde el manejador de la tablaEl manejador de la tabla de '%-.192s' no tiene esta opcionNo puedo encontrar el registro en '%-.192s'Informacion erronea en el archivo: '%-.200s'Clave de archivo erronea para la tabla: '%-.200s'; intente repararloClave de archivo antigua para la tabla '%-.192s'; reparelo!'%-.192s' es de solo lecturaMemoria insuficiente. Reinicie el demonio e intentelo otra vez (necesita %d bytes)Memoria de ordenacion insuficiente. Incremente el tamano del buffer de ordenacionInesperado fin de ficheroU mientras leiamos el archivo '%-.192s' (Error: %d - %s)Demasiadas conexionesMemoria/espacio de tranpaso insuficienteNo puedo obtener el nombre de maquina de tu direccionProtocolo erroneoAcceso negado para usuario: '%-.48s'@'%-.64s' para la base de datos '%-.192s'Acceso negado para usuario: '%-.48s'@'%-.64s' (Usando clave: %s)Base de datos no seleccionadaComando desconocidoLa columna '%-.192s' no puede ser nulaBase de datos desconocida '%-.192s'La tabla  '%-.192s' ya existeTabla '%-.129s' desconocidaLa columna: '%-.192s' en %-.192s es ambiguaDesconexion de servidor en procesoLa columna '%-.192s' en %-.192s es desconocidaUsado '%-.192s' el cual no esta group byNo puedo agrupar por '%-.192s'El estamento tiene funciones de suma y columnas en el mismo estamentoLa columna con count no tiene valores para contarEl nombre del identificador '%-.100s' es demasiado grandeNombre de columna duplicado '%-.192s'Nombre de clave duplicado '%-.192s'Entrada duplicada '%-.192s' para la clave %dEspecificador de columna erroneo para la columna '%-.192s'%s cerca '%-.80s' en la linea %dLa query estaba vaciaTabla/alias: '%-.192s' es no unicaValor por defecto invalido para '%-.192s'Multiples claves primarias definidasDemasiadas claves primarias declaradas. Un maximo de %d claves son permitidasDemasiadas partes de clave declaradas. Un maximo de %d partes son permitidasDeclaracion de clave demasiado larga. La maxima longitud de clave es %dLa columna clave '%-.192s' no existe en la tablaLa columna Blob '%-.192s' no puede ser usada en una declaracion de claveLongitud de columna demasiado grande para la columna '%-.192s' (maximo = %lu).Usar BLOB en su lugarPuede ser solamente un campo automatico y este debe ser definido como una clave%s: preparado para conexiones
Version: '%s'  socket: '%s'  port: %d%s: Apagado normal
%s: Recibiendo signal %d. Abortando!
%s: Apagado completado
%s: Forzando a cerrar el thread %ld  usuario: '%-.48s'
No puedo crear IP socketLa tabla '%-.192s' no tiene indice como el usado en CREATE INDEX. Crea de nuevo la tablaLos separadores de argumentos del campo no son los especificados. Comprueba el manualNo puedes usar longitudes de filas fijos con BLOBs. Por favor usa 'campos terminados por '.El archivo '%-.128s' debe estar en el directorio de la base de datos o ser de lectura por todosEl archivo '%-.200s' ya existeRegistros: %ld  Borrados: %ld  Saltados: %ld  Peligros: %ldRegistros: %ld  Duplicados: %ldParte de la clave es erronea. Una parte de la clave no es una cadena o la longitud usada es tan grande como la parte de la claveNo puede borrar todos los campos con ALTER TABLE. Usa DROP TABLE para hacerloNo puedo ELIMINAR '%-.192s'. compuebe que el campo/clave existeRegistros: %ld  Duplicados: %ld  Peligros: %ldYou can't specify target table '%-.192s' for update in FROM clauseIdentificador del thread: %lu  desconocidoTu no eres el propietario del thread%luNo ha tablas usadasMuchas strings para columna %-.192s y SETNo puede crear un unico archivo log %-.200s.(1-999)
Tabla '%-.192s' fue trabada con un READ lock y no puede ser actualizadaTabla '%-.192s' no fue trabada con LOCK TABLESCampo Blob '%-.192s' no puede tener valores patronNombre de base de datos ilegal '%-.100s'Nombre de tabla ilegal '%-.100s'El SELECT puede examinar muchos registros y probablemente con mucho tiempo. Verifique tu WHERE y usa SET SQL_BIG_SELECTS=1 si el SELECT esta correctoError desconocidoProcedimiento desconocido %-.192sEquivocado parametro count para procedimiento %-.192sEquivocados parametros para procedimiento %-.192sTabla desconocida '%-.192s' in %-.32sCampo '%-.192s' especificado dos vecesInvalido uso de función en grupoTabla '%-.192s' usa una extensión que no existe en esta MySQL versiónUna tabla debe tener al menos 1 columnaLa tabla '%-.192s' está llenaJuego de caracteres desconocido: '%-.64s'Muchas tablas. MySQL solamente puede usar %d tablas en un joinMuchos camposTamaño de línea muy grande. Máximo tamaño de línea, no contando blob, es %ld. Tu tienes que cambiar algunos campos para blobSobrecarga de la pila de thread:  Usada: %ld de una %ld pila.  Use 'mysqld --thread_stack=#' para especificar una mayor pila si necesarioDependencia cruzada encontrada en OUTER JOIN.  Examine su condición ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerNo puedo cargar función '%-.192s'No puedo inicializar función '%-.192s'; %-.192sNo pasos permitidos para librarias conjugadasFunción '%-.192s' ya existeNo puedo abrir libraria conjugada '%-.192s' (errno: %d %-.128s)No puedo encontrar función '%-.128s' en librariaFunción '%-.192s' no está definidaServidor '%-.255s' está bloqueado por muchos errores de conexión.  Desbloquear con 'mysqladmin flush-hosts'Servidor '%-.255s' no está permitido para conectar con este servidor MySQLTu estás usando MySQL como un usuario anonimo y usuarios anonimos no tienen permiso para cambiar las clavesTu debes de tener permiso para actualizar tablas en la base de datos mysql para cambiar las claves para otrosNo puedo encontrar una línea correponsdiente en la tabla userLíneas correspondientes: %ld  Cambiadas: %ld  Avisos: %ldNo puedo crear un nuevo thread (errno %d). Si tu está con falta de memoria disponible, tu puedes consultar el Manual para posibles problemas con SOEl número de columnas no corresponde al número en la línea %ldNo puedo reabrir tabla: '%-.192sInvalido uso de valor NULLObtenido error '%-.64s' de regexpMezcla de columnas GROUP (MIN(),MAX(),COUNT()...) con no GROUP columnas es ilegal si no hat la clausula GROUP BYNo existe permiso definido para usuario '%-.48s' en el servidor '%-.255s'%-.128s comando negado para usuario: '%-.48s'@'%-.64s' para tabla '%-.64s'%-.16s comando negado para usuario: '%-.48s'@'%-.64s' para columna '%-.192s' en la tabla '%-.192s'Ilegal comando GRANT/REVOKE. Por favor consulte el manual para cuales permisos pueden ser usados.El argumento para servidor o usuario para GRANT es demasiado grandeTabla '%-.192s.%-.192s' no existeNo existe tal permiso definido para usuario '%-.48s' en el servidor '%-.255s' en la tabla '%-.192s'El comando usado no es permitido con esta versión de MySQLAlgo está equivocado en su sintaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useConexión abortada %ld para db: '%-.192s' usuario: '%-.48s' (%-.64s)Obtenido un paquete mayor que 'max_allowed_packet'Obtenido un error de lectura de la conexión pipeObtenido un error de fcntl()Obtenido paquetes desordenadosNo puedo descomprimir paquetes de comunicaciónObtenido un error leyendo paquetes de comunicaciónObtenido timeout leyendo paquetes de comunicaciónObtenido un error de escribiendo paquetes de comunicaciónObtenido timeout escribiendo paquetes de comunicaciónLa string resultante es mayor que max_allowed_packetEl tipo de tabla usada no permite soporte para columnas BLOB/TEXTEl tipo de tabla usada no permite soporte para columnas AUTO_INCREMENTINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESIncorrecto nombre de columna '%-.100s'El manipulador de tabla usado no puede indexar columna '%-.192s'Todas las tablas en la MERGE tabla no estan definidas identicamenteNo puedo escribir, debido al único constraint, para tabla '%-.192s'Columna BLOB column '%-.192s' usada en especificación de clave sin tamaño de la claveTodas las partes de un PRIMARY KEY deben ser NOT NULL;  Si necesitas NULL en una clave, use UNIQUEResultado compuesto de mas que una líneaEste tipo de tabla necesita de una primary keyEsta versión de MySQL no es compilada con soporte RAIDTu estás usando modo de actualización segura y tentado actualizar una tabla sin un WHERE que usa una KEY columna. %sClave '%-.192s' no existe en la tabla '%-.192s'No puedo abrir tablaEl manipulador de la tabla no permite soporte para %sNo tienes el permiso para ejecutar este comando en una transiciónObtenido error %d - '%-.192s' durante COMMITObtenido error %d - '%-.192s' durante ROLLBACKObtenido error %d durante FLUSH_LOGSObtenido error %d durante CHECKPOINTAbortada conexión %u para db: '%-.192s' usuario: '%-.48s' servidor: '%-.255s' (%-.64s)El manipulador de tabla no soporta dump para tabla binariaBinlog closed, cannot RESET SOURCEFalla reconstruyendo el indice de la tabla dumped '%-.192s'Error del master: '%-.64s'Error de red leyendo del masterError de red escribiendo para el masterNo puedo encontrar índice FULLTEXT correspondiendo a la lista de columnasNo puedo ejecutar el comando dado porque tienes tablas bloqueadas o una transición activaDesconocida variable de sistema '%-.64s'Tabla '%-.192s' está marcada como crashed y debe ser reparadaTabla '%-.192s' está marcada como crashed y la última reparación (automactica?) fallóAviso:  Algunas tablas no transancionales no pueden tener rolled backMultipla transición necesita mas que 'max_binlog_cache_size' bytes de almacenamiento. Aumente esta variable mysqld y tente de nuevoEsta operación no puede ser hecha con el esclavo funcionando, primero use STOP SLAVEEsta operación necesita el esclavo funcionando, configure esclavo y haga el START SLAVEEl servidor no está configurado como esclavo, edite el archivo config file o con CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logNo puedo crear el thread esclavo, verifique recursos del sistemaUsario %-.64s ya tiene mas que 'max_user_connections' conexiones activasTu solo debes usar expresiones constantes con SETTiempo de bloqueo de espera excedidoEl número total de bloqueos excede el tamaño de bloqueo de la tablaBloqueos de actualización no pueden ser adqueridos durante una transición READ UNCOMMITTEDDROP DATABASE no permitido mientras un thread está ejerciendo un bloqueo de lectura globalCREATE DATABASE no permitido mientras un thread está ejerciendo un bloqueo de lectura globalArgumentos errados para %s'%-.48s`@`%-.64s` no es permitido para crear nuevos usuariosIncorrecta definición de la tabla; Todas las tablas MERGE deben estar en el mismo banco de datosEncontrado deadlock cuando tentando obtener el bloqueo; Tente recomenzar la transiciónEl tipo de tabla usada no soporta índices FULLTEXTNo puede adicionar clave extranjera constraintNo puede adicionar una línea hijo: falla de clave extranjera constraintNo puede deletar una línea padre: falla de clave extranjera constraintError de coneccion a master: %-.128sError executando el query en master: %-.128sError de %s: %-.128sEquivocado uso de %s y  %sEl comando SELECT usado tiene diferente número de columnasNo puedo ejecutar el query  porque usted tiene conflicto de traba de lecturaMezla de transancional y no-transancional tablas está deshabilitadaOpción '%s' usada dos veces en el comandoUsuario '%-.64s' ha excedido el recurso '%s' (actual valor: %ld)Acceso negado. Usted necesita el privilegio %-.128s para esta operaciónVariable '%-.64s' es una SESSION variable y no puede ser usada con SET GLOBALVariable '%-.64s' es una GLOBAL variable y no puede ser configurada con SET GLOBALVariable '%-.64s' no tiene un valor patrónVariable '%-.64s' no puede ser configurada para el valor de '%-.200s'Tipo de argumento equivocado para variable '%-.64s'Variable '%-.64s' solamente puede ser configurada, no leídaEquivocado uso/colocación de '%s'Esta versión de MySQL no soporta todavia '%s'Recibió fatal error %d: '%-.512s' del master cuando leyendo datos del binary logSlave SQL thread ignorado el query debido a las reglas de replicación-*-tablaVariable '%-.192s' es una %s variableEquivocada definición de llave extranjera para '%-.192s': %sReferencia de llave y referencia de tabla no coincidenOperando debe tener %d columna(s)Subconsulta retorna mas que 1 líneaDesconocido preparado comando handler (%.*s) dado para %sBase de datos Help está corrupto o no existeCíclica referencia en subconsultasConvirtiendo columna '%s' de %s para %sReferencia '%-.64s' no soportada (%s)Cada tabla derivada debe tener su propio aliasSelect %u fué reducido durante optimizaciónTabla '%-.192s' de uno de los SELECT no puede ser usada en %-.32sCliente no soporta protocolo de autenticación solicitado por el servidor; considere actualizar el cliente MySQLTodas las partes de una SPATIAL index deben ser NOT NULLCOLLATION '%s' no es válido para CHARACTER SET '%s'Slave ya está funcionandoSlave ya fué paradoTamaño demasiado grande para datos descomprimidos. El máximo tamaño es %d. (probablemente, extensión de datos descomprimidos fué corrompida)Z_MEM_ERROR: No suficiente memoria para zlibZ_BUF_ERROR: No suficiente espacio en el búfer de salida para zlib (probablemente, extensión de datos descomprimidos fué corrompida)ZLIB: Dato de entrada fué corrompido para zlibRow %u was cut by GROUP_CONCAT()Línea %ld no contiene datos para todas las columnasLínea %ld fué truncada; La misma contine mas datos que las que existen en las columnas de entradaDatos truncado, NULL suministrado para NOT NULL columna '%s' en la línea %ldOut of range value for column '%s' at row %ldDatos truncados para columna '%s' en la línea %ldUsando motor de almacenamiento %s para tabla '%s'Ilegal mezcla de collations (%s,%s) y (%s,%s) para operación '%s'Cannot drop one or more of the requested usersNo puede revocar todos los privilegios, derecho para uno o mas de los usuarios solicitadosIlegal mezcla de collations (%s,%s), (%s,%s), (%s,%s) para operación '%s'Ilegal mezcla de collations para operación '%s'Variable '%-.64s' no es una variable componente (No puede ser usada como XXXX.variable_name)Collation desconocida: '%-.64s'Parametros SSL en CHANGE MASTER son ignorados porque este slave MySQL fue compilado sin soporte SSL; pueden ser usados despues cuando el slave MySQL con SSL sea inicializadoServidor está rodando en modo --secure-auth, pero '%s'@'%s' tiene clave en el antiguo formato; por favor cambie la clave para el nuevo formatoCampo o referencia '%-.192s%s%-.192s%s%-.192s' de SELECT #%d fue resolvido en SELECT #%dParametro equivocado o combinación de parametros para START SLAVE UNTILEs recomendado rodar con --skip-replica-start cuando haciendo replicación step-by-step con START SLAVE UNTIL, a menos que usted no esté seguro en caso de inesperada reinicialización del mysqld slaveSQL thread no es inicializado tal que opciones UNTIL son ignoradasNombre de índice incorrecto '%-.100s'Nombre de catalog incorrecto '%-.100s'Query cache fallada para configurar tamaño %lu, nuevo tamaño de query cache es %luColumna '%-.192s' no puede ser parte de FULLTEXT indexDesconocida key cache '%-.100s'MySQL esta inicializado en modo --skip-name-resolve. Usted necesita reinicializarlo sin esta opción para este derecho funcionarDesconocido motor de tabla '%s''%s' está desaprobado, use '%s' en su lugarLa tabla destino %-.100s del %s no es actualizableEl recurso '%s' fue deshabilitado; usted necesita construir MySQL con '%s' para tener eso funcionandoEl servidor MySQL está rodando con la opción %s tal que no puede ejecutar este comandoColumna '%-.100s' tiene valor doblado '%-.64s' en %sEquivocado truncado %-.64s valor: '%-.128s'Incorrecta definición de tabla; Solamente debe haber una columna TIMESTAMP con CURRENT_TIMESTAMP en DEFAULT o ON UPDATE cláusulaInválido ON UPDATE cláusula para campo '%-.192s'This command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionEntrada duplicada '%-.64s' para la clave '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTAcceso negado para usuario: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setParticion '%-.64s' no existeFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionEntrada duplicada para la clave '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\�ю����swedish/errmsg.sysnu�[��������H|��Z��Q���
Hw�@w��&J_���*m��a��c��	c		�	�	�	�	
.
B
d
�
�
�
9a����%Lg�� 
B
�
�
+o����c��Mm��0}��&Ce{��,\�������%Gr���hz�r�;_���4r�k�&Q~��+J�I���/���2R�� 1 Y � � � !+!`!�!�!7"V"�"�"#;#�#�#�#($�$�$�$%%Z%}%�%�%�%6&s&�&�&�&'@'n'�'�'"(p(�(4)~)�)J*�*�*+I+�+�+�+A,�,�,�,7-�-�-�-.C.p.�.�.�./R/�/�/0H0�0�0
1?1j1�1�1�192|2�2�2
313T3�3�3�3�34N4t4�4&5Z5�5�5�556M6�6�6�67c7�7�7	8/8p8�8�8)9V9�9�9w:�:U;�;]<�<�<�<%=^=|=�=>W>�>�>9?n?�?@A@�@�@�@�@)ANA�A�A�ABB2BIBgB{B�B�B�BCEC�CD?D|D�D�D�D�DE,ECEVEnE�E�E�E�E
F"F8FUF�F�F�FGBGoG�G�G"HjH�H�H�HI9IhI�IJjJ�J4KpK�K�K�K�K.LOL|L�L�L�L0MVM�M�M�MN:NlN~N�N�N�NO0OzO�O�O�OPZP}P�P�P�PQSQ�Q�Q�Q�Q4R�R�R'SYS�S�STBTUT�T�TU<UsU�UV0VtV2W�W�XY,YvY�Y�Y>Z|Z�Z[M[�[\q\�\�\]�]�]�]^=^f^�^B_�_(`G`�`a]a�a�a1bib�bczc�cdcd�d�deDexe�e�efff\f�f�fg$g�g�g;h�h�h2ivi�i�i.jvj�jk^k�k�k&lgl�l�l7m~m�mnXn�no>o�o�o#pnp�p�p&q�q
rLrwr�r�r4sVs�s�sjt�t�tu<u^u�u�u�u�uv^v�v�v�v7w�w�wx,xLx^x�x�x�x	y)y�y�y�yz/zMz�z�z!{F{�{E|�|�|C}q}�}�}�};~T~�~
)h����V���ۀ
�?�ہ�\���ׂ��6���7�k������:�N�k���Å��9�h�����L������0�_�����
�5�f�����҉�C���؊E�������N���ÌʌԌ�����U�u�����A�b���Ȏ��e���ߏ�A�^���͐�b���&�͒x�&�ϔK�וT�ٖ��{��I�Ιߙ<�v���ۚ�N�p�ϛ$�m���ۜ�7�n���+�d���ʞ�D���֟�Z�������ޢ�\���ţۣ��ʤ���R�'��E��������6�r�լ
�P����1�l���߮�.����]������Q��*�a���Ʋ�E���ϳS���J�c���˶M�ŷ'�d�����l����]���պ�����}��#���ܽ)�������ڿ�����K�m����������Z����+�B���j���$�T����������>�[����������]����������V������^���7�����G�g���c�����0�������������V�������1�}������/�	�'�����;�]���#�W�����=�����D�����]���\�z���/�e���������������������:�����'�����8�������!�T������$�����=�������2����C�v����R�}�������D�����4�]�������
�6�^���������#�O���#�����-�U�u�����T��,�@�n����5�������@����L����`����S���w��]����c��,��#Z��9y��<k�L� ��S���	/	Q	m	�	�	
:
Y
/^��E�!
?
�
�
9��C����(^��6|��u�@d���/FY��5��69e���Mn��%G6��L��p������* @ e � � k!�!"J"�"�"#*#A#�#�#�#�#�#$6$m$�$�$�%�%*&�&�&�'(G(�(�(�)9*�*�*,+�+�+�+,>,i,�,�,�,-=-z-�-
.G.�.�.//�/=0e0�0�0�0�0#1�1�1�12A2|2�23X3�3�3 4�4�4K5�5�5?6j6�6�6�687t7�7�7�78 8&8V8�8�809~9�9:X:�:�:';U;�;"<y<�<8=�=o>�>5?V?�?�?@a@�@�@A�A�AdB�B�BCVC�C�C5D�D�D7EwE�E�E$FNF�F�FYGG�G�G2HoH�H�H
IZI�I�I J^J�J�JKPK�K�K?L�L!M_M�M�MNHN�N
O8O�OP6P�P�P�QuR�RwSaT�T�T�T
UU8U�U�U�U�U	V'VAV~V�V�VWFW�W�WX8X~X�X1YQYZ:ZmZ�Z[G[�[&\`\]F]p]�]�]^E^�^�^�^;_i_�_�_<`p`�`�`�a�a�a&bvb�b�b�b"c~c�cdBd\d�d/eRe�e=f�fOg�g�g�g	i�i�i)jdj�j/k�k�kXl�l�m�mnSn�n�noio�oop2q�q�rsrt�t�t7uzuv0v�v�vw6wpw�wxPx�xy�y�y9z�z�z{X{�{�{M|}�}�}I~�~7��v���ҀM�g���ځ�E����c����|������M���Յe�����k�������7���ӌ,�d���э�K�v���E�~��X�ƐK�ϑ�D�v���ʒK����M�p�����U�����?�����#�[���ė�E��U�ƙ?���6�Q���ۛ�a������P���ѝ�`��������F���џ>�_�����8�]���ȡ	�\�����_���#�v���@�Х��2�r�˦'�T����
�N�èL�����.���٪"�g���Ϋ�b��e�/�����%�W�����ï<�����o�ӱ�����s���
�s�ʴ#�����׵�?���/�����u�ݸ��L����������&���c�پf�%����a��H�w���������D��G�~���Z�C�������9���������q�2�n��L������3���L���������+���5�����,��D�v�����A�p���:�����%������z���z�������:���I�����>����P�����S��������4���������[�������6��������E�|���)���$�y���D���<�?�����%�������8����p��W������������W����S������C����2�i�R#T{��g�� K��%Gw�Bj��G�;��G	�	�	>
m
�
j�\��
u
T�0r����
Y���p�!��!f�,c���Bo����/_���5i{��F~��3h�X��	1_e�
)X���R��; x !�!c"�"�"�"t#�#�#;$�$+%�%�%&D&r&�&�&�&'�'�'�(�(~)�)A*�*�*�* +T+�+�+#,Y,v,�,2-w-�-�-�-".+.6.a.�.�.L/�/�/�/�/�/�/C0a0�0�0�01(1K11�1262�2�2�233]3�3�3�304i4�4�45~5�5�6)7�7�7=89�9,:R:v:�:�:�:;9;�;�;�;�<*=L=�=�=
>Z>�>�>?3?b?�?!@"A{A~A�A'B{B�B�B�B)CxC�CDTD�D�D(EQE�E�E�EF-FNF�F�F�F2G�G�G�G	H>H�H�H�H�H�HI"I�I�J�J)KqKKLMpM�M�M�MNLN�N�N�NO#ODO|O�O�OPP*PEPrP�P�P+Q�Q�Q�Q�QR>RfR�R�R�RS8SqS�S�S�ST:TmT�T�TU'U;U�U�U�UV�V�V�V%WOW�W�W�W�WX@XeX�X�X�X.Y�Y�YZuZ�Z[O[�[
\�\
]G]�]I^�^�^�_sa�a�a�bc<ckc�c�c$drd�de(e�e�e�elfg�g�ghbh�h7i�i�i�ijjCjdj�j�jk5kyk�klTl�l�l�lPm�mn�n�n;ofo�o�o�opep�p�pCq�qrGr�r�r"sxs�stBtzt�t�t�u�vCw'x]x�x�x�x�xysy~y�y�y
z=z�z�zV{�{T|�|�|}C}l~�~�~W�����Y���ہ�D�����0�v����D�����G���ԅ�m�����L���������!�Z����߉�n��-�L�s���-�����ތ�2�Q�����*�g����I�����
���9����,�l�����ђ�0�M�������:�l����F�n����0�`�����ߖ$�j�ϗ��'�R�t���ۘ>����7�l����Q����6�}���ݝ8���S�����$�J�v����[�A����l��l���Хצ�t����;�j�����]���ݪ�J����m������#�B����	�;�[������f���?����,�H�������e���ε�R���s����F�m�����Z�n�����ֹ��0�a�������=�����.�V���޼�x�ӽ9�v�����B���ǿ&�O���������r�����!�P������N�����0����d������������@�[�������2����������?�r������2�e�����2�I�o������6�V�~������<�v����0�T�t��������.�W������� �G�����_����(�Z�������V���������P���������%������ �=�e�~������;�b��������'�W�w������5�k��������J������G�u����-�T�u����]�s�����#�i���:������*�C�v���������I������x�����X������B�n���J���p�����E�m�����0���/����W�������F�������.�\������U������]�����/�^����.��������`���(�I���
��/�7�B�{������/�N��H�r���"�������E����>��R���y�����'����4o���u����'8i���p�h��%c��`	�	�	
I
�
�
+8~��l���
�
�
%d���Bg������,��
=x��E�'_��A���	M~��:h��A��;l��g�W����@i���<��D��� 7 � � !.!b!�!�!�!L"}"�"�"�".#c#5$~$%�%�%&1&Q&�&('�'(C(�(�(!)I)z)�)*q*�*z+,�,-/-M-�-�-�-�-�-�-�-�-�-�-.d.�.�.�./5/p/�/�/�/0�0�0^1�1�1�12\2�2�23=3�3�304k4�4�45z5�5v6R7�78F8o8n9�9�9:%:U:[:}:�:�:#;d;�;�;�;�;<3<Y<|<�<�<�<�<�<*=m=�=�=�=�=!>Y>�>�>�>�>+?Y?�?�?�?�?@D@f@�@�@>AbA�A�ABdB�B�BCCAC�C�C�CDHD�D�D�DE0EJE�E�EF[FpF�F�F�FBGqG�G�G�G(HPH�H�H�H�HI&I)I�I-J�J_K�K�K�K2L]L�L�L�LMoMrM�M�M,NaN�N�N�N�NO>OiO�O�O�OP)PDP�P�P�P	QQQTQwQ�Q�Q�Q�Q�Q@R]R�R�R3S�S�S%TITiTlToTrT�T�TEUxU�U�U$V=W�WX�X�Y�Z�Z
[+[x[�[�[\\@\[\�\�\�\.][]�]�]�]&^n^�^�^�^�^8___�_`P`f`�`�`�`�`�`a8aja�a�a�aAbsb�b�b#cIczc�c�c#dDd\dtd�d�d	e1exe�e�ef?flf~f�f�f�fgg@gdg�g�gh3heh�h�h�hiBivi�i�ij�j�k�k-lRl}l�l�l�lRm�m�m"nXnin�n�n!oAojo�o�odpdq�q�q�q;rtr�r�rs'sGsks�s�s�s�st1t|t�t�t�tu.udu{u�uviv�v
w�wxRx�xjy�yz�zH{�{�{]|�|�|�|�}q~�~Z~��E�\�����(�����V���ǂ�F�n�׃4�o��H���,�{�͆'�v����q�͈T����������\�����<�ލ��'�ǎK�m��������a���א�[�������;����8�f�v�����.�s�����$�^�����(�k���љ�[���R��9��� ����!��������m����ޢ-����)�c����x������h���=�x���ר��V����n�Ī	�u���x��:���
�P��h�����¯��9�h���!���ٱ%�j����:�����#�|�ص*�i��h�˷��P������ ���5����}����3��������4�m�ѿ �d����B�����d���9�����0������b���>���M�����K�~���(�U�������6�������������(����j������H�|������T������9�����3�e����S�������������v���W�i�����)�������S����J�����G�����"�����3�k���=����� ���3�{�����
�4�������R���%�m���2�����1�n����� ������^����l�������>�{������������;�c������� �N�������+�C�}������9�m�����G�q�����#�c�����*�R���������;�t�����-�Y������L��������(�P�r����c��������B�^�������s��������������"�%�(�+�.�1�4�7�:�=�@�C�F�I�L�O�R�U�X�[�^�a�d�g�j�m�p�s�v�y�|������������������������������������!$'*-0369<?BEHKNQTWZ]`cfilor���������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}���������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%x��Iq�������<���E��#�	�	�	�	.
h
�
��/
T
�
�
�
�
�
�
/258;>ADGJMPSVY\_behknqtwz}�������������GJMPSVY\_behkn����������������������#x{~������������������������������������������� #&),/258;>ADGJMPSVY\_behknqtwz}�������������������������������������������

"%(+.147:=@CFILORUX[^adgjmpsvy|�������������	!$'*-0369<?BEHKNQTWZ]`cfilorux{~�����������������'*-�������������������������a�,�&T�Bq���@CXo��An
7m��Azg�~�; � � � F!�!�!,"/"2"I"L"O"R"U"X"["#Z#�#$8$j$�$%?%c%|%�%�%v&�&�&�&�'M(�($)^)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)�)********** *#*&*)*,*/*2*5*8*;*>*A*D*G*J*M*P*S*V*Y*\*_*b*e*h*k*n*q*t*w*z*}*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*�*+++x+{+~+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+�+,,,,,,,,,, ,#,&,),,,/,2,5,8,;,>,A,D,G,J,M,P,S,V,Y,\,_,b,e,h,k,n,q,t,w,z,},�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,�,---
-
-------"-%-(-+-.-1-4-7-:-=-@-C-F-I-L-O-R-U-X-[-^-a-d-g-j-m-p-s-v-y-|--�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-�-Q.�.�.C/�/�/0P0�0�0�01f1�1�1�1�12T2�2�2�2353x3�3�3�3414U4�4�4�4[5y5�5�5�56h6�6�6+7J7�7�708�89Q9l9�9�9�9�9G:�:�:.;\;y;�;8<s<�<�<�<�<�<�<�<�<�<�<�<�=�=�=L>O>t>�>�>?=?e?�?�AB.BsB�B�C�DE&EUE|EE�E�EGcG�H�H�HICIpI�I�I�I�I�I�I�I�I�I�I�IJJ:J=JrJuJ�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J�J%K(K+K.K1K4K7K:K=K@KCKFKIKLKOKRKUKXK[K^KaK�K�K�KL!L�L�L�L�L�L�L�L�LMMM
M
MMMMMM~M�MDN�N�N�N�N�NODOsO�O�O�O�O;PfP�P�PxQ{Q~Q�Q�Q�Q�Q�Q�Q�Q�Q�QRRSSSLS�S�TiU�U�VIW�W�XYY@YcZ�Z`[�[�[�[�\�\@]T]d]�]�]�]�]^b^�^�^
__<_�_V`�`�`�`a7afa�a�ab-b�bchcjc�cd\d�de~e�e�e�e�ef fDf�f�f�f�g�gIhsh�h�h�hiTi�i�i/jjj�jkVk�kl6lYlwl�l�l�l%mXmvm�m�m�m�mnRnUnXn[n^nandngnjn�n!o�o�o�o[p�paq�q�q*rVr�r�r4s�s�sEt�t.u�u�uvnv�v�v_w2xYx�x�xy`y�y�yz>zaz�z'{�{S|�|�}~u~�~$����h������
�
���́��'�B�v�-�m�p���ǃ׃�#�X���ڄ������g������-���ˇ(���Ȉ�C���0�z��9�����O�������X���:����X����:�����x���Βt�����C�������T���ĕ��.���ݖ�>�v�����
�9���ʘ���;���˙�:�r�����Қ��"�R���ڛ!���ݝ0�����d�ʟj��`��!�p�ȢV�ģ�s�����Τ�E�_�����ڥ`���Φ�A�W�ŧ�E�z���r�(�Q���ݪ��9�X����)�{����<����0������u��R��B�m����;�������/�O�p�ҳ!�n����j���е�S�ȶ����%�^���ݸ��������ڹ�m�ߺ"�Z���̼���B�t�žF�����*������5�_�~�t���������G�x�{���h�2���.�����5����L���O���'���#�x���(�]���%�f������}���o���5�����.�p���������5���$�P�S�v�������������������������������������l�����������x�����	�+�.�Q�r������D�������I�q���/���P���O�����D���4���P����j����e����V�����T�~���������������������������������������������������������������������������*�r�����.�n������x���J��������������=�[���
�?�[�������u�/�����Y���������0�����8�F�I�L�O���� �e�P���-kn���A���W�J�:�X�.`�9	�	�	�
X�h.
�
}��W�8��M��<�B��1r�K�h�b�T�}�"�< � � � "!m!�!|"k#�$b%y&�&�'(�(/)w)�)�)�)*G*�*+3+m+�+�+�+�+,�,&.C.j.�.�./:/u/�/$0�0�0B1�1�1�346�6=7k7�7]8�8�9?:�:�:1;|;<]<�<y=>m>�>�>�>�>f?�?�?�?�?Z@�@�@�@�@�AvBC9C�C�CDID�D�DlE�EF|F�F8G�G5H�H�ITJ,KLML~L�LMUM�M�M�MN-N`N�N�N�N�OPdP�P�P(QNQmQ�Q�QRGR�RUST�T�W�Y&ZWZ�Z�Z[~[�[+\d\�\�\�]E^�^�_'`�`ahama�a�ab�b�b%cIc�c�c6dpd�d�d�deKeke�e�e�e�e�e
ffuf#gwg�g)h�h�i�j@k%m7mGm�m�m�m�mn�n�ngo�o@p�p�p>q�q�q>r�r�rsjs�s[t�t�u6v�v�vwVwYwx�xyyy
z�z�z*{�{R|�|A}�}�}I~�~�~ ���$�M�q�ŀ��X����t�܂>����`����-�O�Z�m�����ȅӅ��:�U���h�ԇ�Q�q��e���ˉ�������%�T�����׌���S���܎�m���>������y�|�ْ-�����u��������hashchkisamchkNOYESKan inte skapa filen '%-.200s' (Felkod: %d - %s)Kan inte skapa tabellen '%-.200s' (Felkod: %d - %s)Kan inte skapa databasen '%-.192s' (Felkod: %d - %s)Databasen '%-.192s' existerar redanKan inte radera databasen '%-.192s'; databasen finns inteFel vid radering av databasen (Kan inte radera '%-.192s'. Felkod: %d - %s)Fel vid radering av databasen (Kan inte radera biblioteket '%-.192s'. Felkod: %d - %s)Kan inte radera filen '%-.192s' (Felkod: %d - %s)Hittar inte posten i systemregistretKan inte läsa filinformationen (stat) från '%-.200s' (Felkod: %d - %s)Kan inte inte läsa aktivt bibliotek. (Felkod: %d - %s)Kan inte låsa filen. (Felkod: %d - %s)Kan inte använda '%-.200s' (Felkod: %d - %s)Hittar inte filen '%-.200s' (Felkod: %d - %s)Kan inte läsa från bibliotek '%-.192s' (Felkod: %d - %s)Kan inte byta till '%-.192s' (Felkod: %d - %s)Posten har förändrats sedan den lästes i register '%-.192s'Disken är full (%s). Väntar tills det finns ledigt utrymme... (Felkod: %d - %s)Kan inte skriva, dubbel söknyckel i register '%-.192s'Fick fel vid stängning av '%-.192s' (Felkod: %d - %s)Fick fel vid läsning av '%-.200s' (Felkod %d - %s)Kan inte byta namn från '%-.210s' till '%-.210s' (Felkod: %d - %s)Fick fel vid skrivning till '%-.200s' (Felkod %d - %s)'%-.192s' är låst mot användningSorteringen avbrutenFormulär '%-.192s' finns inte i '%-.192s'Fick felkod %d - '%-.192s' från databashanterarenTabellhanteraren for tabell '%-.192s' stödjer ej dettaHittar inte posten '%-.192s'Felaktig fil: '%-.200s'Fatalt fel vid hantering av register '%-.200s'; kör en reparationGammal nyckelfil '%-.192s'; reparera registret'%-.192s' är skyddad mot förändringOväntat slut på minnet, starta om programmet och försök på nytt (Behövde %d bytes)Sorteringsbufferten räcker inte till. Kontrollera startparametrarnaOväntat filslut vid läsning från '%-.192s' (Felkod: %d - %s)För många anslutningarFick slut på minnet.  Kontrollera om mysqld eller någon annan process använder allt tillgängligt minne. Om inte, försök använda 'ulimit' eller allokera mera swapKan inte hitta 'hostname' för din adressFel vid initiering av kommunikationen med klientenAnvändare '%-.48s'@'%-.64s' är ej berättigad att använda databasen %-.192sAnvändare '%-.48s'@'%-.64s' är ej berättigad att logga in (Använder lösen: %s)Ingen databas i användningOkänt kommandoKolumn '%-.192s' får inte vara NULLOkänd databas: '%-.192s'Tabellen '%-.192s' finns redanOkänd tabell '%-.129s'Kolumn '%-.192s' i %-.192s är inte unikServern går nu nedOkänd kolumn '%-.192s' i %-.192s'%-.192s' finns inte i GROUP BYKan inte använda GROUP BY med '%-.192s'Kommandot har både sum functions och enkla funktionerAntalet kolumner motsvarar inte antalet värdenKolumnnamn '%-.100s' är för långtKolumnnamn '%-.192s finns flera gångerNyckelnamn '%-.192s' finns flera gångerDublett '%-.192s' för nyckel %dFelaktigt kolumntyp för kolumn '%-.192s'%s nära '%-.80s' på rad %dFrågan var tomIcke unikt tabell/alias: '%-.192s'Ogiltigt DEFAULT värde för '%-.192s'Flera PRIMARY KEY användaFör många nycklar använda. Man får ha högst %d nycklarFör många nyckeldelar använda. Man får ha högst %d nyckeldelarFör lång nyckel. Högsta tillåtna nyckellängd är %dNyckelkolumn '%-.192s' finns inteEn BLOB '%-.192s' kan inte vara nyckel med den använda tabelltypenFör stor kolumnlängd angiven för '%-.192s' (max= %lu). Använd en BLOB inställetDet får finnas endast ett AUTO_INCREMENT-fält och detta måste vara en nyckel%s: klar att ta emot klienter
Version: '%s'  socket: '%s'  port: %d%s: Normal avslutning
%s: Fick signal %d. Avslutar!
%s: Avslutning klar
%s: Stänger av tråd %ld; användare: '%-.48s'
Kan inte skapa IP-socketTabellen '%-.192s' har inget index som motsvarar det angivna i CREATE INDEX. Skapa om tabellenFältseparatorerna är vad som förväntades. Kontrollera mot manualenMan kan inte använda fast radlängd med blobs. Använd 'fields terminated by'Textfilen '%-.128s' måste finnas i databasbiblioteket eller vara läsbar för allaFilen '%-.200s' existerar redanRader: %ld  Bortagna: %ld  Dubletter: %ld  Varningar: %ldRader: %ld  Dubletter: %ldFelaktig delnyckel. Nyckeldelen är inte en sträng eller den angivna längden är längre än kolumnlängdenMan kan inte radera alla fält med ALTER TABLE. Använd DROP TABLE iställetKan inte ta bort '%-.192s'. Kontrollera att fältet/nyckel finnsRader: %ld  Dubletter: %ld  Varningar: %ldINSERT-table '%-.192s' får inte finnas i FROM tabell-listanFinns ingen tråd med id %luDu är inte ägare till tråd %luInga tabeller angivnaFör många alternativ till kolumn %-.192s för SETKan inte generera ett unikt filnamn %-.200s.(1-999)
Tabell '%-.192s' kan inte uppdateras emedan den är låst för läsningTabell '%-.192s' är inte låst med LOCK TABLESBLOB fält '%-.192s' kan inte ha ett DEFAULT-värdeFelaktigt databasnamn '%-.100s'Felaktigt tabellnamn '%-.100s'Den angivna frågan skulle läsa mer än MAX_JOIN_SIZE rader.  Kontrollera din WHERE och använd SET SQL_BIG_SELECTS=1 eller SET MAX_JOIN_SIZE=# ifall du vill hantera stora joinsOkänt felOkänd procedur: %-.192sFelaktigt antal parametrar till procedur %-.192sFelaktiga parametrar till procedur %-.192sOkänd tabell '%-.192s' i '%-.32s'Fält '%-.192s' är redan använtFelaktig användning av SQL grupp functionTabell '%-.192s' har en extension som inte finns i denna version av MySQLTabeller måste ha minst 1 kolumnTabellen '%-.192s' är fullOkänd teckenuppsättning: '%-.64s'För många tabeller. MySQL can ha högst %d tabeller i en och samma joinFör många fältFör stor total radlängd. Den högst tillåtna radlängden, förutom BLOBs, är %ld. Ändra några av dina fält till BLOBTrådstacken tog slut:  Har använt %ld av %ld bytes.  Använd 'mysqld --thread_stack=#' ifall du behöver en större stackFelaktigt referens i OUTER JOIN.  Kontrollera ON-uttrycketTabell hanteraren kan inte indexera NULL kolumner för den givna index typen. Ändra '%-.192s' till NOT NULL eller använd en annan hanterareKan inte ladda funktionen '%-.192s'Kan inte initialisera funktionen '%-.192s'; '%-.192s'Man får inte ange sökväg för dynamiska bibliotekFunktionen '%-.192s' finns redanKan inte öppna det dynamiska biblioteket '%-.192s' (Felkod: %d %-.128s)Hittar inte funktionen '%-.128s' in det dynamiska biblioteketFunktionen '%-.192s' är inte definieradDenna dator, '%-.255s', är blockerad pga många felaktig paket. Gör 'mysqladmin flush-hosts' för att ta bort alla blockeringarnaDenna dator, '%-.255s', har inte privileger att använda denna MySQL serverDu använder MySQL som en anonym användare och som sådan får du inte ändra ditt lösenordFör att ändra lösenord för andra måste du ha rättigheter att uppdatera mysql-databasenHittade inte användaren i 'user'-tabellenRader: %ld  Uppdaterade: %ld  Varningar: %ldKan inte skapa en ny tråd (errno %d)Antalet kolumner motsvarar inte antalet värden på rad: %ldKunde inte stänga och öppna tabell '%-.192sFelaktig använding av NULLFick fel '%-.64s' från REGEXPMan får ha både GROUP-kolumner (MIN(),MAX(),COUNT()...) och fält i en fråga om man inte har en GROUP BY-delDet finns inget privilegium definierat för användare '%-.48s' på '%-.255s'%-.128s ej tillåtet för '%-.48s'@'%-.64s' för tabell '%-.64s'%-.16s ej tillåtet för '%-.48s'@'%-.64s' för kolumn '%-.192s' i tabell '%-.192s'Felaktigt GRANT-privilegium använtFelaktigt maskinnamn eller användarnamn använt med GRANTDet finns ingen tabell som heter '%-.192s.%-.192s'Det finns inget privilegium definierat för användare '%-.48s' på '%-.255s' för tabell '%-.192s'Du kan inte använda detta kommando med denna MySQL versionDu har något fel i din syntaxDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useAvbröt länken för tråd %ld till db '%-.192s', användare '%-.48s' (%-.64s)Kommunkationspaketet är större än 'max_allowed_packet'Fick läsfel från klienten vid läsning från 'PIPE'Fick fatalt fel från 'fcntl()'Kommunikationspaketen kom i fel ordningKunde inte packa up kommunikationspaketetFick ett fel vid läsning från klientenFick 'timeout' vid läsning från klientenFick ett fel vid skrivning till klientenFick 'timeout' vid skrivning till klientenResultatsträngen är längre än max_allowed_packetDen använda tabelltypen kan inte hantera BLOB/TEXT-kolumnerDen använda tabelltypen kan inte hantera AUTO_INCREMENT-kolumnerINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESFelaktigt kolumnnamn '%-.100s'Den använda tabelltypen kan inte indexera kolumn '%-.192s'Tabellerna i MERGE-tabellen är inte identiskt definieradeKan inte skriva till tabell '%-.192s'; UNIQUE-testDu har inte angett någon nyckellängd för BLOB '%-.192s'Alla delar av en PRIMARY KEY måste vara NOT NULL;  Om du vill ha en nyckel med NULL, använd UNIQUE iställetResultet bestod av mera än en radDenna tabelltyp kräver en PRIMARY KEYDenna version av MySQL är inte kompilerad med RAIDDu använder 'säker uppdateringsmod' och försökte uppdatera en tabell utan en WHERE-sats som använder sig av en nyckel. %sNyckel '%-.192s' finns inte in tabell '%-.192s'Kan inte öppna tabellenTabellhanteraren för denna tabell kan inte göra %sDu får inte utföra detta kommando i en transaktionFick fel %d - '%-.192s' vid COMMITFick fel %d - '%-.192s' vid ROLLBACKFick fel %d vid FLUSH_LOGSFick fel %d vid CHECKPOINTAvbröt länken för tråd %u till db '%-.192s', användare '%-.48s', host '%-.255s' (%-.64s)Tabellhanteraren klarar inte en binär kopiering av tabellenBinlog closed, cannot RESET SOURCEFailed rebuilding the index of  dumped table '%-.192s'Fel från master: '%-.64s'Fick nätverksfel vid läsning från masterFick nätverksfel vid skrivning till masterHittar inte ett FULLTEXT-index i kolumnlistanKan inte utföra kommandot emedan du har en låst tabell eller an aktiv transaktionOkänd systemvariabel: '%-.64s'Tabell '%-.192s' är trasig och bör repareras med REPAIR TABLETabell '%-.192s' är trasig och senast (automatiska?) reparation misslyckadesWarning:  Några icke transaktionella tabeller kunde inte återställas vid ROLLBACKTransaktionen krävde mera än 'max_binlog_cache_size' minne. Öka denna mysqld-variabel och försök på nyttDenna operation kan inte göras under replikering; Gör STOP SLAVE förstDenna operation kan endast göras under replikering; Konfigurera slaven och gör START SLAVEServern är inte konfigurerade som en replikationsslav. Ändra konfigurationsfilen eller gör CHANGE MASTER TOKunde inte initialisera replikationsstrukturerna. See MySQL fel fil för mera informationKunde inte starta en tråd för replikeringAnvändare '%-.64s' har redan 'max_user_connections' aktiva inloggningarMan kan endast använda konstantuttryck med SETFick inte ett lås i tid ; Försök att starta om transaktionenAntal lås överskrider antalet reserverade låsUpdateringslås kan inte göras när man använder READ UNCOMMITTEDDROP DATABASE är inte tillåtet när man har ett globalt läslåsCREATE DATABASE är inte tillåtet när man har ett globalt läslåsFelaktiga argument till %s'%-.48s'@'%-.64s' har inte rättighet att skapa nya användareFelaktig tabelldefinition; alla tabeller i en MERGE-tabell måste vara i samma databasFick 'DEADLOCK' vid låsförsök av block/rad. Försök att starta om transaktionenTabelltypen har inte hantering av FULLTEXT-indexKan inte lägga till 'FOREIGN KEY constraint'FOREIGN KEY-konflikt:  Kan inte skriva barnFOREIGN KEY-konflikt:  Kan inte radera faderFick fel vid anslutning till master: %-.128sFick fel vid utförande av command på mastern: %-.128sFick fel vid utförande av %s: %-.128sFelaktig använding av %s and %sSELECT-kommandona har olika antal kolumnerKan inte utföra kommandot emedan du har ett READ-låsBlandning av transaktionella och icke-transaktionella tabeller är inaktiveratOption '%s' användes två gångerAnvändare '%-.64s' har överskridit '%s' (nuvarande värde: %ld)Du har inte privlegiet '%-.128s' som behövs för denna operationVariabel '%-.64s' är en SESSION variabel och kan inte ändrad med SET GLOBALVariabel '%-.64s' är en GLOBAL variabel och bör sättas med SET GLOBALVariabel '%-.64s' har inte ett DEFAULT-värdeVariabel '%-.64s' kan inte sättas till '%-.200s'Fel typ av argument till variabel '%-.64s'Variabeln '%-.64s' kan endast sättas, inte läsasFel använding/placering av '%s'Denna version av MySQL kan ännu inte utföra '%s'Fick fatalt fel %d: '%-.512s' från master vid läsning av binärloggenSlav SQL tråden ignorerade frågan pga en replicate-*-table regelVariabel '%-.192s' är av typ %sFelaktig FOREIGN KEY-definition för '%-.192s': %sNyckelreferensen och tabellreferensen stämmer inte överensOperand should contain %d column(s)Subquery returnerade mer än 1 radOkänd PREPARED STATEMENT id (%.*s) var given till %sHjälpdatabasen finns inte eller är skadadCyklisk referens i subqueriesKonvertar kolumn '%s' från %s till %sReferens '%-.64s' stöds inte (%s)Varje 'derived table' måste ha sitt eget aliasSelect %u reducerades vid optimieringTabell '%-.192s' från en SELECT kan inte användas i %-.32sKlienten stöder inte autentiseringsprotokollet som begärts av servern; överväg uppgradering av klientprogrammet.Alla delar av en SPATIAL index måste vara NOT NULLCOLLATION '%s' är inte tillåtet för CHARACTER SET '%s'Slaven har redan startatSlaven har redan stoppatUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldAnvänder handler %s för tabell '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatField or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredFelaktigt index namn '%-.100s'Felaktigt katalog namn '%-.100s'Storleken av 'Query cache' kunde inte sättas till %lu, ny storlek är %luKolumn '%-.192s' kan inte vara del av ett FULLTEXT indexOkänd nyckel cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadTabell %-.100s använd med '%s' är inte uppdateringsbar'%s' är inte aktiverad; För att aktivera detta måste du bygga om MySQL med '%s' definieradMySQL är startad med %s. Pga av detta kan du inte använda detta kommandoColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementConfiguration file '%-.192s' is too bigMalformed file type header in file '%-.192s'Unexpected end of file while parsing comment '%-.200s'Error while parsing parameter '%-.192s' (line: '%-.192s')Unexpected end of file while skipping unknown parameter '%-.192s'EXPLAIN/SHOW can not be issued; lacking privileges for underlying tableFile '%-.192s' has unknown type '%-.64s' in its header'%-.192s.%-.192s' is not %sColumn '%-.192s' is not updatableView's SELECT contains a subquery in the FROM clauseView's SELECT contains a '%s' clauseView's SELECT contains a variable or parameterView's SELECT refers to a temporary table '%-.192s'In definition of view, derived table or common table expression, SELECT list and column names list have different column countsView merge algorithm can't be used here for now (assumed undefined algorithm)View being updated does not have complete key of underlying table in itView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION on non-updatable view '%-.192s.%-.192s'CHECK OPTION failed '%-.192s.%-.192s'%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0View text checksum failedCan not modify more than one base table through a join view '%-.192s.%-.192s'Can not insert into join view '%-.192s.%-.192s' without fields listCan not delete from join view '%-.192s.%-.192s'Operation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntaxfel: %-.64s PARTITIONering kräver definition av VALUES %-.64s för varje partitionEndast %-.64s partitionering kan använda VALUES %-.64s i definition av partitionenMAXVALUE kan bara användas i definitionen av den sista partitionenSubpartitioner kan bara vara hash och key partitionerSubpartitioner måste definieras på alla partitioner om på enAntal partitioner definierade och antal partitioner är inte likaAntal subpartitioner definierade och antal subpartitioner är inte likaKonstanta uttryck eller slumpmässiga uttryck är inte tillåtna (sub)partitioneringsfunktionerUttryck i RANGE/LIST VALUES måste vara ett konstant uttryckFält i listan av fält för partitionering med key inte funnen i tabellenEn lista av fält är endast tillåtet för KEY partitionerPartitioneringsinformationen i frm-filen är inte konsistent med vad som kan skrivas i frm-filen%-.192s-funktionen returnerar felaktig typFör %-.64s partitionering så måste varje partition definierasVärden i VALUES LESS THAN måste vara strikt växande för varje partitionVärden i VALUES måste vara av samma typ som partitioneringsfunktionenMultipel definition av samma konstant i list partitioneringPartitioneringssyntax kan inte användas på egen hand i en SQL-frågaDenna mix av lagringsmotorer är inte tillåten i denna version av MySQLFör partitioneringsmotorn så är det nödvändigt att definiera alla %-.64sFör många partitioner (inkluderande subpartitioner) definieradesDet är endast möjligt att blanda RANGE/LIST partitionering med HASH/KEY partitionering för subpartitioneringMisslyckades med att skapa specifik fil i lagringsmotorEtt BLOB-fält är inte tillåtet i partitioneringsfunktionerA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Antal %-.64s = 0 är inte ett tillåten värdePartitioneringskommando på en opartitionerad tabell är inte möjligtForeign keys är inte ännu implementerad i kombination med partitioneringFel i listan av partitioner att %-.64sDet är inte tillåtet att ta bort alla partitioner, använd DROP TABLE iställetCOALESCE PARTITION kan bara användas på HASH/KEY partitionerREORGANIZE PARTITION kan bara användas för att omorganisera partitioner, inte för att ändra deras antalREORGANIZE PARTITION utan parametrar kan bara användas på auto-partitionerade tabeller som använder HASH partitionering%-.64s PARTITION kan bara användas på RANGE/LIST-partitionerADD PARTITION med fel antal subpartitionerÅtminstone en partition måste läggas till vid ADD PARTITIONÅtminstone en partition måste slås ihop vid COALESCE PARTITIONFler partitioner att reorganisera än det finns partitionerDuplicerat partitionsnamn %-.192sDet är inte tillåtet att stänga av binlog på detta kommandoNär ett antal partitioner omorganiseras måste de vara i konsekutiv ordningReorganisering av rangepartitioner kan inte ändra den totala intervallet utom för den sista partitionen där intervallet kan utökasPartition function not supported in this version for this handlerPartition state kan inte definieras från CREATE/ALTER TABLE%-.64s stödjer endast 32 bitar i integers i VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartitionskonstanten är utanför partitioneringsfunktionens domänDenna partitioneringsfunktion är inte tillåtenError in DDL logDet är inte tillåtet att använda NULL-värden i VALUES LESS THANFelaktigt partitionsnamnTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine inte användas i en partitionerad tabellCannot activate '%-.64s' logThe server was not built with row-based replicationAvkodning av base64 sträng misslyckadesRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionDublett '%-.64s' för nyckel '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesDetta är inte säkert att logga i statement-format, för BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabasTabellPartitionSubpartitionTemporärNamnändradToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerMisslyckades läsa från .par filenVärden i VALUES för partition '%-.64s' måste ha typen INTAnvändare '%-.48s'@'%-.64s' är ej berättigad att logga inSET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Attributet '%-.64s' är olika mellan partition och tabellTabellen att byta ut mot partition är partitionerad: '%-.64s'Tabellen att byta ut mot partition är temporär: '%-.64s'Subpartitionerad tabell, använd subpartition istället för partitionOkänd partition '%-.64s' i tabell '%-.64s'Tabellerna har olika definitionerHittade en rad som inte passar i partitionenOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Tabellen att byta ut mot partition har foreign key referenser: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () klausul för en icke partitionerad tabellHittade en rad som inte passar i någon given partitionDet finns ingen partition som heter '%-.64s'Failure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index stöds ej för partitionerade tabeller.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera barntabell '%.192s' på grund av nyckel '%.192s'FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera en barntabell på grund av UNIQUE-testSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionDublett för nyckel '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Hittade en rad i fel partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\k����ukrainian/errmsg.sysnu�[�������h�t�S�e�N��2�u�`�Hp�	^	�	�	7
�
�
V�2S�
:j�_���Hr��6T�b��=���S�x�3�5�Iv��3a�X���A3�.z�+S~�! � � Q!�!�!�"�"##s#�#�#$e$�$+%W%�%&1&�&�'+(�(�(.)�)�)>*�*�*�+�+�,R-�-./�/�/0U0�0b1�1d23Q3�34s4�4�45�5�5(6Y6�6�6N7�78_8�89k9�9�9n:�:);�;R<�<�<N=>\>�>�>'?k?�?�?)@�@AuA�A	BRB�BC�C�CRD�DwEcF�F�G4H�HI�I�I.J�J"K�K>LfL�L*MmM�M�M1NvN�N�N�NOAO�O�O�O)PjP�P�P,QeQ�Q�Q�QR[R�R�R�R(SjS�S�STET~T�T�T$UeU�U�U+VFVgV�V�VOWjW�W�WXRX�X�X�XYAY�Y�Y�YLZhZ[�["\k\*]g]�]�]1^c^^�^_Z_�_�_A`v`�`aIa�a�a�a�a1bVb�b�b�bc%c:cQcoc�c�c�cd&dMd�d'eGe�e�e�e�e�ef4fKf^fvf�f�f�f�fg*g@g]g�g�gh"hrh�h
ili�i[j�j�jkQk�k�klylm�m#n_n�n�n�n�no>okoyo�o�oFp�p�pq6q[q|q�q�q�qr&rQrrr�r�rs-sXs�s�s�st-t�tHu�ujv�v�v�v2wmw�w�wTx�x�x�x�x=yyy�y�yzCz�z�z{�{�|-}�}�}~g~�~�~o��O����\�����=�d������	������˄�m����<���Ԇ�u���������6�������H�r���������9�����ǋ>��ތ'���ȍ��4�t�����^���я�b���Ð	�A�{�����;�v�ؒ��1���͓
�Q�w����B����%�J�s���̖�I�����7�r�����ۘ
��0�f�����R���
�,�i�������ޛ�C�^�~�؜�?�h������7�v���	�����F���Ơ��$�5�g���С9�U�����ݢ�2�v�֣��-�_���>�|�����:�r��s���ק=�M�h�������ި
�C������/�f���̪�Q�z���˫�T��������O�����"���ˮ��2�e�������+�5�=�e�����ް�1�\�������4�M�����%�]�����γ�a����l����l��������źc���'����%�������!�]������j����!�\�}�����q�����E�����*�r���H���m���2�m������/�K�������{�4�����
�
�`�����)�a����H�������#�E�s���Z�������F���.�m�������+�k�����y�6�9�q�������n���=�z��������
�s������/���(����9�����?��������������a�����������1�p���*�A�X�������:�j��������0�T�q��������4�s���2������l������t���M�����]�}���y�����F���������
�,�l������G�������E��Y���m����U����%�o��*�v�����+�����
a����G��
��.l�Y�	j	�	�	)
S
�
�
$7V��o
�
�
d�2u��B���/v�f���<h���*U��U�'_������^r��:g��-r�*~�$����� C!�!�!$#�#�#6$�$^%�%&U&�&�&'k'�'�'$(n(�(�(>)~)�)R*�*+�+�+,$,G,a,�,�,�,-?-l-�-4.a.�.�.!/w/0S0q0�0%1k1�1�132u2�2)3D3�3!4Z4�4�4%5h5�5�56N6�67N7r7�7�7�7$8a8x8�8�8�8g9�9:h:k;�;�;�;)<<�<�<�<W=y=�=h>�>,?~?�?@�@.A�A*BIB�B�BC\CrC�C�C�C�D�DPE|E�EFFF\FsF�F�F
GG-GCGhG�G�G�G�H-I\I�IJ�J3KyK�KL�LkM�M
N^N�N�NOFOpO�O�O�OPNPoP�PQ<QyQ�Q/RaR�RoS�S�S�S
T&TUT�T�TUHUsU�U�UMV�V�VWRW�WX}X�XYqY�Y�YZ/ZjZ�Z�Z[/[E[R[X[�[�[\b\�\
]=]�]�]-^Y^�^�^T_�_�_j`�`�a/bgb�b�b�bLc�c�cdKd�d.e�e�e�eNf�f�f-ggg�ghih�h�hiVi�i�i)j�j�j�jkdk�k�kl?l�l�l)mRm�m�m�m4n�n�n oqopSp�p�p�p>qzq�q<rjr�rJshs�st�t�u)v�v�w�w�wx?xQxjx�x�x�xy;yYysy�y�yzKzxz�z�z3{j{�{�{c|�|2}l}�}�}P~y~�~X�D�x���Ԁ�C�w�ҁ�/�m���ނ�n���Ѓ�ń���X�����.�T����:�t����a���Èo�1������)�;�'�[����a�َ�������G���ߑ
�9�������d���I���ؗ�i���5�b�͙�=�h�����A���͛3�ќ#�k�����K�������D�ʠ�{�ߡi��7���ͣ����Ԥ�E�w�ʥ@����O����(�J��¨����٫�����.�i����^���۰�G�}���*�w��������}��9�v�������}�Ͷ=�����-���и/�q����3�U�������"�w������q���h�����
�J���ο)�L�����P������8�x����p�������j�������;�����)�����U���!�C�r��)�d�����Y������<�����~���/�`����T������7���!���a���*�W���������n���*����*���J�����?�����U�����	�G�q���a����J������~���N�����*�X�/������W���P����z������C���G�v�@�y�������u�/���!�k�������!���d���O�~����6�e���~�$�P���P���]��g����^�J�v�����s����l����W��
�@������L�O�l�{��p�J����L�E	�	9
f
�
�
M�2�)
�
h��@w��[�V��v�nq�W�*�j�B�F�$��+�.��5��$� u!�!&"d"�#�#L$�$2%U%�%�%�%&�&'.'R'}'�'(.(W(y(�()t)�)�)*y*�*m+�+!,y,�,-p-�-�-6.�.�.�/�/0I0�0F1�1C2#3b3�3�3�34*4<4�4�4�4
5O5�5�596S6�6+7S7�7�778^8�8�8�8"9J9t9�9�9�9:J:�:a;�;�;�;<9<g<�<�<�<=>=B=x=�=�=*>e>�>�>N?�?�?�?;@c@�@�@�@?A[A�A�A�AB@B�B�B.CmC�CFD�D�E�E�E(F�F�F'GmGH]H�HIDIvI�I�I�I
JFJ�J,K�K+L�L�LsM�M�MNRN�N�N0OUO�O�O.PdP�P�PQ&QTQ]QhQ�Q�Q*R~R�R�R	SS#S.SuS�S�ST#T5TZT}T�T�T2UhU�U�U
VeV�V�V�V�VbW�W�WX4X�X�XZ[Z�Z'[o[I\�\^]�]�]�]�]'^O^k^�^�^_`\`~`�`
a<a�a�a�a6beb�b�bScTd�d�d�dYe�e�ef.f[f�fgAg�g�ghZh�h�h�hi4i_i�i�ij%jdj�j�jk;kpk�k�k
ll&l6lTl�ln$n[n�n}oQp�p�p�p
qLq~q�q�qr3rUrvr�r�rs2sEs\sws�s�s&t]t�t�tu%u@upu�u�u�uv=vjv�v�v�v wCwlw�w�wx8xYxmx�x�xyJy�y�y$zWz�z�z�z{%{L{r{�{�{�{|`|�|�|J}�}~H~�~�~?�?�y���{��)�Â���#�܅8�n�����V����3�Z�ň�)���J���9����i���ь�6�M�u������8�g�����C�����������O����m���ʒ��P���ݓ-�u���N�y��(�T����4�t���ݗ���˙u�Y���ě���0�G���������<�o��������֟�4�u���á�8�����Ƣ�ߣ��Ĥ
�D�v���,�b���ަ�v���K�y����M���٩*�~���Ӫ��S�����Ȭ�G�����_�~���&�L�_���د�:�d����-�\����5�{����<���k���^���Ƶ��&�b��¶��P�l�����x���Ǹ�:�b���ù��V�����>�Y������
�p�+�I�i���ٽ9���˿�h�����j������#� �V�|��������s��� ���������	�C�����6�m������������N�|�'�=��������U�t���Q�;�m���F���1�����q���F�^�z������������2���������6�x�����.����������0�b��������J�o���1�`������Q����k������I�t�����X�������H���!�N������S�������������b���B����������� �>�r��������d���6������q������8�d�����/�d�{�������@�h��������:�n�����7�b����������5�`�������'�R�y������=�Z������	�������/��������'�W����3�R�o�������F�m������+�B�Y�������:�g�������@�|�����9y��=_���E���U��l��2\u���	{�
7�����K	t	�	
|
�
��w��/
b
!a�F��1x��)`��I���M��a�A`���F��Z{<ait���a�z��T��%>w�p# � � � �!�!1"Y"�"%#E#f$�$�$�$'%�%-&�&�&+'Y'j'�'�'�(�(�)�)�*�*+W+�+�+	,�,�,-=-{-�- .].j.�.�.�.�/�/0�0�01W1�1�1�1
2=2t2�2�2�2�2)3�3-4^4�4�586<6o6�6�67w7�7Y8�8�8)9s9�9�9:;::�:�:;l;�;�;-<s<�<�<@=m=�=�=�=J>�>�>I?�?�?�?�?1@r@�@�@�@AnA�A�ALBvB�B�BCACiC�CD=D`D�D�D�D/E~E�E�EF
F`F�FgG�GFH�H.IMIcI�I�IZJ�J2KuK�KLSL{L�L!M9M�MN�NMO�O:PaPP�P�P�P�P�P�P�P�P"Q%Q8Q�Q�QRRFRgR�R�R�R�RQS�S$T�T�TU/UMU�U�UV:VoV�V
WbW�W�WXQX�X"Y�Y�Z[C[x[�[�\�\]3]W]�]�]�]�]^U^�^�^�^�^"_J_e_�_�_�_�_�_�_%`\`�`�`�`�`*aSa�a�a�a�a#b]b�b�b�bc*cOcvc�c�c$dpd�d�deLe�e�ef6fPfsf�f�fg=gzg�g�gh6hbh|h�h�h2i�i�i�i�i%jtj�j�jk-kZk�k�k�kl%l=lXl[lm_m0n�n�n�n!odo�o�o�opMp�p�p�pq^q�q�q�qr0rPrpr�r�r�rs=s[svs�s�st;t�t�t�t�t�t�tu/uru�u�uvev�vwWw{w�w�w�w�w�w�wwx�x�xyVyoz{K{�{�|�}�}?~]~�~�~3Br���/�`�������X�����߁��%�j����Q�������ك���K�j���΄	�1�s����"�U�{�����U�v�������;�c�����$�J�q�����ˉމ	�3�M�r������G�e���ċ��:�t�����@����_��������0�����!�T�������S�s���͒��������� �m�����:�Y�y�������)�E�c����� �D�`������G���ԙ<���B���������N��z�Ȟ-���Ɵ��#����-�N�������)�w������M�Z�٤�N�������G�x���	�f����z��^�����Y���ܪ=��������K�ŭ:������گ(�n��1�Y���}���Ų�)�P���ٳ	�J���ʴ�/�m��8�j��������=�`���º+�V����)�Z���ټ�Q�������k�޿R��$�S���(���#���E����_���%�[��������*���:�����o�����	�-�����F�����;����=����l���<���K����������J�k�����S����W������l�����U���
�\�����������������R���#�g���D������e���6���(�f����R�����6�t���+�����k����b�����I�����p������*�}���0�Z��������h���������-�Z���N������@�z������J������9�k���*�e���	�Q����������1���������!�[��4��>���	�G|�/y�T� e�
o�Re��<f��)	�	�	W
�
�
d�0c��
R
�
�
6��M���+p����)Pm���
R���]u��:k��
y�	#U��\���"/m��2_��IL~���0Z���N��H�:t��� H � � � 
!�!B"E"H"K"N"Q"T"W"Z"]"`"c"f"i"l"o"r"u"x"{"~"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"�"P#S#V#Y#\#_#b#e#h#k#n#q#t#w#z#}#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#�#$$$
$
$$$$$$$"$%$($+$.$1$4$7$:$=$@$C$F$I$L$O$R$U$X$[$^$a$d$g$j$m$p$s$v$y$|$$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$�$I%L%O%R%U%X%[%^%a%d%g%j%m%p%s%v%y%|%%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%�%&&&	&&&&&&&&!&$&'&*&-&0&3&6&9&<&?&B&E&H&K&N&Q&T&W&�&�&'P'{'�'�'�'�'�'�'�'#)F)n)�)*"*w*�*+U+�+I,�,�,!-`-�-�-�./0a0�0�0!1$1'1*1-1a1d1g1j1m1p1s1v1y1|11�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1�1y2|22�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�2�233U3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3�3444
4
4444444"4%4(4+4.4144474:4=4@4C4F4I4L4O4R4U4X4[4^4a4d4g4j4m4p4s4v4y4|44�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4�4555	55555555!5$5'5*5-505356595<5?5B5E5H5K5N5Q5T5W5Z5]5`5c5f5i5l5o5r5u5x5{5~5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�5�566666 6#6&6)6,6/6265686;6>6A6D6G6J6M6P6S6V6Y6\6_6b6e6h6k6n6q6t6w6z6}6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6�6Y7\7_7�7�7�7�7�7�7�7�7�7�7888
8
8888888"8%8(8+8�8�8^9�9;X;�;�;3<t<�<�<�<'=r=u=�=�=�=�=4>s>�><?i?�?�?�?=@s@�@CA�A�A�B�BmC+D.D1DxD�D0E^EaEdE{E~E�E�E�E�E�E:F�F�F@GjG�G
H:HqH�H�H�H.I�I�I�I1JKK�KVL�L�L�L�L�L�L�L�LMMM
M
MMMMMMM"M%M(M+M.M1M4M7M:M=M@MCMFMIMLMOMRMUMXM[M^MaMdMgMjMmMpMsMvMyM|MM�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�M�MNNN	NNNNNNNN!N@NCNFN�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�N�NOOO
O
OOOOOOO"O%O(O+O.O1O4O7O:O=O@OCOFOIOLOOOROUOXO[O^OaOdOgOjOmOpOsOvOyO|OO�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�O�OPPP	PPPPPPPP!P$P'P*P-P0P3P6P9P<P?PBPEPHPKPNPQPTPWPZP]P`PcPfPiPlPoPrPuPxP{P~P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�P�Q�QRuR�RS5S�S�S�S!TQT�T�T�T�TUAU�U�UV!VFVgV�V�V�VW8WcW�W�WX0X�X�X�X�XY7Y�Y�Y!Z]Z|Z�Z[b[�[>\�\�\�\�\]1]y]�]1^`^�^�^�^j_�_�_�_�_�_�_�_�_```
`�`�`�`~a�a�a�a�aDbob�bc�dCe`e�e�e�f�g=hXh�h�h�h�hi5j�j�k�kl4lul�l�l�l�l�l�l�l�l�l�l�l!mKmNmlmom�m�m�m�m�mnnn	nnnnnnnn!n$n'nWnZn]n`ncnfninlnonrnunxn{n~n�n�n�n�n�n�n�noo-oPoSopp!p$p'p*p-p0p3p6p9p<p?pBpEpHpKpNp�p�pvqrr
r
rrLrvr�r�r�rs(sms�s�st�t�t�t�t�t�t�t�t�t�t�t�t:u=uIvLvOv~vw�w�x�x�y{z�z�{5|J|r|�}~�~�~�~�'�r���������)�E�����?�M�n����Ƀ�!�@�i���Ǆ��7�_���C������F����P�����È��5�R�v�Ɖ܉�Ȋ�{�������E������a���ˍD����C�h�����ÏƏ�W�����ϐ���P��������������������S����%��������"�\������f��w��`���M����-���d���̛�3���Ü'�O�p���!�Y�	������4���!�V�ɢޢ��H���ͣ��<�?������7�Y�t���_���������	��U������Q�¨�������&�_�����Z�����9�u��b����k�ܮ�J���ɯ5�������l�ܲ=���ݳ�l�̴�9�������߶+�u����+������(�`����F�p���̺ۺ?�k�����-�m�����K�l���ٽ��,�T������S���b��)����������"�S���������J���������w�������������3�s�����2�w����4���Z������.�k������[������n����b�����F������B�t����� �m������B�a������S�����A������A��������@�W���������������@����T�������H���t�����x�����\������"�g���������*�M���5�y���������d�)�`����g���9�~������Y���U����Z����W�����/�M������1�g���`��������+�g��V����������������"�%�(�+�.�1�4�7�:�=�@�C�F�I�����B�E�H�K�N�Q�����;�]�`�������N�v��IL#{��a����v�f/��C��>	�	�	:
�
�
.����������������������������

\��!
`
�
�
�
B�|�(+��Qo��?q����a������b��jx{~� � R!�!�"$1$_$�$�$�$�$*%s%�% &L&�&:'�'�'6(|(�(=)l)�)�*+`+�+�+k,�,-�-�.�.�/`0�0�12�2�3�3B4j4�455�5�6n7�7t89+:c:�:;};<�<=�=>=>@>�>�?�@EA�ATB�BnC�C�CDTD�D�D�E�F�G�H�I
J�JLKLaL�L�LM,MFMyM�M2NeN�N�N�NO*OKOPXQuQ�Q�QRIRlR�RSVS�STtT�T(UW7WKY�YoZ�Z[�[�[�\q]�]"^c^�^Q_�_�_�`5a�a�a�ab.b�b�b�b�b�b�c�c$d'd*de�e=fkf�fg3g{g�gh�hiFi�ijjj�jgkl�l�m^n3oo�opEp�p�p�pq:q_q�q�q�q"r�rDs�s�stZt�t�t�tu3uyu�u�vGw	x�z/}X}�}�}�}P~�~�~]��1�рw�
���Y��4�������B��	�W�{�ˆ�h���Ç��A�}�����و���<�O���U����[�ʋ�-�r�W�i�y���ѐ���L���%����r�͓%�p����p����C���Ζ������h���M�����H�ʛK���<����\�����ğs���{���R�Ǣ��-�V������#�O����:����p�Ц2����A�_���������ۨ����>�l�������8��������̬��1���E��W�����ܯ	�6����ڱ�7���زp��ӴC������_������P�-�ɹ1�hashchkisamchkНІТАКНе можу створити файл '%-.200s' (помилка: %d - %s)Не можу створити таблицю '%-.200s' (помилка: %d - %s)Не можу створити базу данних '%-.192s' (помилка: %d - %s)Не можу створити базу данних '%-.192s'. База данних існуєНе можу видалити базу данних '%-.192s'. База данних не існуєНе можу видалити базу данних (Не можу видалити '%-.192s', помилка: %d - %s)Не можу видалити базу данних (Не можу видалити теку '%-.192s', помилка: %d - %s)Не можу видалити '%-.192s' (помилка: %d - %s)Не можу зчитати запис з системної таблиціНе можу отримати статус '%-.200s' (помилка: %d - %s)Не можу визначити робочу теку (помилка: %d - %s)Не можу заблокувати файл (помилка: %d - %s)Не можу відкрити файл: '%-.200s' (помилка: %d - %s)Не можу знайти файл: '%-.200s' (помилка: %d - %s)Не можу прочитати теку '%-.192s' (помилка: %d - %s)Не можу перейти у теку '%-.192s' (помилка: %d - %s)Запис було змінено з часу останнього читання з таблиці '%-.192s'Диск заповнений (%s). Вичикую, доки звільниться трохи місця... (помилка: %d - %s)Не можу записати, дублюючийся ключ в таблиці '%-.192s'Не можу закрити '%-.192s' (помилка: %d - %s)Не можу прочитати файл '%-.200s' (помилка: %d - %s)Не можу перейменувати '%-.210s' у '%-.210s' (помилка: %d - %s)Не можу записати файл '%-.200s' (помилка: %d - %s)'%-.192s' заблокований на внесення змінСортування перерваноВигляд '%-.192s' не існує для '%-.192s'Отримано помилку %d - '%-.192s' від дескриптора таблиціДескриптор таблиці '%-.192s' не має цієї властивостіНе можу записати у '%-.192s'Хибна інформація у файлі: '%-.200s'Хибний файл ключей для таблиці: '%-.200s'; Спробуйте його відновитиСтарий файл ключей для таблиці '%-.192s'; Відновіть його!Таблиця '%-.192s' тільки для читанняБрак пам'яті. Рестартуйте сервер та спробуйте знову (потрібно %d байтів)Брак пам'яті для сортування. Треба збільшити розмір буфера сортування у сервераХибний кінець файлу '%-.192s' (помилка: %d - %s)Забагато з'єднаньБрак пам'яті;  Перевірте чи mysqld або якісь інші процеси використовують усю доступну пам'ять. Як ні, то ви можете скористатися 'ulimit', аби дозволити mysqld використовувати більше пам'яті або ви можете додати більше місця під свапНе можу визначити ім'я хосту для вашої адресиНевірна установка зв'язкуДоступ заборонено для користувача: '%-.48s'@'%-.64s' до бази данних '%-.192s'Доступ заборонено для користувача: '%-.48s'@'%-.64s' (Використано пароль: %s)Базу данних не вибраноНевідома командаСтовбець '%-.192s' не може бути нульовимНевідома база данних '%-.192s'Таблиця '%-.192s' вже існуєНевідома таблиця '%-.129s'Стовбець '%-.192s' у %-.192s визначений неоднозначноЗавершується работа сервераНевідомий стовбець '%-.192s' у '%-.192s''%-.192s' не є у GROUP BYНе можу групувати по '%-.192s'У виразі використано підсумовуючі функції поряд з іменами стовбцівКількість стовбців не співпадає з кількістю значеньІм'я ідентифікатора '%-.100s' задовгеДублююче ім'я стовбця '%-.192s'Дублююче ім'я ключа '%-.192s'Дублюючий запис '%-.192s' для ключа %dНевірний специфікатор стовбця '%-.192s'%s біля '%-.80s' в строці %dПустий запитНеунікальна таблиця/псевдонім: '%-.192s'Невірне значення по замовчуванню для '%-.192s'Первинного ключа визначено неодноразовоЗабагато ключів зазначено. Дозволено не більше %d ключівЗабагато частин ключа зазначено. Дозволено не більше %d частинЗазначений ключ задовгий. Найбільша довжина ключа %d байтівКлючовий стовбець '%-.192s' не існує у таблиціBLOB стовбець '%-.192s' не може бути використаний у визначенні ключа в цьому типі таблиціЗадовга довжина стовбця '%-.192s' (max = %lu). Використайте тип BLOBНевірне визначення таблиці; Може бути лише один автоматичний стовбець, що повинен бути визначений як ключ%s: Готовий для з'єднань!
Version: '%s'  socket: '%s'  port: %d%s: Нормальне завершення
%s: Отримано сигнал %d. Перериваюсь!
%s: Роботу завершено
%s: Прискорюю закриття гілки %ld користувача: '%-.48s'
Не можу створити IP роз'ємТаблиця '%-.192s' має індекс, що не співпадає з вказанним у CREATE INDEX. Створіть таблицю зновуХибний розділювач полів. Почитайте документаціюНе можна використовувати сталу довжину строки з BLOB. Зкористайтеся 'fields terminated by'Файл '%-.128s' повинен бути у теці бази данних або мати встановлене право на читання для усіхФайл '%-.200s' вже існуєЗаписів: %ld  Видалено: %ld  Пропущено: %ld  Застережень: %ldЗаписів: %ld  Дублікатів: %ldНевірна частина ключа. Використана частина ключа не є строкою, задовга або вказівник таблиці не підтримує унікальних частин ключейНе можливо видалити всі стовбці за допомогою ALTER TABLE. Для цього скористайтеся DROP TABLEНе можу DROP '%-.192s'. Перевірте, чи цей стовбець/ключ існуєЗаписів: %ld  Дублікатів: %ld  Застережень: %ldТаблиця '%-.192s' що змінюється не дозволена у переліку таблиць FROMНевідомий ідентифікатор гілки: %luВи не володар гілки %luНе використано таблицьЗабагато строк для стовбця %-.192s та SETНе можу згенерувати унікальне ім'я log-файлу %-.200s.(1-999)
Таблицю '%-.192s' заблоковано тільки для читання, тому її не можна оновитиТаблицю '%-.192s' не було блоковано з LOCK TABLESСтовбець BLOB '%-.192s' не може мати значення по замовчуваннюНевірне ім'я бази данних '%-.100s'Невірне ім'я таблиці '%-.100s'Запиту SELECT потрібно обробити багато записів, що, певне, займе дуже багато часу. Перевірте ваше WHERE та використовуйте SET SQL_BIG_SELECTS=1, якщо цей запит SELECT є вірнимНевідома помилкаНевідома процедура '%-.192s'Хибна кількість параметрів процедури '%-.192s'Хибний параметер процедури '%-.192s'Невідома таблиця '%-.192s' у %-.32sСтовбець '%-.192s' зазначено двічіХибне використання функції групуванняТаблиця '%-.192s' використовує розширення, що не існує у цій версії MySQLТаблиця повинна мати хочаб один стовбецьТаблиця '%-.192s' заповненаНевідома кодова таблиця: '%-.64s'Забагато таблиць. MySQL може використовувати лише %d таблиць у об'єднанніЗабагато стовбцівЗадовга строка. Найбільшою довжиною строки, не рахуючи BLOB, є %ld. Вам потрібно привести деякі стовбці до типу BLOBСтек гілок переповнено:  Використано: %ld з %ld. Використовуйте 'mysqld --thread_stack=#' аби зазначити більший стек, якщо необхідноПерехресна залежність у OUTER JOIN. Перевірте умову ONTable handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handlerНе можу завантажити функцію '%-.192s'Не можу ініціалізувати функцію '%-.192s'; %-.192sНе дозволено використовувати путі для розділюваних бібліотекФункція '%-.192s' вже існуєНе можу відкрити розділювану бібліотеку '%-.192s' (помилка: %d %-.128s)Не можу знайти функцію '%-.128s' у бібліотеціФункцію '%-.192s' не визначеноХост '%-.255s' заблоковано з причини великої кількості помилок з'єднання. Для розблокування використовуйте 'mysqladmin flush-hosts'Хосту '%-.255s' не доволено зв'язуватись з цим сервером MySQLВи використовуєте MySQL як анонімний користувач, тому вам не дозволено змінювати пароліВи повині мати право на оновлення таблиць у базі данних mysql, аби мати можливість змінювати пароль іншимНе можу знайти відповідних записів у таблиці користувачаЗаписів відповідає: %ld  Змінено: %ld  Застережень: %ldНе можу створити нову гілку (помилка %d). Якщо ви не використали усю пам'ять, то прочитайте документацію до вашої ОС - можливо це помилка ОСКількість стовбців не співпадає з кількістю значень у строці %ldНе можу перевідкрити таблицю: '%-.192s'Хибне використання значення NULLОтримано помилку '%-.64s' від регулярного виразуЗмішування GROUP стовбців (MIN(),MAX(),COUNT()...) з не GROUP стовбцями є забороненим, якщо не має GROUP BYПовноважень не визначено для користувача '%-.48s' з хосту '%-.255s'%-.128s команда заборонена користувачу: '%-.48s'@'%-.64s' у таблиці '%-.64s'%-.16s команда заборонена користувачу: '%-.48s'@'%-.64s' для стовбця '%-.192s' у таблиці '%-.192s'Хибна GRANT/REVOKE команда; прочитайте документацію стосовно того, які права можна використовуватиАргумент host або user для GRANT задовгийТаблиця '%-.192s.%-.192s' не існуєПовноважень не визначено для користувача '%-.48s' з хосту '%-.255s' для таблиці '%-.192s'Використовувана команда не дозволена у цій версії MySQLУ вас помилка у синтаксисі SQLDelayed insert thread couldn't get requested lock for table %-.192sToo many delayed threads in useПерервано з'єднання %ld до бази данних: '%-.192s' користувача: '%-.48s' (%-.64s)Отримано пакет більший ніж max_allowed_packetОтримано помилку читання з комунікаційного каналуОтримано помилкку від fcntl()Отримано пакети у неналежному порядкуНе можу декомпресувати комунікаційний пакетОтримано помилку читання комунікаційних пакетівОтримано затримку читання комунікаційних пакетівОтримано помилку запису комунікаційних пакетівОтримано затримку запису комунікаційних пакетівСтрока результату довша ніж max_allowed_packetВикористаний тип таблиці не підтримує BLOB/TEXT стовбціВикористаний тип таблиці не підтримує AUTO_INCREMENT стовбціINSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLESНевірне ім'я стовбця '%-.100s'Використаний вказівник таблиці не може індексувати стовбець '%-.192s'Таблиці у MERGE TABLE мають різну структуруНе можу записати до таблиці '%-.192s', з причини вимог унікальностіСтовбець BLOB '%-.192s' використано у визначенні ключа без вказання довжини ключаУсі частини PRIMARY KEY повинні бути NOT NULL; Якщо ви потребуєте NULL у ключі, скористайтеся UNIQUEРезультат знаходиться у більше ніж одній строціЦей тип таблиці потребує первинного ключаЦя версія MySQL не зкомпільована з підтримкою RAIDВи у режимі безпечного оновлення та намагаєтесь оновити таблицю без оператора WHERE, що використовує KEY стовбець. %sКлюч '%-.192s' не існує в таблиці '%-.192s'Не можу відкрити таблицюВказівник таблиці не підтримуе %sВам не дозволено виконувати цю команду в транзакціїОтримано помилку %d - '%-.192s' під час COMMITОтримано помилку %d - '%-.192s' під час ROLLBACKОтримано помилку %d під час FLUSH_LOGSОтримано помилку %d під час CHECKPOINTПерервано з'єднання %u до бази данних: '%-.192s' користувач: '%-.48s' хост: '%-.255s' (%-.64s)Цей тип таблиці не підтримує бінарну передачу таблиціРеплікаційний лог закрито, не можу виконати RESET MASTERНевдале відновлення індекса переданої таблиці '%-.192s'Помилка від головного: '%-.64s'Мережева помилка читання від головногоМережева помилка запису до головногоНе можу знайти FULLTEXT індекс, що відповідає переліку стовбцівНе можу виконати подану команду тому, що таблиця заблокована або виконується транзакціяНевідома системна змінна '%-.64s'Таблицю '%-.192s' марковано як зіпсовану та її потрібно відновитиТаблицю '%-.192s' марковано як зіпсовану та останнє (автоматичне?) відновлення не вдалосяЗастереження: Деякі нетранзакційні зміни таблиць не можна буде повернутиТранзакція з багатьма виразами вимагає більше ніж 'max_binlog_cache_size' байтів для зберігання. Збільште цю змінну mysqld та спробуйте зновуОперація не може бути виконана з запущеним підлеглим, спочатку виконайте STOP SLAVEОперація вимагає запущеного підлеглого, зконфігуруйте підлеглого та виконайте START SLAVEСервер не зконфігуровано як підлеглий, виправте це у файлі конфігурації або з CHANGE MASTER TOCould not initialize connection metadata structure; more error messages can be found in the MySQL error logНе можу створити підлеглу гілку, перевірте системні ресурсиКористувач %-.64s вже має більше ніж 'max_user_connections' активних з'єднаньМожна використовувати лише вирази зі сталими у SETЗатримку очікування блокування вичерпаноЗагальна кількість блокувань перевищила розмір блокувань для таблиціОновити блокування не можливо на протязі транзакції READ UNCOMMITTEDDROP DATABASE не дозволено доки гілка перебуває під загальним блокуванням читанняCREATE DATABASE не дозволено доки гілка перебуває під загальним блокуванням читанняХибний аргумент для %sКористувачу '%-.48s'@'%-.64s' не дозволено створювати нових користувачівIncorrect table definition; all MERGE tables must be in the same databaseDeadlock found when trying to get lock; try restarting transactionВикористаний тип таблиці не підтримує FULLTEXT індексівCannot add foreign key constraintCannot add or update a child row: a foreign key constraint failsCannot delete or update a parent row: a foreign key constraint failsError connecting to source: %-.128sError running query on source: %-.128sError when executing command %s: %-.128sWrong usage of %s and %sThe used SELECT statements have a different number of columnsCan't execute the query because you have a conflicting read lockMixing of transactional and non-transactional tables is disabledOption '%s' used twice in statementUser '%-.64s' has exceeded the '%s' resource (current value: %ld)Access denied. You need the %-.128s privilege for this operationVariable '%-.64s' is a SESSION variable and can't be used with SET GLOBALVariable '%-.64s' is a GLOBAL variable and should be set with SET GLOBALVariable '%-.64s' doesn't have a default valueVariable '%-.64s' can't be set to the value of '%-.200s'Incorrect argument type to variable '%-.64s'Variable '%-.64s' can only be set, not readIncorrect usage/placement of '%s'This version of MySQL doesn't yet support '%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replica SQL thread ignored the query because of replicate-*-table rulesVariable '%-.192s' is a %s variableIncorrect foreign key definition for '%-.192s': %sKey reference and table reference don't matchОперанд має складатися з %d стовбцівПідзапит повертає більш нiж 1 записUnknown prepared statement handler (%.*s) given to %sHelp database is corrupt or does not existЦиклічне посилання на підзапитПеретворення стовбца '%s' з %s у %sПосилання '%-.64s' не пiдтримуется (%s)Every derived table must have its own aliasSelect %u was скасовано при оптимiзацiiTable '%-.192s' from one of the SELECTs cannot be used in %-.32sClient does not support authentication protocol requested by server; consider upgrading MySQL clientAll parts of a SPATIAL index must be NOT NULLCOLLATION '%s' is not valid for CHARACTER SET '%s'Replica is already runningReplica already has been stoppedUncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)ZLIB: Not enough memoryZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)ZLIB: Input data corruptedRow %u was cut by GROUP_CONCAT()Row %ld doesn't contain data for all columnsRow %ld was truncated; it contained more data than there were input columnsColumn set to default value; NULL supplied to NOT NULL column '%s' at row %ldOut of range value for column '%s' at row %ldData truncated for column '%s' at row %ldUsing storage engine %s for table '%s'Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'Cannot drop one or more of the requested usersCan't revoke all privileges for one or more of the requested usersIllegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'Illegal mix of collations for operation '%s'Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)Unknown collation: '%-.64s'SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is startedServer is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new formatСтовбець або посилання '%-.192s%s%-.192s%s%-.192s' із SELECTу #%d було знайдене у SELECTі #%dIncorrect parameter or combination of parameters for START REPLICA UNTILIt is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restartSQL thread is not to be started so UNTIL options are ignoredIncorrect index name '%-.100s'Incorrect catalog name '%-.100s'Кеш запитів неспроможен встановити розмір %lu, новий розмір кеша запитів - %luColumn '%-.192s' cannot be part of FULLTEXT indexUnknown key cache '%-.100s'MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to workUnknown storage engine '%s''%s' is deprecated and will be removed in a future release. Please use %s insteadТаблиця %-.100s у %s не може оновлюватисьThe '%s' feature is disabled; you need MySQL built with '%s' to have it workingThe MySQL server is running with the %s option so it cannot execute this statementColumn '%-.100s' has duplicated value '%-.64s' in %sTruncated incorrect %-.64s value: '%-.128s'Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clauseInvalid ON UPDATE clause for '%-.192s' columnThis command is not supported in the prepared statement protocol yetGot error %d '%-.100s' from %sGot temporary error %d '%-.100s' from %sUnknown or incorrect time zone: '%-.64s'Invalid TIMESTAMP value in column '%s' at row %ldInvalid %s character string: '%.64s'Result of %s() was larger than max_allowed_packet (%ld) - truncatedConflicting declarations: '%s%s' and '%s%s'Can't create a %s from within another stored routine%s %s already exists%s %s does not existFailed to DROP %s %sFailed to CREATE %s %s%s with no matching label: %sRedefining label %sEnd-label %s without matchReferring to uninitialized variable %sPROCEDURE %s can't return a result set in the given contextRETURN is only allowed in a FUNCTION%s is not allowed in stored proceduresThe update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored.The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.Query execution was interruptedIncorrect number of arguments for %s %s; expected %u, got %uUndefined CONDITION: %sNo RETURN found in FUNCTION %sFUNCTION %s ended without RETURNCursor statement must be a SELECTCursor SELECT must not have INTOUndefined CURSOR: %sCursor is already openCursor is not openUndeclared variable: %sIncorrect number of FETCH variablesNo data - zero rows fetched, selected, or processedDuplicate parameter: %sDuplicate variable: %sDuplicate condition: %sDuplicate cursor: %sFailed to ALTER %s %sSubquery value not supported%s is not allowed in stored function or triggerVariable or condition declaration after cursor or handler declarationCursor declaration after handler declarationCase not found for CASE statementЗанадто великий конфігураційний файл '%-.192s'Невірний заголовок типу у файлі '%-.192s'Несподіванний кінець файлу у коментарі '%-.200s'Помилка в роспізнаванні параметру '%-.192s' (рядок: '%-.192s')Несподіванний кінець файлу у спробі проминути невідомий параметр '%-.192s'EXPLAIN/SHOW не може бути віконано; немає прав на тиблиці запитуФайл '%-.192s' має невідомий тип '%-.64s' у заголовку'%-.192s.%-.192s' не є %sСтовбець '%-.192s' не може бути зминенийView SELECT має підзапит у конструкції FROMView SELECT має конструкцію '%s'View SELECT має зминну або параметерView SELECT використовує тимчасову таблицю '%-.192s'View SELECT і перелік стовбців view мають різну кількість сковбцівАлгоритм зливання view не може бути використаний зараз (алгоритм буде невизначений)View, що оновлюеться, не містить повного ключа таблиці(ь), що викорістана в ньюомуView '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use themCan't drop or alter a %s from within another stored routineGOTO is not allowed in a stored procedure handlerTrigger already existsTrigger does not existTrigger's '%-.192s' is view or temporary tableUpdating of %s row is not allowed in %striggerThere is no %s row in %s triggerField '%-.192s' doesn't have a default valueDivision by 0Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ldIllegal %s '%-.192s' value found during parsingCHECK OPTION для VIEW '%-.192s.%-.192s' що не може бути оновленнимПеревірка CHECK OPTION для VIEW '%-.192s.%-.192s' не пройшла%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'Failed purging old relay logs: %sPassword hash should be a %d-digit hexadecimal numberTarget log not found in binlog indexI/O error reading log index fileServer configuration does not permit binlog purgeFailed on fseek()Fatal error during log purgeA purgeable log is in use, will not purgeUnknown error during log purgeFailed initializing relay log position: %sYou are not using binary loggingThe '%-.64s' syntax is reserved for purposes internal to the MySQL serverWSAStartup FailedCan't handle procedures with different groups yetSelect must have a group with this procedureCan't use ORDER clause with this procedureBinary logging and replication forbid changing the global server %sCan't map file: %-.200s, errno: %dWrong magic in %-.64sPrepared statement contains too many placeholdersKey part '%-.192s' length cannot be 0Перевірка контрольної суми тексту VIEW не пройшлаНеможливо оновити більш ниж одну базову таблицю выкористовуючи VIEW '%-.192s.%-.192s', що містіть декілька таблицьНеможливо уставити рядки у VIEW '%-.192s.%-.192s', що містить декілька таблиць, без списку стовбцівНеможливо видалити рядки у VIEW '%-.192s.%-.192s', що містить декілька таблицьOperation %s failed for %.256sXAER_NOTA: Unknown XIDXAER_INVAL: Invalid arguments (or unsupported command)XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s stateXAER_OUTSIDE: Some work is done outside global transactionXAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistencyXA_RBROLLBACK: Transaction branch was rolled backThere is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'Failed to grant EXECUTE and ALTER ROUTINE privilegesFailed to revoke all privileges to dropped routineData too long for column '%s' at row %ldBad SQLSTATE: '%s'%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %sCan't load value from file with fixed size rows to variableYou are not allowed to create a user with GRANTIncorrect %-.32s value: '%-.128s' for function %-.32sTable definition has changed, please retry transactionDuplicate handler declared in the same blockOUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE triggerNot allowed to return a result set from a %sCannot get geometry object from data you send to the GEOMETRY fieldA routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changesThis function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it.The statement (%lu) has no open cursor.Explicit or implicit commit is not allowed in stored function or trigger.Field of view '%-.192s.%-.192s' underlying table doesn't have a default valueRecursive stored functions and triggers are not allowed.Too big scale %d specified for column '%-.192s'. Maximum is %lu.Too-big precision %d specified for '%-.192s'. Maximum is %lu.For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s').You can't combine write-locking of system tables with other tables or lock typesUnable to connect to foreign data source: %.64sThere was a problem processing the query on the foreign data source. Data source error: %-.64sThe foreign data source you are trying to reference does not exist. Data source error:  %-.64sCan't create federated table. The data source connection string '%-.64s' is not in the correct formatThe data source connection string '%-.64s' is not in the correct formatCan't create federated table. Foreign data src error:  %-.64sTrigger in wrong schemaThread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack.Routine body for '%-.100s' is too longCannot drop default keycacheDisplay width out of range for column '%-.192s' (max = %lu)XAER_DUPID: The XID already existsDatetime function: %-.32s field overflowCan't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger.The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'.The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive mannerNot allowed to set autocommit from a stored function or triggerDefiner is not fully qualifiedView '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definerThe user specified as a definer ('%-.64s'@'%-.64s') does not existChanging schema from '%-.192s' to '%-.192s' is not allowed.Cannot delete or update a parent row: a foreign key constraint fails (%.192s)Cannot add or update a child row: a foreign key constraint fails (%.192s)Variable '%-.64s' must be quoted with `...`, or renamedNo definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer.'%-.192s' has an old format, you should re-create the '%s' object(s)Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192sFailed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)Incorrect routine name '%-.192s'Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!AGGREGATE is not supported for stored functionsCan't create more than max_prepared_stmt_count statements (current value: %lu)`%-.192s`.`%-.192s` contains view recursionNon-grouping field '%-.192s' is used in %-.64s clauseThe used table type doesn't support SPATIAL indexesTriggers can not be created on system tablesLeading spaces are removed from name '%s'Failed to read auto-increment value from storage engineuser namehost nameString '%-.70s' is too long for %s (should be no longer than %d)The target table %-.100s of the %s is not insertable-intoTable '%-.64s' is differently defined or of non-MyISAM type or doesn't existToo high level of nesting for selectName '%-.64s' has become ''First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BYThe foreign server, %s, you are trying to create already exists.The foreign server name you are trying to reference does not exist. Data source error:  %-.64sTable storage engine '%-.64s' does not support the create option '%.64s'Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partitionOnly %-.64s PARTITIONING can use VALUES %-.64s in partition definitionMAXVALUE can only be used in last partition definitionSubpartitions can only be hash partitions and by keyMust define subpartitions on all partitions if on one partitionWrong number of partitions defined, mismatch with previous settingWrong number of subpartitions defined, mismatch with previous settingConstant, random or timezone-dependent expressions in (sub)partitioning function are not allowedExpression in RANGE/LIST VALUES must be constantField in list of fields for partition function not found in tableList of fields is only allowed in KEY partitionsThe partition info in the frm file is not consistent with what can be written into the frm fileThe %-.192s function returns the wrong typeFor %-.64s partitions each partition must be definedVALUES LESS THAN value must be strictly increasing for each partitionVALUES value must be of same type as partition functionMultiple definition of same constant in list partitioningPartitioning can not be used stand-alone in queryThe mix of handlers in the partitions is not allowed in this version of MySQLFor the partitioned engine it is necessary to define all %-.64sToo many partitions (including subpartitions) were definedIt is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioningFailed to create specific handler fileA BLOB field is not allowed in partition functionA %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered).Number of %-.64s = 0 is not an allowed valuePartition management on a not partitioned table is not possibleForeign keys are not yet supported in conjunction with partitioningError in list of partitions to %-.64sCannot remove all partitions, use DROP TABLE insteadCOALESCE PARTITION can only be used on HASH/KEY partitionsREORGANIZE PARTITION can only be used to reorganize partitions not to change their numbersREORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs%-.64s PARTITION can only be used on RANGE/LIST partitionsTrying to Add partition(s) with wrong number of subpartitionsAt least one partition must be addedAt least one partition must be coalescedMore partitions to reorganize than there are partitionsDuplicate partition name %-.192sIt is not allowed to shut off binlog on this commandWhen reorganizing a set of partitions they must be in consecutive orderReorganize of range partitions cannot change total ranges except for last partition where it can extend the rangePartition function not supported in this version for this handlerPartition state cannot be defined from CREATE/ALTER TABLEThe %-.64s handler only supports 32 bit integers in VALUESPlugin '%-.192s' is not loadedIncorrect %-.32s value: '%-.128s'Table has no partition for value %-.64sIt is not allowed to specify %s more than onceFailed to create %sFailed to drop %sThe handler doesn't support autoextend of tablespacesA size parameter was incorrectly specified, either number or on the form 10MThe size number was correct but we don't allow the digit part to be more than 2 billionFailed to alter: %sWriting one row to the row-based binary log failedTable definition on source and replica does not match: %sReplica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log eventsEvent '%-.192s' already existsFailed to store event %s. Error code %d from storage engine.Unknown event '%-.192s'Failed to alter event '%-.192s'Failed to drop %sINTERVAL is either not positive or too bigENDS is either invalid or before STARTSEvent execution time is in the past. Event has been disabledFailed to open mysql.eventNo datetime expression providedColumn count of mysql.%s is wrong. Expected %d, found %d. The table is probably corruptedCannot load from mysql.%s. The table is probably corruptedFailed to delete the event from mysql.eventError during compilation of event's bodySame old and new event nameData for column '%s' too longCannot drop index '%-.192s': needed in a foreign key constraintThe syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s insteadYou can't write-lock a log table. Only read access is possibleYou can't use locks with log tables.Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entryThe column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Cannot switch out of the row-based binary log format when the session has open temporary tablesCannot change the binary logging format inside a stored function or triggerThe NDB cluster engine does not support changing the binlog format on the fly yetCannot create temporary table with partitionsPartition constant is out of partition function domainThis partition function is not allowedError in DDL logNot allowed to use NULL value in VALUES LESS THANIncorrect partition nameTransaction characteristics can't be changed while a transaction is in progressALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'Internal scheduler error %dError during starting/stopping of the scheduler. Error code %uEngine cannot be used in partitioned tablesCannot activate '%-.64s' logThe server was not built with row-based replicationDecoding of base64 string failedRecursion of EVENT DDL statements is forbidden when body is presentCannot proceed because system tables used by Event Scheduler were found damaged at server startOnly integers allowed as number hereThis storage engine cannot be used for log tablesYou cannot '%s' a log table if logging is enabledCannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'Incorrect parameter count in the call to native function '%-.192s'Incorrect parameters in the call to native function '%-.192s'Incorrect parameters in the call to stored function %-.192sThis function '%-.192s' has the same name as a native functionДублюючий запис '%-.64s' для ключа '%-.385s'Too many files opened, please execute the command againEvent execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation.Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future.The incident %s occurred on the source. Message: %sTable has no partition for some existing valuesUnsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %sFatal error: %sRelay log read failure: %sRelay log write failure: %sFailed to create %sSource command %s failed: %sBinary logging not possible. Message: %sView `%-.64s`.`%-.64s` has no creation contextCreation context of view `%-.64s`.`%-.64s' is invalidCreation context of stored routine `%-.64s`.`%-.64s` is invalidCorrupted TRG file for table `%-.64s`.`%-.64s`Triggers for table `%-.64s`.`%-.64s` have no creation contextTrigger creation context of table `%-.64s`.`%-.64s` is invalidCreation context of event `%-.64s`.`%-.64s` is invalidCannot open table for trigger `%-.64s`.`%-.64s`Cannot create stored routine `%-.64s`. Check warningsAmbiguous replica modes combination. %sThe BINLOG statement of type `%s` was not preceded by a format description BINLOG statement.Corrupted replication event was detectedInvalid column reference (%-.64s) in LOAD DATABeing purged log %s was not foundXA_RBTIMEOUT: Transaction branch was rolled back: took too longXA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detectedPrepared statement needs to be re-preparedDELAYED option not supported for table '%-.192s'The connection metadata structure does not exist<%-.64s> option ignoredBuilt-in plugins cannot be deletedPlugin is busy and will be uninstalled on shutdown%s variable '%s' is read-only. Use SET %s to assign the valueStorage engine %s does not support rollback for this statement. Transaction rolled back and must be restartedUnexpected source's heartbeat data: %sThe requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds).Bad schema for mysql.ndb_replication table. Message: %-.64sError in parsing conflict function. Message: %-.64sWrite to exceptions table failed. Message: %-.128sComment for table '%-.64s' is too long (max = %lu)Comment for field '%-.64s' is too long (max = %lu)FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference ManualDatabaseTablePartitionSubpartitionTemporaryRenamedToo many active concurrent transactionsNon-ASCII separator arguments are not fully supporteddebug sync point wait timed outdebug sync point hit limit reachedDuplicate condition information item '%s'Unhandled user-defined warning conditionUnhandled user-defined not found conditionUnhandled user-defined exception conditionRESIGNAL when handler not activeSIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATEData truncated for condition item '%s'Data too long for condition item '%s'Unknown locale: '%-.64s'The requested server id %d clashes with the replica startup option --replicate-same-server-idQuery cache is disabled; restart the server with query_cache_type=1 to enable itDuplicate partition field name '%-.192s'Inconsistency in usage of column lists for partitioningPartition column values of incorrect typeToo many fields in '%-.192s'Cannot use MAXVALUE as value in VALUES INCannot have more than one value for this type of %-.64s partitioningRow expressions in VALUES IN only allowed for multi-field column partitioningField '%-.192s' is of a not allowed type for this type of partitioningThe total length of the partitioning fields is too largeCannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %sCannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%sCannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT.Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted.The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas.Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.Statement is unsafe because it uses a UDF which may not return the same value on the replica.Statement is unsafe because it uses a system variable that may have a different value on the replica.Statement is unsafe because it uses a system function that may return a different value on the replica.Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction.%s Statement: %sColumn %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Can't create conversion table for table '%-.192s.%-.192s'Cannot modify @@session.binlog_format inside a transactionThe path specified for %.64s is too long.'%s' is deprecated and will be removed in a future release.Native table '%-.64s'.'%-.64s' has the wrong structureInvalid performance_schema usage.Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statementCannot modify @@session.binlog_direct_non_transactional_updates inside a transactionCannot change the binlog direct flag inside a stored function or triggerA SPATIAL index may only contain a geometrical type columnComment for index '%-.64s' is too long (max = %lu)Wait on a lock was aborted due to a pending exclusive lock%s value is out of range in '%s'A variable of a non-integer based type in LIMIT clauseMixing self-logging and non-self-logging engines in a statement is unsafe.Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.Cannot modify @@session.sql_log_bin inside a transactionCannot change the sql_log_bin inside a stored function or triggerFailed to read from the .par fileVALUES value for partition '%-.64s' must have type INTДоступ заборонено для користувача: '%-.48s'@'%-.64s'SET PASSWORD has no significance for users authenticating via pluginsGRANT with IDENTIFIED WITH is illegal because the user %-.*s already existsCannot truncate a table referenced in a foreign key constraint (%.192s)Plugin '%s' is force_plus_permanent and can not be unloadedThe requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled.The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout.Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try againPrimary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'.Table rebuild required. Please do "ALTER TABLE `%-.64s` FORCE" or dump/reload to fix it!The value of '%s' should be no less than the value of '%s'Index column size too large. The maximum column size is %lu bytes.Trigger '%-.64s' has an error in its body: '%-.256s'Unknown trigger has an error in its body: '%-.256s'Index %s is corruptedUndo log record is too big.INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica.REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica.UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica.Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica.CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica.INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafeTable is being used in foreign key check.Storage engine '%s' does not support system tables. [%s.%s]INSERT into autoincrement field which is not the first part in the composed primary key is unsafe.Cannot load from %s.%s. The table is probably corruptedThe requested value %s for the source delay exceeds the maximum %uOnly Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)Non matching attribute '%-.64s' between partition and tableTable to exchange with partition is partitioned: '%-.64s'Table to exchange with partition is temporary: '%-.64s'Subpartitioned table, use subpartition instead of partitionUnknown partition '%-.64s' in table '%-.64s'Tables have different definitionsFound a row that does not match the partitionOption binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'Table to exchange with partition has foreign key references: '%-.64s'Key value '%-.192s' was not found in table '%-.192s.%-.192s'Data for column '%s' too longReplication event checksum verification failed while reading from network.Replication event checksum verification failed while reading from a log file.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't update table '%-.192s' while '%-.192s' is being created.PARTITION () clause on non partitioned tableFound a row not matching the given partition setpartition '%-.64s' doesn't existFailure while changing the type of replication repository: %s.The creation of some temporary tables could not be rolled back.Some temporary tables were dropped, but these operations could not be rolled back.%s is not supported in multi-threaded replica mode. %sThe number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata.Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s.%sFULLTEXT index is not supported for partitioned tables.Invalid condition numberSending passwords in plain text without SSL/TLS is extremely insecure.Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child tableSetting authentication options is not possible when only the Replica SQL Thread is being started.The table does not have FULLTEXT index to support this queryThe system variable %.200s cannot be set in stored functions or triggers.The system variable %.200s cannot be set when there is an ongoing transaction.The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST.The system variable @@SESSION.GTID_NEXT cannot change inside a transaction.The statement 'SET %.200s' cannot invoke a stored function.The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.Skipping transaction %.200s because it has already been executed and logged.Malformed GTID set specification '%.200s'.Malformed GTID set encoding.Malformed GTID specification '%.200s'.Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid.Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF.Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates.@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF.@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON.@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF.Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions.Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.Unknown EXPLAIN format name: '%s'Cannot execute statement in a READ ONLY transaction.Comment for table partition '%-.64s' is too long (max = %lu)Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log.InnoDB presently supports one FULLTEXT index creation at a timeCannot create FULLTEXT index on temporary InnoDB tableColumn '%-.192s' is of wrong type for an InnoDB FULLTEXT indexIndex '%-.192s' is of wrong type for an InnoDB FULLTEXT indexCreating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again.Unknown ALGORITHM '%s'Unknown LOCK type '%s'CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL.Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log.Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corruptedReplica must silently retry current transactionThere is a foreign key check running on table '%-.192s'. Cannot discard the table.Schema mismatch (%s)Table '%-.192s' in system tablespaceIO Read error: (%lu, %s) %sIO Write error: (%lu, %s) %sTablespace is missing for table %s.Tablespace '%-.192s' exists.Tablespace has been discarded for table '%-.192s'Internal error: %sALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'Index corrupt: %sInvalid display width. Use YEAR instead.Your password does not satisfy the current policy requirementsYou must reset your password using ALTER USER statement before executing this statement.Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'Failed to add the foreign key constraint '%s' to system tablesFailed to open the referenced table '%s'Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'Duplicate foreign key constraint name '%s'The password hash doesn't have the expected format.Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULLDuplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release.Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'Malformed communication packet.Running in read-only modeWhen @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'.The system variable %.200s cannot be set in stored procedures.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON.@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients).@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to.%s is not supported for this operation. Try %s.%s is not supported. Reason: %s. Try %s.COPY algorithm requires a lockPartition specific operations do not yet support LOCK/ALGORITHMColumns participating in a foreign key are renamedCannot change column type INPLACEAdding foreign keys needs foreign_key_checks=OFFCreating unique indexes with IGNORE requires COPY algorithm to remove duplicate rowsDropping a primary key is not allowed without also adding a new primary keyAdding an auto-increment column requires a lockCannot replace hidden FTS_DOC_ID with a user-visible oneCannot drop or rename FTS_DOC_IDFulltext index creation requires a locksql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transactionДублюючий запис для ключа '%-.192s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.cannot silently convert NULL values, as required in this SQL_MODEYour password has expired. To log in you must change it using a client that supports expired passwords.Found a row in wrong partition %sCannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max.Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB tableThe binary log file '%s' is logically corrupted: %sfile %s was not purged because it was being read by %d thread(s), purged only %d out of %d files.file %s was not purged because it is the active log file.Auto-increment value in UPDATE conflicts with internally generated valuesRow events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'Replica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryAccess denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting.InnoDB is in read only mode.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data.Temporary file write failure.Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index.TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format.Operation not allowed when innodb_force_recovery > 0.The initialization vector supplied to %s is too short. Must be at least %d bytes longPlugin '%s' cannot be uninstalled now. %sCannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED.The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly.Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members.File %s is corruptedQuery partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Storage engine for table '%s'.'%s' is not loaded.GET STACKED DIAGNOSTICS when handler not active%s is no longer supported. The statement was converted to %s.Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica.Cannot DISCARD/IMPORT tablespace associated with temporary tableForeign key cascade delete/update exceeds max depth of %d.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Trigger %s.%s.%s does not have CREATED attribute.Referenced trigger '%s' for the given action time and event type does not exist.EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACEInvalid size for column '%-.192s'.Table storage engine '%-.64s' found required create option missingOut of memory in storage engine '%-.64s'.The password for anonymous user cannot be expired.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD firstCannot create FULLTEXT index on materialized subqueryUndo Log error: %sInvalid argument for logarithmThis operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first.This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0.CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file.Query execution was interrupted, maximum statement execution time exceededSelect is not a read only statement, disabling timerDuplicate entry '%-.192s'.'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead.Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECTExpression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated queryReplica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well.replica_preserve_commit_order is not supported %s.The server is currently in offline modeBinary geometry function %s given two geometries of different srids: %u and %u, which should have been identical.Calling geometry function %s with unsupported types of arguments.Unknown GIS error occurred in function %s.Unknown exception caught in GIS function %s.Invalid GIS data provided to function %s.The geometry has no data in function %s.Unable to calculate centroid because geometry is empty in function %s.Geometry overlay calculation error: geometry data is invalid in function %s.Geometry turn info calculation error: geometry data is invalid in function %s.Analysis procedures of intersection points interrupted unexpectedly in function %s.Unknown exception thrown in function %s.Memory allocation error: %-.256s in function %s.Domain error: %-.256s in function %s.Length error: %-.256s in function %s.Invalid argument error: %-.256s in function %s.Out of range error: %-.256s in function %s.Overflow error: %-.256s in function %s.Range error: %-.256s in function %s.Underflow error: %-.256s in function %s.Logic error: %-.256s in function %s.Runtime error: %-.256s in function %s.Unknown exception: %-.384s in function %s.Geometry byte string must be little endian.The password provided for the replication user exceeds the maximum length of 32 charactersIncorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set.Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition.REPLACE cannot be executed as it requires deleting rows that are not in the viewDo not support online operation on table with GIS indexUser variable name '%-.100s' is illegalCannot %s when GTID_MODE = OFF.Cannot %s from a replica thread.Incorrect type for argument %s in function %s.Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %sExpression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %sSupplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'OK packet too largeInvalid JSON data provided to function %s: %sInvalid GeoJSON data provided to function %s: Missing required member '%s'Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'Invalid GeoJSON data provided to function %sUnsupported number of coordinate dimensions in function %s: Found %u, expected %uReplica channel '%s' does not exist.A replica channel '%s' already exists for the given host and port combination.Couldn't create channel: Channel name is either invalid or too long.To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE.Cannot delete replica info objects for channel '%s'.Multiple channels exist on the replica. Please provide channel name as an argument.Maximum number of replication channels allowed exceeded.This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' firstThis operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'Replication thread(s) for channel '%s' are already runnning.Replication thread(s) for channel '%s' are already stopped.This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first.When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter.Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_byIn aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_byUpdating '%s' is deprecated. It will be made read-only in a future release.Changing sql mode '%s' is deprecated. It will be removed in a future release.DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`.The server is not configured properly to be an active member of the group. Please see more details on error log.The START GROUP_REPLICATION command failed since the group is already running.The START GROUP_REPLICATION command failed as the applier module failed to start.The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete.The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer.The START GROUP_REPLICATION command failed as there was an error when joining the communication group.The table does not comply with the requirements by an external plugin.Cannot change the value of variable %s without binary log format as ROW.Error on observer while running replication hook '%s'.Plugin instructed the server to rollback the current transaction.Expression of generated column '%s' contains a disallowed function.INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actionsCannot define foreign key with %s clause on a generated column.The value specified for generated column '%s' in table '%s' is not allowed.'%s' is not supported for generated columns.Generated column can refer only to generated columns defined prior to it.Column '%s' has a generated column dependency.Generated column '%s' cannot refer to auto-increment column.The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s.The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld.Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency.There are ongoing transactions that violate GTID consistency.Access denied for user '%-.48s'@'%-.64s'. Account is locked.Incorrect tablespace name `%-.192s`Tablespace `%-.192s` is not empty.Incorrect File Name '%s'.Inconsistent intersection points.Optimizer hint syntax errorUnsupported MAX_EXECUTION_TIMEMAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements onlyHint %s is ignored as conflicting/duplicatedQuery block name %s is not found for %s hintUnresolved name %s for %s hintPlease do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state.Command not supported by pluggable protocolsIncorrect locking service lock name '%-.192s'.Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition.Service lock wait timeout exceeded.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s.'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.Version token mismatch for %.*s. Correct value %.*sVersion token %.*s not found.Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK.%-.192s cannot be performed on channel '%-.192s'.Invalid JSON text: "%s" at position %u in value for column '%-.200s'.Invalid JSON text in argument %u to function %s: "%s" at position %u.%-.0sThe JSON binary value contains invalid data.Invalid JSON path expression. The error is around character position %u.%-.200sCannot create a JSON value from a string with CHARACTER SET '%s'.Invalid JSON character data provided to function %s: '%s'; utf8 is required.Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required.Cannot CAST value to JSON.A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'.In this situation, path expressions may not contain the * and ** tokens or an array range.The JSON value is too big to be stored in a JSON column.The JSON object contains a key name that is too long.JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path.The path expression '$' is not allowed in this context.The oneOrAll argument to %s may take these values: 'one' or 'all'.Out of range JSON value for CAST to %s%-.0s from column %s at row %ldInvalid JSON value for CAST to %s%-.0s from column %s at row %ldThe JSON document exceeds the maximum depth.JSON documents may not contain NULL member names.Connections using insecure transport are prohibited while --require_secure_transport=ON.No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON.Storage engine %s is disabled (Table creation is disallowed).Authorization ID %s does not exist.Authorization ID %s already exists.Aborted by Audit API ('%-.48s';%d).A path expression is not a path to a cell in an array.Another buffer pool resize is already in progress.The '%s' feature is disabled; see the documentation for '%s'Server isn't availableSession was killedMemory capacity of %llu bytes for '%s' exceeded. %sRange optimization was not done for this query.Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONINGThe client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.Cannot add foreign key on the base column of indexed virtual column.Cannot create index on virtual column whose base column has foreign constraint.Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction.Lock acquisition refused by storage engine.ADD COLUMN col...VIRTUAL, ADD INDEX(col)Master key rotation is not supported by storage engine.Encryption key rotation error reported by SE: %sWrite to binlog failed. However, master key rotation has been completed successfully.Storage engine is not available.This tablespace can't be encrypted.Invalid encryption option.Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Parser bailed out for this query.Cannot alter encryption attribute by inplace algorithm.Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using.It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure.RESET SOURCE is not allowed because %-.384s.The START GROUP_REPLICATION command failed since the group already has 9 members.Cannot add foreign key on the base column of stored column. Cannot complete the operation because table is referenced by another connection.The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead.%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead.%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead.The resource manager is not able to commit the transaction branch at this time. Please retry later.Function %s failed due to: %s.Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements.%s UDF failed; %sCan not perform keyring migration : %sAccess denied; you need %-.128s privileges for this operationKeyring migration %s.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.No keyring plugin installed.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Audit Log filtering has not been installed.Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operationSUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Could not reinitialize audit log filters.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Invalid "max_array_length" argument value.%sFilter name cannot be empty.User cannot be empty.Specified filter has not been found.First character of the user name must be alphanumeric.Invalid character in the user name.Invalid character in the host name.With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Could not open file '%s' for error logging%s%sGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Can't start server : Named Pipe "%s" already in use.The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher.Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing.KDF method name is not valid. Please use hkdf or pbkdf2_hmac method nameFor KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security.KDF option size is invalid, please provide valid size < %d bytes and not NULLCREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.The ACL operation failed due to the following error from SE: errcode %d - %.256sThis storage engine does not support the %s index algorithm, storage engine default was used instead.Database '%-.192s' doesn't existToo many enumeration values for column %.192s.Too long enumeration/set value for column %.192s.%s dictionary object is invalid. (%.192s)Failed to update %.192s dictionary object.Dictionary object id (%lu) does not exist.Dictionary object name '%s' is invalid. (%.192s)Tablespace %-.192s doesn't exist.Comment for routine '%-.64s' is too long (max = %lu)Failed to load routine '%-.64s'.Binary operands of bitwise operators must be of equal lengthAggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() functionHints aren't supported in %s%.64s value is a geometry of unexpected type %.64s in %.64s.Can't parse the spatial reference system definition of SRID %u.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.There's no spatial reference system with SRID %u.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.A primary key index cannot be invisibleUnknown authorization ID `%.64s`@`%.64s`Failed to grant %.90s` to %.90sFailed to open the security system tablesFailed to set default rolesCannot find schema in specified URN: '%.192s'.Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'.Cannot load component from specified URN: '%.192s'.`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`Could not revoke role from `%.64s`@`%.64s`Renaming of a role identifier is forbiddenCannot acquire specified service implementation: '%.192s'.Cannot satisfy dependency for service '%.192s' required by component '%.192s'.Cannot register service implementation '%.192s' provided by component '%.192s'.Initialization method provided by component '%.192s' failed.Component specified by URN '%.192s' to unload has not been loaded before.De-initialization method provided by component '%.192s' failed.Release of previously acquired service implementation failed.Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component.Cannot unload component from specified URN: '%.192s'.The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before.The mysql.component table is missing or has an incorrect definition.Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine.The component with specified URN: '%.192s' was specified in group more than once.@@GLOBAL.GTID_PURGED cannot be changed: %sCan not lock user management caches for processing.There's no spatial reference system with SRID %u.Variables cannot be persisted. Please retry.Information schema queries do not support the '%s' clause.Unable to store dynamic %s statistics into data dictionary.Access to system schema '%.64s' is rejected.Access to system tablespace '%.64s' is rejected.Access to %.64s '%.64s.%.64s' is rejected.data dictionary tablesystem tabletableInvalid option key '%.192s' in function %.192s.Invalid value '%.192s' for option '%.192s' in function '%.192s'.The string '%.192s' is not a valid key %c value pair in function %.192s.The options argument in function %.192s starts with the invalid character '%c'.The options argument in function %.192s ends with the invalid character '%c'.The options argument in function %.192s contains the invalid character sequence '%.192s'.Duplicate option key '%.192s' in funtion '%.192s'.There's no spatial reference system with SRID %u. The axis order is unknown.Access to native function '%.64s' is rejected.The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'.Unresolved table name %s in locking clause.Table %s appears in multiple locking clauses.Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic.Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic.Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set.Recursive Common Table Expression '%s' should contain a UNIONRecursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive onesRecursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query blockIn recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hintsIn recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery'%s' requires @@internal_tmp_disk_storage_engine=InnoDBWindow name '%s' is not defined.There is a circularity in the window dependency graph.A window which depends on another cannot define partitioning.Window '%s' has a frame definition, so cannot be referenced by another window.Window '%s' cannot inherit '%s' since both contain an ORDER BY clause.Window '%s': frame start cannot be UNBOUNDED FOLLOWING.Window '%s': frame end cannot be UNBOUNDED PRECEDING.Window '%s': frame start or end is negative, NULL or of non-integral typeWindow '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal typeWindow '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed.Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed.Window '%s' has a non-constant frame bound.Window '%s' is defined twice.Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression.You cannot use the window function '%s' in this context.'You cannot use the alias '%s' of an expression containing a window function in this context.'You cannot nest a window function in the specification of window '%s'.Window '%s': INTERVAL can only be used with RANGE frames.ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BYTo get information about window functions use EXPLAIN FORMAT=JSONWindow function '%s' ignores the frame clause of window '%s' and aggregates over the whole partitionWindowing requires @@internal_tmp_mem_storage_engine=TempTable.Too many arguments for function %s: %lu; maximum allowed is %s.Argument #%u of GROUPING function is not in GROUP BYComment for tablespace '%-.64s' is too long (max = %lu)Storage engine can't drop table '%-.129s'Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary.Duplicate file name for tablespace '%-.64s'Problem while dropping database. Can't remove database directory (%s). Please remove it manually.No SDI files matched the pattern '%s'Schema '%.256s', referenced in SDI, does not exist.Table '%.256s.%.256s', referenced in SDI, already exists.Imported mysqld_version (%llu) is not compatible with current (%llu)Imported dd version (%u) is not compatible with current (%u)Imported sdi version (%llu) is not compatible with current (%llu)Invalid number of arguments for hint %sVariable %s does not exist in persisted config fileLongitude %f is out of range in function %.192s. It must be within (%f, %f].Latitude %f is out of range in function %.192s. It must be within [%f, %f].%.192s(%.80s) has not been implemented for geographic spatial reference systems.Illegal privilege level specified for %sAccess to system view INFORMATION_SCHEMA.'%.64s' is rejected.The log-filter component "%s" got confused at "%s" ...Partitioning expression is too long.DROP FUNCTION can't drop a dynamically registered user defined functionUnable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles.Tablespace '%.192s' does not have a file named '%.192s'Access denied; you need %-.128s privileges for this operationYou need the SUPER privilege for command '%-.192s'Path is within the current data directory '%-.192s'Concurrent DDL is performed during clone operation. Please try again.Too many concurrent clone operations. Maximum allowed - %d.The table in transaction %s does not comply with the requirements by an external plugin.Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value.Variable %s cannot be set using SET_VAR hint.Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policyNon-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password historyThe client doesn't support %sTablespace '%s' was skipped since its definition is being modified by concurrent DDL statementEngine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Could not apply JSON diff in table %.*s, column %s.Corrupted JSON diff for table %.*s, column %s.Resource Group '%-.192s' existsResource Group '%-.192s' does not exist.Invalid cpu id %uInvalid VCPU range %u-%uInvalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d].%s operation is disallowed on %sResource group %s is busy.Resource group %s is disabled.Feature %s is unsupported (%s).Attribute %s is ignored (%s).Invalid thread id (%llu).Unable to bind resource group %s with thread id (%llu).(%s).Option FORCE invalid as DISABLE option is not specified.The %s command encountered a failure. %sFailed to %s SDI '%.192s.%.192s' in tablespace '%.192s'.Missing value for JSON_TABLE column '%.192s'Can't store an array or an object in the scalar JSON_TABLE column '%.192s'Every table function must have an aliasINNER or LEFT JOIN must be used for LATERAL references made by '%.192s'Value is out of range for JSON_TABLE's column '%.192s'More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'The selected authentication method %.*s does not support password expirationInvalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object.Column '%-.192s' cannot be nullThe spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column.Create table/tablespace '%-.192s' failed, as disk is fullCould not parse argument to digest function: "%s".Could not parse argument to digest function.Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location).Schema directory '%.192s' does not existFailed to create schema directory '%.192s' (errno: %d - %s)Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location).Function %.192s is only defined for SRID 0 and SRID 4326.The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)The result string is larger than the result buffer.Illegal argument to a regular expression.Index out of bounds in regular expression search.Internal error in the regular expression library.Syntax error in regular expression on line %u, character %u.Unrecognized escape sequence in regular expression.The regular expression contains a feature that is not implemented in this library version.Mismatched parenthesis in regular expression.Incorrect description of a {min,max} interval.The maximum is less than the minumum in a {min,max} interval.Invalid back-reference in regular expression.The look-behind assertion exceeds the limit in regular expression.The regular expression contains an unclosed bracket expression.The regular expression contains an [x-y] character range where x comes after y.Overflow in the regular expression backtrack stack.Timeout exceeded in regular expression match.The regular expression pattern exceeds limits on size or complexity.Value for %s got confusing at or around "%s". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once.Setting an empty %s pipeline disables error logging!filter %s: %s%.192s(%.80s) has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems.Invalid radius provided to function %s: Radius must be greater than zero.Restart server failed (%s).Missing mandatory attribute %s.Multiple definitions of attribute %s.The spatial reference system name can't be an empty string or start or end with whitespace.The organization name can't be an empty string or start or end with whitespace.There is already a spatial reference system with SRID %u.There is already a spatial reference system with SRID %u.SRID 0 is not modifiable.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.Can't modify SRID %u. There is at least one column depending on it.Invalid character in attribute %s.Attribute %s is too long. The maximum length is %u characters.'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expectedUnable to collect information for column '%-.192s': %-.192s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.This option cannot be set %s.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet.Spatial indexes can't be primary or unique indexes.The index type %.20s is not supported for spatial indexes.Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f].A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f].Foreign key '%s' uses virtual column '%s' which is not supported.Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.The length of the semi-major axis must be a positive number.The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere.The angular unit conversion factor must be a positive number.The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit.Transformation from SRID %u is not supported.Transformation to SRID %u is not supported.Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again.Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try againChanging @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.Data truncated for functional index '%s' at row %ldValue is out of range for functional index '%s' at row %ldCannot create a functional index on a function that returns a JSON or GEOMETRY value.Functional index '%.64s' cannot refer to an auto-increment column.Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index.The primary key cannot be a functional indexCannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST.Expression of functional index '%s' contains a disallowed function.Fulltext functional index is not supported.Spatial functional index is not supported.The used storage engine cannot index the expression '%s'.Functional index on a column is not supported. Consider using a regular index instead.Expression of generated column '%s' contains a disallowed function: %s.Expression of generated column '%s' cannot refer to a row value.Expression of generated column '%s' cannot refer user or system variables.Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed.Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value.Default value expression of column '%s' cannot refer to an auto-increment column.Default value expression of column '%s' contains a disallowed function.Default value expression of column '%s' contains a disallowed function: %s.Default value expression of column '%s' cannot refer to a row value.Default value expression of column '%s' cannot refer user or system variables.DEFAULT function cannot be used with default value expressions'%s' is not supported for default value expressions.Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Cannot change table's storage engine because the table participates in a foreign key constraint.Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'.'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.Nested comment syntax is deprecated and will be removed in a future release.Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible.Timeout exceeded for held statement while new Group Replication primary member is applying backlog.Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog.Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Failed to change binlog_encryption value. %-.80s.Unable to recover binlog encryption master key, please check if keyring is loaded.slow query log file format changed as requested, but setting will have no effect when not actually logging to a file.The option group_replication_consistency cannot be used on the current member state.Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'.Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit.The Group Replication plugin is stopping, therefore new transactions are not allowed to start.Expression of functional index '%s' cannot refer to a row value.Failed to encrypt content to write into binlog file: %s.Page Tracking is not started yet.Tracking was not enabled for the LSN range specifiedCannot purge data when concurrent clone is in progress. Try later.Cannot rotate binary log master key when 'binlog-encryption' is off.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files.Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key.Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.An expression of non-boolean type specified to a check constraint '%-.192s'.Column check constraint '%-.192s' references other column.An expression of a check constraint '%-.192s' contains disallowed function: %s.An expression of a check constraint '%-.192s' contains disallowed function.An expression of a check constraint '%-.192s' cannot refer to a user or system variable.Check constraint '%-.192s' cannot refer to a row value.Check constraint '%-.192s' cannot refer to an auto-increment column.Check constraint '%-.192s' is violated.Check constraint '%-.192s' refers to non-existing column '%-.192s'.Check constraint '%-.192s' is not found in the table.Duplicate check constraint name '%-.192s'.Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action.Creating an unencrypted table in a database with default encryption enabled.Request to create %s table while using an %s tablespace.Table encryption differ from its database default encryption, and user doesn't have enough privilege.Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege.This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege.This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege.Cannot determine the type of the tablespace named '%s'.Source tablespace is encrypted but target tablespace is not.ENCRYPTION clause is not valid for %s tablespace.Multiple %s clausesGRANT ... AS is currently supported only for global privileges.Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement.Column '%s' has a functional index dependency and cannot be dropped or renamed.Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Redo log archiving start prohibits path name in 'subdir' argumentRedo log archiving start timed outServer variable 'innodb_redo_log_archive_dirs' is NULL or emptyLabel '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'Redo log archive directory '%.192s' does not exist or is not a directoryRedo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'Redo log archive directory '%.192s' is accessible to all OS usersCannot create redo log archive file '%.512s' (OS errno: %d - %.128s)Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() firstRedo log archiving is not activeRedo log archiving failed: %.512sRedo log archiving has not been started by this sessionRegex error: %-.256s in function %s.Invalid JSON type in argument %u to function %s; an %s is required.Cannot convert string '%.64s' from %s to %sColumn '%s' has a partitioning function dependency and cannot be dropped or renamed.AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'.Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first.Specifying number of digits for floating point data types is deprecated and will be removed in a future release.UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release.Integer display width is deprecated and will be removed in a future release.The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column.Clone Donor Error: %.512s.Clone received unexpected response from Donor : %.512s.Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s.Clone Donor OS: %.64s is different from Recipient OS: %.64s.Clone Donor platform: %.64s is different from Recipient platform: %.64s.Clone Donor collation: %.128s is unavailable in Recipient.Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s.Clone system configuration: %.512sClone Donor plugin %.128s is not active in Recipient.Clone cannot use loop back connection while cloning into current data directory.Clone needs SSL connection for encrypted table.Clone estimated database size is %.64s. Available space %.64s is not enough.Concurrent clone in progress. Please try after clone is complete.The clone operation cannot be executed when %s.Cannot grant roles to an anonymous user.%sEmpty password can not be retained as second password for user '%s'@'%s'.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Gtid table is not ready to be used. Table '%s.%s' cannot be opened.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'.Error installing plugin '%s': %sStorage engine could not allocate temporary tablespace for this session.Got unknown error: %dCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.A capture group has an invalid name.Failed to set up SSL because of the following SSL library error: %sSecondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Do not specify the current password while changing it for other users.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.sql_mode=0x%08x is not supported.Invalid match mode flag in regular expression.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted.There's no unit of measure named '%s'.Invalid JSON value for CAST for functional index '%-.64s'.Out of range JSON value for CAST for functional index '%-.64s'.Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s).Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes.Data too long for functional index '%-.64s'.Cannot store an array or an object in a scalar key part of the index '%.192s'.Cannot use functional index '%-.64s' due to type or collation conversion.The function '%s' failed. %sCannot update GTID_PURGED with the Group Replication plugin runningGrouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s''audit_log' password has been copied into '%.32s' and will be removed with first purged password.Started auto-rejoin procedure attempt %lu of %luA plugin was loaded or unloaded during a query, a system variable table was changed.A plugin was loaded or unloaded during a query, a global status variable was changed.The START GROUP_REPLICATION command failed to start its message service.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'.Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'.Invalid compression algorithm '%.192s'.Invalid zstd compression level for algorithm '%.192s'.Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege.Dynamic privilege '%s' is not registered with the server.Function '%s' failed because key is invalid.Function '%s' failed because key type is invalid.Function '%s' failed because key length is too long.Function '%s' failed because key type is too long.%s.Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server.Invalid character set '%s' was specified. It must be a character set name as supported by server.Invalid collation '%s' was specified. It must be a collation name as supported by server.Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type.Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause.Constraint '%-.192s' does not exist.Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints.Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement.A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement.The query does not comply with variable require_row_format restrictions.The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1.Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatoryFailed to acquire lock on user management service, unable to fetch mandatory role listLoading local data is disabled; this must be enabled on both the client and server sidesFailed to import %s because the CFG file version (%u) is not compatible with the current version (%u)Out of memoryCharacter set can be set only for the UDF argument type STRING.Character set can be set only for the UDF RETURN type STRING.Multiple INTO clauses in one query block.Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses.Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins.UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release.Clone needs max_allowed_packet value to be %u or more. Current value is %uFailed to %s sdi for %s.%s in %s due to missing record.Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed.This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION firstSpecifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead.The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead.The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.No value was found by '%.192s' on the specified path.More than one value was found by '%.192s' on the specified path.Hostname cannot be longer than %d characters.Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty.The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel.The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters.Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' onInvalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200sOnly BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement.Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement.START TRANSACTION clause cannot be used %.128sInvalid json attribute, error: "%s" at pos %u: '%s'Storage engine '%s' does not support ENGINE_ATTRIBUTE.The user attribute must be a valid JSON objectCannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCECannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()Not enough resources to complete lock request.Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNINGThe function %s does not support the character set '%s'.Conversion from collation %s into %s impossible for %sSchema '%s' is in read only mode.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON.Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled.The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1.Invalid use of parameters in '%s'Character set '%s' cannot be used in conjunction with '%s' in call to %s.Changing %s not supported on this platform. Falling back to the default.Invalid time zone interval: '%s'Cannot cast value to %s.The hypergraph optimizer does not yet support '%s'The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services.@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event.Could not open file '%s' for error logging%s%sUser %.256s is referenced as a definer account in %s.Operation %s failed for %.256s as it is referenced as a definer account in %s.Decimal number in regular expression is too large.The variable "%s" has a non-integer based typeReads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables.The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica.STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete.The Replica Monitor thread failed to start.Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON.The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON.The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF.Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation.WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_nameCHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name.The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.AUTOEXTEND_SIZE should be a multiple of %uMInnoDB: "%s" not allowed with general tablespacesAUTOEXTEND_SIZE value should be between %uM and %uMAUTOEXTEND_SIZE clause is not valid for %s tablespace.User account %s is directly or indirectly granted to the role %s. The GRANT would create a loopA table must have at least one visible column.Compression failed with the following error : %sThe parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter.The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior.Invalid cast from %s to %s.Invalid cast from %s to %s. A polygon ring is in the wrong direction.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID.Keyring reload failed. Please check error log for more details.Tablespace '%.192s' is invalid for SDI operations.Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'.A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher.CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid.Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuidUnable to retrieve group_replication_view_change_uuid variable during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm.Cannot install the %.192s plugin when the %.192s plugin is installed.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause.Invalid target for assignment in INSERT or UPDATE statement '%.192s'.This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary.Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation.audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Invalid plugin "%s" specified as %d factor during "%s".IDENTIFIED BY clause during "%s" not supported for plugin "%s".This operation is not supported for plugin "%s".Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration.%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method.%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation.%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable.The registration for %d factor authentication method is already completed. You cannot perform registration multiple times.The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session.Authentication plugin's registration failed.%d factor authentication method should be added before %d factor authentication method.Authentication factor should be different.The operation "%s" cannot be performed for user '%s'@'%s' configured to connect without a password.GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1.REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1.When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid.When configuring a group replication channel you must do it when GTID_MODE = ON.Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.SSL fips mode error: %s%s=%llu is outside the valid range [%llu,%llu]. %llu will be used.MATCH does not support ROLLUP columns.Missing locale resource in regular expression library.Regular expression library used default (root) locale.Missing data file in regular expression library.'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Need to rebuild the table to change column typeThis function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name.Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions.%sComment for %s '%s' contains an invalid %s character string: '%.64s'.Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'.Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ONMaximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE.Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY.All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'.Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'.Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove.Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable.SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely.Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'.Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table.This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function.SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit.Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit.The spatial reference system definition for SRID %u contains unused projection parameter "%s".Failed to generate invisible primary key. Column 'my_row_id' already exists.Failed to generate invisible primary key. Auto-increment column already exists.Altering generated invisible primary key column 'my_row_id' is not allowed.Please drop primary key column to be able to drop generated invisible primary key.Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0.Recursive table reference in EXCEPT or INTERSECT operand is not allowed.Error when trying to fetch information from security context object, when trying to connect the server.Error in command service backend interface, because of : "%s"The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %sUsing %s as unquoted identifier is deprecated, please use quotes or rename the identifier.Max number of duplicate rows in INTERSECT ALL exceeded.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupInvalid timestamp format in %s udfSHAPE_PREDICTION UDF %s got error because of %s.Height parameter must be non negative.Scaling parameter must be non negative.Zone width parameter must be an integer between 1-60.Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810).The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release.Table '%-.192s' is not empty.Table '%-.192s' has no primary key.Table '%-.192s' is in a shared tablespace.Table '%-.192s' has indexes other than primary key.[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %sBulk executor error: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional details.Bulk loader failed, mysql_load->load returned an error, check the error log for additional details.CSV column too big for leftover buffer.Bulk loader component error: %sThe first file being loaded contained less lines than the ignore clauseMissing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.LOAD BULK DATA into table '%-.192s' failed: %sIncorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed.Cannot change the '%s' system variable in read-only mode.Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY.Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY.Failed to set persisted options.The value supplied for %s in the SET list cannot be nullThe assignment of %s in SET doesn't match any of the variables registered by the component(s)'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.User-level lock name '%-.192s' should not exceed %d characters.Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number.The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal.'%s' is deprecated and will be removed in a future release. %sRunning recursive calls to SQL execution service is not supportedParser saw: %sCan't create thread to handle bootstrap (errno: %d)Trigger for table '%s'.'%s': invalid %s value (%s).Wrong tree: %sError: Invalid %sSkip re-populating collations and character sets tables in %s%sread-only mode.Using data dictionary with version '%d'.Installed data dictionary with version %dData Dictionary version '%d' not supported.Failed to set syslog facility to "%s", setting to "%s" (%d) instead.Cannot open %s; check privileges, or remove syseventlog from --log-error-services! either restart the query logging by using "SET GLOBAL SLOW_QUERY_LOG=ON" or either restart the query logging by using "SET GLOBAL GENERAL_LOG=ON" orFailed to write to %s: %sWhile initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u).Gtid table is not ready to be used. Table '%s.%s' cannot be opened.System schema directory does not exist.Error in initializing dictionary, upgrade will do a cleanup and exitView '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s').Error in allocating memory for character set name for view %s.%s.Data Dictionary initialization failed.Failed to update plugin metadata in dictionary tables.Failed to Populate DD tables.Error in Creating View %s.%sUnable to start server. Cannot find the meta data for data dictionary table '%s'.Dictionary cache not empty at shutdown.Dictionary objects used but not released.Dictionary objects left in default releaser.Dictionary object auto releaser not deletedError: Unable to create primary object keyError: Unable to create object keyCan't create handle_manager thread (errno= %d)It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change.option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF.Changed ENFORCE_GTID_CONSISTENCY from %s to %s.Changed GTID_MODE from %s to %s.%s is set to a disabled storage engine %s.Debug sync points hit:                   %22sDebug sync points executed:              %22sDebug sync points max active per thread: %22sDebug Sync Facility disabled due to lack of memory.Can't init tc logEvent Scheduler: Can't initialize the execution queueEvent Scheduler: Purging the queue. %u eventsEvent Scheduler: Last execution of %s.%s. %s%*sEvent Scheduler: [%s].[%s.%s] event execution failed.Event Scheduler: Cannot initialize the scheduler threadEvent Scheduler: StoppedEvent scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)Event Scheduler: Waiting for the scheduler thread to replyEvent Scheduler: scheduler thread started with id %uEvent Scheduler: Serious error during getting next event to execute. StoppingEvent_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event schedulerEvent Scheduler: Killing the scheduler thread, thread id %uIP address '%s' could not be resolved: %sHost name '%s' could not be resolved: %sIP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself.Hostname '%s' does not resolve to '%s'.Hostname '%s' has the following IP addresses: - %sDefiner clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer.Client character set is missing for trigger of table %s. Using default character set.Error in parsing view %s.%sFailed to bootstrap components infrastructure.Failed to shutdown components infrastructure.Failed to bootstrap persistent components loader.Giving %d client threads a chance to die gracefullyCA certificate %s is self signed.Failed to set up SSL because of the following SSL library error: %sFailed to generate a server UUID because it is failed to allocate the THD.Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, Generated uuid: '%s', server_start_time: %lu, bytes_sent: %lluThe server_uuid stored in auto.cnf file is not a valid UUID.Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s.Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID.Unknown/unsupported storage engine: %sUnsupported value 0 for secure-authInvalid instrument name or value for performance_schema_instrument '%s'The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.ignore-builtin-innodb is ignored and will be removed in future releases.Invalid old_passwords mode: 1. Valid values are 2 and 0--verbose is for use with --help; did you mean --log-error-verbosity?options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not setnet_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify.TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).Invalid ft-boolean-syntax string: %s'NO_AUTO_CREATE_USER' sql mode was not set.Could not allocate memory for connection handlingCould not allocate memory for thread handlingCan't create test file %sCan't start server: can't create PID file: %sUnable to delete pid file: %sCan't create thread to handle shutdown requests (errno= %d)Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %sIgnoring --secure-file-priv value as server is running with --initialize(-insecure).Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabledInsecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory.Failed to get stat for directory pointed out by --secure-file-privInsecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.Value for --secure-file-priv is longer than maximum limit of %dCan't create thread to handle named pipes (errno= %d)Can't create thread to handle TCP/IP (errno= %d)Can't create thread to handle shared memory (errno= %d)Can't create interrupt-thread (error %d, errno: %d)World-writable config file '%s' has been removed.setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signalsWrong date/time format specifier: %sCould not allocate replication and binlog filters: %sCannot allocate the keycacheCurrent time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process.Iteration %d: Obtained valid current time from systemIteration %d: Current time obtained from system is greater than 2038This MySQL server doesn't support dates later then 2038%s (mysqld %s) starting as process %luShutting down replica threadsForcefully disconnecting %d remaining clientsAbortingBinlog endgethostname failed, using '%s' as hostnameOne can only use the --user switch if running as rootFatal error: Please read "Security" section of the manual to find out how to run mysqld as root!Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured.setgid: %ssetuid: %ssetregid: %ssetreuid: %schroot: %sTCP/IP, --shared-memory, or --named-pipe should be configured on NT OSCTRL-C ignored during startup'%s' can not be used as client character set. '%s' will be used as default client character set.Out of memoryFailed to lock memory. Errno: %dmy_init() failed.Execution of init_file '%s' started.Execution of init_file '%s' ended.Changed limits: max_open_files: %lu (requested %lu)Could not increase number of max_open_files to more than %lu (request: %lu)Changed limits: max_connections: %lu (requested %lu)Changed limits: table_open_cache: %lu (requested %lu)Ignoring user change to '%s' because the user was set to '%s' earlier on the command lineCould not add do table rule '%s'!Could not add ignore table rule '%s'!The variable session_track_system_variables either has duplicate values or invalid values.Too many arguments (first extra is '%s').Use --verbose --help to get a list of available options!Unable to read errmsg.sys fileCan't init databasesThere were other values specified to log-output besides NONE. Disabling slow and general logs anyway.CSV engine is not present, falling back to the log filesBad syntax in replicate-rewrite-db - missing '->'!Bad syntax in replicate-rewrite-db - empty FROM db!Bad syntax in replicate-rewrite-db - empty TO db!Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option.Invalid value for %s: %sThe server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode.Setting lower_case_table_names=2 because file system for %s is case insensitivelower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems.You need to use --log-bin to make %s work.Path '%s' is a directory name, please specify a file name for %s optionNo argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem.You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentationUnable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d).Failed to initialize GTID structures.Failed to initialize early plugins.Failed to initialize builtin plugins.Failed to initialize dynamic plugins.Performance schema disabled (reason: init failed).Asked for %lu thread stack, but got %ldfailed to set datadir to %sCan't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/groupCan't change data directory owner to %sSetting persistent options failed.Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table.Can't start server: Invalid value for --default-authentication-pluginCould not join %sthread. error:%dAn error occurred while building do_table and ignore_table rules to hashes for global replication filter.Error opening CA certificate fileError accessing directory pointed by --ssl-capathFound %s, %s and %s in data directory. Trying to enable SSL support using them.Failed to create %s(file: '%s', errno %d)Failed to initialize timer component (errno %d).server-id configured is too large to represent with server-id-bits configured.Default%s storage engine (%s) is not availableCould not open file '%s' for error logging%s%sInvalid log file name after expanding symlinks: '%s'using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server.using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled.NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value%sUnable to start server. The data dictionary tablespace '%s' does not exist.Connection collation is missing for trigger of table %s. Using default connection collation.Database collation is missing for trigger of table %s. Using Default character set.Error in Memory allocation for Definer %s for Trigger.Error in reading %s.TRG file.Error in parsing Triggers from %s.TRG file.Error in creating DD entry for Trigger %s.%sResolving dependency for the view '%s.%s' failed. View is no more valid to use%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view.Plugin '%s' init function returned error.Initialization of transaction delegates failed. Please report a bug.Initialization binlog storage delegates failed. Please report a bug.Initialization of binlog transmit delegates failed. Please report a bug.Initialization binlog relay IO delegates failed. Please report a bug.Run function '...' in plugin '%s' failedmysql_ha_read: Got error %d when reading table '%s'Stored routine '%s'.'%s': invalid value in column %s.Invalid creation context '%s.%s'.Got error %d when reading table '%s'load_des_file:  Found wrong key_number: %cFailed to set persisted options.Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON.Found option without preceding group in config fileVALGRIND_DO_QUICK_LEAK_CHECKVALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug.Got unknown error: %dCan't allocate memory for udf structuresCan't alloc memory for udf function: '%.64s'Invalid row in mysql.func table for function '%.64s'Could not open the mysql.func table. Please perform the MySQL upgrade procedure.Found %d prepared transaction(s) in %sFound %d prepared XA transactionsignore xid %scommit xid %srollback xid %sStarting XA crash recovery...--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery.Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions.XA crash recovery finished.Failed to collect GTID to send in the response packet!MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %sFollowing users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sFollowing users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %sTable '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!Got an error from thread_id=%u, %s:%dGot an error from unknown thread, %s:%dToo many storage engines!Storage engine '%s' has conflicting typecode. Assigning value %d.Out of memory on transaction write set extractionUnable to allocate memory for plugin '%s' handlerton.Shared memory setting up listenerCan't create shared memory service: %s. : %sCan't create shared memory connection: %s. : %sCan't create event, last error=%uCan't create new named pipe!: %sCan't create thread to handle new connection(errno= %d)Failed to create a socket for %s '%s': errno: %d.Server socket created on IP: '%s'.Server hostname (bind-address): '%s'; port: %dIPv6 is available.IPv6 is not available.Can't create IP socket: %sCan't start server: cannot resolve hostname!Do you already have another mysqld server running on port: %d ?Do you already have another mysqld server running on socket: %s ?Another process with pid %d is using unix socket file.Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Retrying bind on TCP/IP port %uCan't start server: Bind on TCP/IP port: %sFails to print out IP-address.  - '%s' resolves to '%s';Can't start server: listen() on TCP/IP port: %slisten() on TCP/IP failed with error %dThe socket file path is too long (> %u): %sUnable to setup unix socket lock file.Can't start server: UNIX Socket : %sCan't start server : Bind on unix socket: %slisten() on Unix socket failed with error %dUnable to create unix socket lock file %s after retries.Could not create unix socket lock file %s.Could not open unix socket lock file %s.Could not read unix socket lock file %s.Unix socket lock file is empty %s.Invalid pid in unix socket lock file %s.Could not write unix socket lock file %s errno %d.Could not remove unix socket lock file %s errno %d.Could not sync unix socket lock file %s errno %d.Could not close unix socket lock file %s errno %d.mysqld: Got error %d from selectError in accept: %sRSA %s key file not found: %s. Some authentication plugins will not work.Failure to parse RSA %s key (file exists): %s: %sFailure to read key file: %sRSA key files not found. Some authentication plugins will not work.Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %sX.509 ciphers mismatch: should be '%s' but is '%s'X.509 issuer mismatch: should be '%s' but is '%s'X.509 subject mismatch: should be '%s' but is '%s'Failed to activate default role %s for %sCould not generate RSA private key required for X.509 certificate.Could not write key file: %sCould not set file permission for %sCould not read CA key file: %sCould not read CA certificate file: %sCould not generate X.509 certificate.Could not write certificate file: %sCould not generate RSA Private/Public key pairCould not write private key file: %sCould not write public key file: %sSkipping generation of SSL certificates as options related to SSL are specified.Skipping generation of SSL certificates as certificate files are present in data directory.Auto generated SSL certificates are placed in data directory.Skipping generation of SSL certificates as --auto_generate_certs is set to OFF.Skipping generation of RSA key pair through %s as options related to RSA keys are specified.Skipping generation of RSA key pair through %s as key files are present in data directory.Auto generated RSA key files through %s are placed in data directory.Skipping generation of RSA key pair as %s is set to OFF.'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode.The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account.The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account.Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed.'user' entry '%s@%s' ignored in --skip-name-resolve mode.Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure.User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore.User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore.Found invalid password for user: '%s@%s'; Ignoring user'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored.Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Found an entry in the 'db' table with empty database name; Skipped'db' entry '%s %s@%s' ignored in --skip-name-resolve mode.'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE.The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure.Fatal error: Can't open and lock privilege tables: %sFatal: can't initialize grant subsystem - '%s''procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.'procs_priv' entry '%s' ignored, bad routine type'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode.Failed to add %s in extra_users. Binary log entry may miss some of the users.Unable to start server. The data dictionary schema '%s' does not exist.Unable to start server. The data dictionary table '%s' does not exist.Failed to initialize DD Storage EngineFound partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found .frm file with same name as one of the Dictionary Tables.Created Data Dictionary for upgradeCan't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive.Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters.Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!Not enough memory for messagefile '%s'Can't read from messagefile '%s'Found incompatible DECIMAL field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!Found incompatible YEAR(x) field '%s' in %s; Please do "ALTER TABLE `%s` FORCE" to fix it!'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changedFound wrong key definition in %s; Please do "ALTER TABLE `%s` FORCE " to fix it!Unable to open file %sError in reading file %sTable '%s' was created with a different version of MySQL and cannot be readUnable to read view %sFile %s has unknown type in its header.Incorrect information in file %sCan't open and lock privilege tables: %sPlugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported.Plugin '%s' has invalid data.Fatal error: OOM while initializing time zonesCan't open and lock time zone table: %s trying to live without themFatal error: Out of memory while loading mysql.time_zone_leap_second tableFatal error: While loading mysql.time_zone_leap_second table: too much leapsFatal error: Error while loading mysql.time_zone_leap_second tableFatal error: Illegal or unknown default time zone '%s'Can't find description of time zone '%.*s'Can't find description of time zone '%u'Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type idError while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviationsError while loading time zone description from mysql.time_zone_transition_type tableError while loading time zone description from mysql.time_zone_transition table: too much transitionsError while loading time zone description from mysql.time_zone_transition table: bad transition type idError while loading time zone description from mysql.time_zone_transition tableloading time zone without transition typesOut of memory while loading time zone descriptionUnable to build mktime map for time zoneOut of memory while loading time zoneFatal error: Out of memory while setting new time zoneReplica SQL thread is stopped because UNTIL condition is bad(%s:%llu).Replica SQL thread stopped because it reached its UNTIL position %lluReplica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already appliedReplica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %sReplica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %sReplica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session.Group Replication plugin is not installed.The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client.Failed to delete the row: '%s' from the gtid_executed table.Failed to compress the gtid_executed table.Failed to compress the gtid_executed table, because it is failed to allocate the THD.Failed to initialize thread attribute when creating compression thread.Can not create thread to compress gtid_executed table (errno= %d)Could not join gtid_executed table compression thread. error:%dCan't start server : Initialize security descriptor: %sCan't start server : Set security descriptor: %sCan't start server : Named Pipe "%s" already in use.NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning.NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %lluNDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu.NDB Replica: missing data for %s timestamp column %u.NDB Replica: Table %s.%s logging exceptions to %s.%sNDB Replica: Table %s.%s : %s, low epoch resolutionFound unexpected field type %uFailed to create NdbInfoFailed to init NdbInfondb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u%s - %s.%s%sInfo table is not ready to be used. Table '%s.%s' cannot be opened.Info table is not ready to be used. Table '%s.%s' cannot be scanned.Corrupted table %s.%s. Check out table definition.Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead.Choosing worker id %lu, the following is going to be %luTransaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLEFor the creation of replication channels the server id must be different from 0Replica: Wrong repository. Repository should be TABLEError creating connection metadata: %s.Error changing the type of connection metadata's repository: %s.It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change.Error creating applier metadata: %s.Error changing the type of applier metadata's repository: %s.Could not delete from Replica Workers info repository.Could not store the reset Replica Worker state into the replica info repository.Error in checking %s repository info type of %s.Replica: %sReplica: Could not create channel listReplica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE.Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it.Failed to initialize the connection metadata structure%sReplica: Failed to create a channel from connection metadata repository.Failed to create a new info file (file '%s', errno %d)Failed to create a cache on info file (file '%s')Failed to open the existing info file (file '%s', errno %d)Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs.Unknown cost constant "%s" in mysql.server_cost tableInvalid value for cost constant "%s" in mysql.server_cost table: %.1fUnknown cost constant "%s" in mysql.engine_cost tableUnknown storage engine "%s" in mysql.engine_cost tableInvalid device type %d for "%s" storage engine for cost constant "%s" in mysql.engine_cost tableInvalid value for cost constant "%s" for "%s" storage engine and device type %d in mysql.engine_cost table: %.1fError while reading from mysql.server_cost table.Error while reading from mysql.engine_cost table.Failed to open optimizer cost constant tablesUnsupported non-ignorable event fed into the event stream.GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s.QUERY(BEGIN) is not expected in an event stream in the middle of a %s.QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s.QUERY(XA ROLLBACK) is not expected in an event stream %s.Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user.Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege.Event Scheduler: %serror during compilation of %s.%sEvent Scheduler: Dropping %s.%sNdb schema[%s.%s]: %sIn RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s.root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.A temporary password is generated for root@localhost: %sFailed to open the bootstrap file %sBootstrapping complete--initialize specified but the data directory has files in it. Aborting.--initialize specified on an existing data directory.--initialize specified but the data directory exists and the path is too long. Aborting.--initialize specified but the data directory exists and is not writable. Aborting.Creating the data directory %sStart binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)source sends heartbeat messagethe rest of heartbeat info skipped ...Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process themNDB: Query '%s' failed, error: %d: %sKilling thread %luPlugin %s is deinitializing a thread but left a session attached. Detaching it forcefully.Failed to detach the session.Closed forcefully %u session%s left opened by plugin %sFailed to decrement the number of threadsPlugin %s did not deinitialize %u threadsKilled %u threads of plugin %sNDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %sNDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica startNDB: NodeID is %lu, management server '%s:%lu'tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%uNDB Internal error: Default values differ for column %u, ndb_default: %dNDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%ufield[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]fix_unique_index_attr_order: my_malloc(%u) failureNDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica.NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica.NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster.NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster.Error %lu in readAutoIncrementValue(): %sfound uncommitted autocommit+rbwr transaction, commit status: %dNdb replica retried transaction %u time(s) in vain.  Giving up.Error %lu in ::update_create_info(): %sNDB: allocating table share for %s failedNDB Binlog: (%d)%sNDB Binlog: CREATE TABLE Event: %sNDB Binlog: FAILED CREATE TABLE event operations. Event: %sNDB Binlog: RENAME Event: %sNDB Binlog: FAILED create event operations during RENAME. Event %sUnexpected rename case detected, sql_command: %dError %lu in ::get_auto_increment(): %sCalling ndbcluster_create_binlog_setup(%s) in ::opentable '%s' opened read onlyNDB: '--initialize' -> ndbcluster plugin disabledNDB: Changed global value of binlog_format from STATEMENT to MIXEDNDB_SHARE: trailing share %s, released by close_cached_tablesNDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak.handle_trailing_share: %s use_count: %undbcluster_get_share: %s use_count: %undbcluster_real_free_share: %s use_count: %undbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)ndbcluster_free_share: %s use_count: %undbcluster_mark_share_dropped: %s use_count: %undbcluster_mark_share_dropped: destroys share %sCould not allocate Thd_ndb objectNDB Binlog: Ndb tables initially read only.ndb util thread: malloc failure, query cache not maintained properlyTrying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignoredTrying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %sdbug_check_shares open:  %s.%s: state: %s(%u) use_count: %udbug_check_shares dropped:Invalid (old?) table or database name '%s'Recovering after a crash using %sCannot perform automatic crash recovery when --tc-heuristic-recover is usedBad magic header in tc logRecovery failed! You must enable exactly %d storage engines that support two-phase commit protocolCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}Heuristic crash recovery modeHeuristic crash recovery failedPlease restart mysqld without --tc-heuristic-recoverFailed to create or recover replication info repositories.Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread.Replica: Could not start replica for channel '%s'. operation discontinuedReplica: Could not stop replica for channel '%s' operation discontinuedError during --relay-log-recovery: Could not locate rotate event from the source.Error during --relay-log-recovery: Error reading events from relay log: %dError during --relay-log-recovery: Error while freeing IO_CACHE objectRelay log recovery skipped for group replication channel.Error during --relay-log-recovery: %sError during --relay-log-recovery: Could not read relay log index file due to an IO error.Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively.Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen.MTA recovery: starting coordinator thread to fill MTA gaps.MTA recovery: failed to start the coordinator thread. Check the error log for additional details.MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA.Failed to open the relay log '%s' (relay_log_pos %s).MTA recovery: completed successfully.Server id not set, will not start replica%sCan't create replica thread%s.The replica IO thread%s was killed while executing initialization query '%s'The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s.Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."SELECT UNIX_TIMESTAMP()" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)Failed to flush connection metadata repository.The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s.Error on %s: %d  %s, will retry in %d secsError reading packet from server%s: %s (server_errno=%d)Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %sMulti-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %lluReplica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu.Error initializing relay log position%s: %sReplica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %sReplica I/O thread%s killed while connecting to sourceReplica I/O thread couldn't register on sourceForcing to reconnect replica I/O thread%sFailed on request_dump()%sLog entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packetStopping replica I/O thread due to out-of-memory error from sourceReplica I/O thread aborted while waiting for relay log spaceReplica I/O thread exiting%s, read up to log '%s', position %sFailed during replica worker initialization%sReplica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %lluError looking for %s.Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu.Error looking for file after %s.This an error cnt != mta_checkpoint_periodFailed during replica worker thread creation%sFailed during replica worker thread creation%s (errno= %d)Failed to init partitions hashReplica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup valueReplica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' Replica (additional info): %s Error_code: MY-%06dReplica: %s Error_code: MY-%06dError loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sError running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log '%s' position %sReplica SQL thread%s exiting, replication stopped in log '%s' at position %sRead invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bugThe queue event failed for channel '%s' as its configuration is invalid.An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu.'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source.Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %snext log '%s' is activenext log '%s' is not activeReplica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)Error reading relay log event%s: %s'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'.Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources.log %s listed in the index, but failed to stat.Could not find first log while counting relay log space.Unable to use replica's temporary directory '%s'.Path '%s' is a directory name, please specify a file name for --relay-log option.Path '%s' is a directory name, please specify a file name for --relay-log-index option.Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem.Failed in open_index_file() called from Relay_log_info::rli_init_info().Failed in init_gtid_sets() called from Relay_log_info::rli_init_info().Failed in open_log() called from Relay_log_info::rli_init_info().Error writing relay log configuration.get_ndb_blobs_value: my_malloc(%u) failedNDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u.NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributedNDB: Creating %s.%sNDB: Flushing %s.%sNDB: Cleaning stray tables from database '%s'NDB: Discovered missing database '%s'NDB: Discovered remaining database '%s'NDB: ndbcluster_find_all_databases retry: %u - %sNDB: ndbcluster_find_all_databases fail: %u - %sNDB: skipping setup table %s.%s, in state %dNDB: failed to setup table %s.%s, error: %d, %sNDB: missing frm for %s.%s, discovering...NDB: mismatch in frm for %s.%s, discovering...ndb_binlog_setup: Clean up leftoversNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %sNDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08xNDB %s: distributing %s timed out. Ignoring...NDB %s: not waiting for distributing %sNDB: distributed %s.%s(%u/%u) type: %s(%u) query: '%s' to %x%08xNDB: distribution of %s.%s(%u/%u) type: %s(%u) query: '%s' - complete!NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08xNDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08xNDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %dNDB: unknown value for binlog signalling 0x%X, %s not loggedNDB: reply to %s.%s(%u/%u) from %s to %x%08xNDB: Could not release slock on '%s.%s', Error code: %d Message: %sNDB schema: Could not find table '%s.%s' in NDBNDB: Discarding event...no obj: %s (%u/%u)NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08xNDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d.NDB Binlog: handling online alter/renameNDB Binlog: Failed to re-open shadow table %s.%sNDB Binlog: handling online alter/rename doneNDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. Got dist_priv event: %s, flushing privilegesNDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08xNDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%sNDB Schema dist: cluster failure at epoch %u/%u.NDB Binlog: ndb tables initially read only on reconnect.NDB Schema dist: unknown event %u, ignoring...NDB Binlog: Opening ndb_binlog_index: %d, '%s'NDB Binlog: Unable to lock table ndb_binlog_indexNDB Binlog: Injecting random write failureNDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d.NDB Binlog: Writing row (%s) to ndb_binlog_index - %sNDB Binlog: Failed committing transaction to ndb_binlog_index with error %d.NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdownNDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqldsNDB: server id provided is too large to be represented in opt_server_id_bits or is reservedNDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1.NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITENDB Binlog: %s%s%sNDB Replica: Table %s.%s : Parse error on conflict fn : %sNDB Replica: Table %s.%s : %sNDB Binlog: Failed to get table %s from ndb: %s, %dNDB Binlog: NOT logging %sNDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %sNDB Binlog: CREATE (DISCOVER) TABLE Event: %sNDB Binlog: DISCOVER TABLE Event: %sNDB Binlog: logging of table %s with BLOB attribute and no PK is not supportedNDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %sNDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %sNDB Binlog: discover reusing old ev opNDB Binlog: Creating NdbEventOperation failed for %sNDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %sNDB Binlog: ndbevent->execute failed for %s; %d %sNDB Binlog: logging %s (%s,%s)NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %sNDB %s: %s timed out. Ignoring...NDB Binlog: unhandled error %d for table %sNDB Binlog: cluster failure for %s at epoch %u/%u.NDB Binlog: unknown non data event %d for %s. Ignoring...NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)remove_all_event_operations: Remaining open tables:   %s.%s, use_count: %uNDB: Could not get apply status shareNDB Binlog: Server shutdown detected while waiting for ndbcluster to start...NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch.NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlogNDB Binlog: starting log at epoch %u/%uNDB Binlog: ndb tables writableNDB Binlog: Server shutdown detected...NDB Binlog: Just lost schema connection, hanging aroundNDB Binlog: ...and on our wayNDB: error %lu (%s) on handling binlog schema eventNDB Binlog: Failed to inject apply status write rowNDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %dNDB Binlog: Error during COMMIT of GCI. Error: %dNDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%uNDB Binlog: Release extra share referencesNDB Binlog: remaining open tables:   %s.%s state: %u use_count: %uWrong tree: Parent doesn't point at parentWrong tree: Root should be blackWrong tree: Found two red in a rowWrong tree: Found right == leftWrong tree: Incorrect black-count: %d - %dUse_count: Wrong count %lu for origin %pUse_count: Wrong count for key at %p, %lu should be %luWrong number of elements: %u (should be %u) for tree at %pError reading replica worker configurationError writing replica worker configurationFailed to open relay log %s, error: %sError when worker read relay log events,relay log name %s, position %lluFailed to find next relay log when retrying the transaction, current relay log is %sMulti-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu.Failed to write the DROP statement for temporary tables to binary logWhen opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary logCouldn't repair table: %s.%sCould not remove temporary table: '%s', error: %dSystem table '%.*s' is expected to be transactional.Error writing source configuration.Error reading source configuration.SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support.Plugin '%s' of type %s failed deinitializationPlugin '%s' has ref_count=%d after deinitialization.Shutting down plugin '%s'Plugin '%s' registration as a %s failed.Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.Couldn't load plugin named '%s' with soname '%s'.plugin-load parameter too longPlugin '%s' will be forced to shutdownPlugin '%s' has ref_count=%d after shutdown.Unknown variable type code 0x%x in plugin '%s'.Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flagMissing variable name in plugin '%s'.Thread local variable '%s' not allocated in plugin '%s'.Out of memory for plugin '%s'.Bad options for plugin '%s'.Parsing options for plugin '%s' failed.Plugin '%s' is disabled.Plugin '%s' has conflicting system variablesSetting persistent options for plugin '%s' failed.Failed on my_net_write, writing to stderr instead: %sRetrying repair of: '%s' without quickRetrying repair of: '%s' with keycacheFound %s of %s rows when repairing '%s'Warning: Optimize table got errno %d on %s.%s, retryingWarning: Enabling keys got errno %d on %s.%s, retryingChecking table:   '%s'Recovering table: '%s'Error in creating TABLE_SHARE from %s.frm file.Unable to acquire lock on %s.%sError in allocation memory for TABLE object.Error in creating handler object for table %s.%sError in setting handler reference for table %s.%sUnable to acquire lock on tablespace name %sError in processing generated columns for table %s.%sError in Creating DD entry for %s.%sError in fetching %s.%s table data from dictionaryError in fixing SE data for %s.%sError in creating stored program '%s.%s'Unable to open db.opt file %s. Using default Character set.Unable to intialize IO cache to open db.opt file %s. Unable to identify the charset in %s. Using default character set.db.opt file not found for %s database. Using default Character set.Event '%s'.'%s': invalid value in column mysql.event.time_zone.Event '%s'.'%s': has invalid time zone value Event '%s'.'%s': invalid value in column mysql.event.character_set_client.Event '%s'.'%s': invalid value in column mysql.event.collation_connection.Failed to open mysql.event Table.Parsing '%s.%s' routine body failed.%sFailed to open mysql.proc Table.Failed to read mysql.proc table.Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again.Unable to open the data directory %s during clean up after upgrade failedFailed to set path %sFailed to open dir %sNDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'.NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'.NDB: using nodeid %uNDB: failed to allocate global ndb cluster connectionNDB: failed to allocate global ndb objectNDB[%u]: using nodeid %uNDB[%u]: failed to allocate cluster connect objectNDB[%u]: starting connect threadNDB[%u]: NodeID: %d, %sNDB[%u]: failed to start connect threadNDB: error (%u) %sIgnored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs providedEvent Error: An error occurred while creating query string, before writing it into binary log.Event Scheduler: Error while loading from disk.Event Scheduler: Error getting event object.Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corruptedUnable to obtain lock for dropping event %s from schema %sUnable to drop event %s from schema %sServer overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase.Unable to resize binlog IOCACHE auxiliary filefile %s was not purged because it was being read by thread number %uI/O error reading the header from the binary log, errno=%d, io cache code=%dFailed to open log (file '%s', errno %d)Failed to create a cache on log (file '%s')Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files.Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files.Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs.Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.MYSQL_BIN_LOG::open_index_file failed to sync the index file.Error reading GTIDs from relaylog: %d%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state.Error reading GTIDs from binary log: %dRead %lu events from binary log file '%s' to determine the GTIDs purged from binary logs.MYSQL_BIN_LOG::open failed to generate new file name.MYSQL_BIN_LOG::open failed to sync the index file.Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.While rebuilding index file %s: Failed to close the index file.While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process.While rebuilding index file %s: Failed to rename the new index file to the existing index file.After rebuilding the index file %s: Failed to open the index file.MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file.Failed to locate old binlog or relay log filesFailed to delete file '%s'MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name.MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file.next log error: %d  offset: %s  log: %s included: %d%s failed to open the crash safe index file.%s failed to copy index file to crash safe index file.%s failed to close the crash safe index file.%s failed to move crash safe index file to index file.MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index.MYSQL_BIN_LOG::purge_logs failed to sync the index file.MYSQL_BIN_LOG::purge_logs failed to copy %s to register file.MYSQL_BIN_LOG::purge_logs failed to flush register file.MYSQL_BIN_LOG::purge_logs failed to update the index fileMYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged.MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name.MYSQL_BIN_LOG::open_purge_index_file failed to open register file.MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for readMYSQL_BIN_LOG::purge_index_entry error %d reading from register file.Failed to execute mysql_file_stat on file '%s'Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog filesFailed to delete file '%s' and read the binlog index fileFailed to delete log file '%s'%s An incident event has been written to the binary log which will stop the replicas.find_log_pos() failed (error: %d)Recovering after a crash using %sFailed to open the crashed binlog file when source server is recovering it.Failed to trim the crashed binlog file when source server is recovering it.Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes.Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it.Failed to run 'after_sync' hooks%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.Failed to run 'after_flush' hooksCrash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}The following warning was suppressed %d times during the last %d seconds in the error logNDB: %sNDB %s: %sNDB: Unable to purge %s.%s File=%s (failed to setup thd)Unknown collation #%lu.syntax error in innodb_log_group_home_dirsyntax error in innodb_undo_directoryInnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name.InnoDB: Invalid page size=%lu.InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lfInnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu%s and %s file names seem to be the same.Transaction not registered for MySQL 2PC, but transaction is activeMySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back.InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%luCannot find index %s in InnoDB index dictionary.Found index %s whose column info does not match that of MySQL.Failed to open table %s.Build InnoDB index translation table for Table %s failedTable %s has a primary key in InnoDB data dictionary, but not in MySQL!Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table.Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB.Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system.Cannot replace error message (%s,%s,%s) "%s" with "%s"; wrong number or type of %% subsitutions.Table for error message replacements could not be found or read, or one or more replacements could not be applied.%s: %sTable '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %sCommand '%s' cannot be aborted. The trigger error was (%d) [%s]: %sEvent '%s' cannot be aborted. The trigger error was (%d) [%s]: %s%s. The trigger error was (%d) [%s]: %sReplica SQL: Configuration with number of replication sources = %u' is not supported when applying to NdbReplica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to NdbNDB %s: distributing %s err: %uStoring MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information.FLUSH RELAY LOGS cannot be performed on channel '%-.192s'.Replica channel '%s' does not exist.Can't find symbol '%-.128s' in library.Can't open shared library '%-.192s' (errno: %d %-.128s).Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege.Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size.Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size.Can't generate a unique log-filename %-.200s.(1-999).Error reading file '%-.200s' (errno: %d - %s)Error writing file '%-.200s' (errno: %d - %s)%s Statement: %s%s: Forcing close of thread %ld  user: '%-.48s'.%s: Shutdown complete (mysqld %s)  %s.Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict.GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.'%s' is deprecated and will be removed in a future release. Please use %s instead.Triggers for table `%-.64s`.`%-.64s` have no creation context'%-.192s' has an old format, you should re-create the '%s' object(s)View `%-.64s`.`%-.64s` has no creation contextLong database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS.Table upgrade required. Please do "REPAIR TABLE `%-.64s`" or dump/reload to fix it!Got error %d - '%-.192s' from storage engine.Access denied for user '%-.48s'@'%-.64s'Access denied for user '%-.48s'@'%-.64s' (using password: %s)Access denied for user '%-.48s'@'%-.64s'. Account is locked.Your password has expired. To log in you must change it using a client that supports expired passwords.Storage engine '%s' does not support system tables. [%s.%s].Sort aborted%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s.Unknown locale: '%-.64s'.Unknown collation: '%-.64s'.Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap spaceOut of memory; restart server and try again (needed %d bytes)COLLATION '%s' is not valid for CHARACTER SET '%s'Failed to set %s at or around "%s" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s).Generating a new UUID: %s.Failed to get absolute path of program executable %sFailed to bootstrap performance schema components infrastructure.Failed to deinit performance schema components infrastructure.Could not open duplicate fd for %s: %s.System views initialization failed.Resource group post initialization failed.Resource Group subsystem initialization failed.Failed to start mysqld daemon. Check mysqld error log.Cannot change to root directory: %s.Failed to bootstrap persistent privileges.Basedir set to %s.Could not add wild do table rule '%s'!Could not add wild ignore table rule '%s'!The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.Cannot set services "%s" requested in --log-error-services, using defaults.Performance schema tables initialization failed.The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s.Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again.The replication timestamps have returned to normal values.%s.Failed to write an incident event into stmt_cache.Relaylog file %s size was %llu, but was truncated at %llu.Unable to purge relay log files. %s:%s.Replica: failed in creating filter for channel '%s'.Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure.ACL table mysql.%.*s missing. Some operations may fail.Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles.Can't set mandatory_role: There's no such authorization ID %s@%s.Table '%-192s' failed to move/insert a row from part %d into part %d: %s.Skipped updating resource group metadata in InnoDB read only mode.Failed to persist resource group %s to Data Dictionary.Failed to deserialize resource group %s.Update of resource group %s failed.Validation of resource group %s failed. Resource group is disabled.Unable to allocate memory for Resource Group %s.Failed to allocate memory for resource group hash.Failed to add resource group %s to resource group map.Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD).Unable to apply resource group controller %s.Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored.PFS %s notification function registration failed.Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s).Unable to bind thread id %llu to cpu ids (error code %d - %-.192s).Unbind thread id %llu failed. (error code %d - %-.192s).Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s).Unable to determine CAP_SYS_NICE capability.%s failed: Failed to get handle for thread %llu.Retrieval of thread priority unsupported on %s.Unable to determine the number of CPUs.Resource group feature shall not be available. Incompatible thread handling option.Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d].bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s).bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s).%s failed: processor_affinity failed (error code %d - %-.192s).Error in renaming mysql_index_stats.ibd.Error in opening data directory %s.Error in fetching list of tablespaces.Error in acquiring Tablespace for SDI insertion %s.Error in resolving Engine name for tablespace %s with engine %s.Error in creating SDI for %s tablespace.Error in storing SDI for %s tablespace.Error in fetching list of tables.Finished populating Data Dictionary tables with data.Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d.Got error %d from SE while migrating tablespaces.Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command.Finished migrating TABLE statistics data.Error in creating Index statistics entry. Fix statistics data by using ANALYZE command.Finished migrating INDEX statistics data.Failed to find valid data directory.Starting upgrade of data directory.Failed to initialize DD Storage Engine.Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again.Found partially upgraded DD. Upgrade will continue and start the server.Error in upgrading engine logs.Error in updating SDI information.Skip updating %s metadata in InnoDB read-only mode.Created system views with I_S version %d.Unknown error detected %d in handler.Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d.The row data is greater than 4GB, which is too big to write to the binary log.Unable to construct DROP EVENT SQL query string.Unable to binlog drop event %s.%s.Failed to start replica threads for channel '%s'.%s%s.Failed registering on source, reconnecting to try again, log '%s' at position %s. %s.Replica I/O thread killed during or after reconnect.Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted.Failed to add a replication filter into filter map for channel '%.192s'.There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded.There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded.An error occurred while building do_table and ignore_table rules to hashes for per-channel filter.Clone plugin cannot be loaded.Clone Handler exists.Could not create Clone Handler.The CYCLE timer is not available. WAIT events in the performance_schema will not be timed.The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed.Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow.Failed to allocate %zu bytes for buffer '%s' due to out-of-memory.InnoDB could not find index %s key no %u for table %s through its index translation table.Cannot find index %s in InnoDB index translation table.InnoDB could not find key no %u with name %s from dict cache for table %s.InnoDB: change_active_index(%u) failed.Stored ref len is %lu, but table ref len is %lu.MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s.Cannot create table %s.Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index.InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL.Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group.Default value is not defined for this set option. Please specify correct counter or module name.InnoDB: Monitor %s is already enabled.Invalid monitor counter : %s.LoadLibrary("%s") failed: GetLastError returns %lu.%s.%s.%s.%s.%s.%s.Unable to wait for process %lld.Unable to determine if daemon is running: %s (rc=%d).%s[FATAL] InnoDB: %sThe syntax '%s' is deprecated and will be removed in a future release. Please use %s instead.The syntax '%s' is deprecated and will be removed in a future release.'%s' is deprecated and will be removed in a future release.%sBinary logging not possible. Message: %s.Failed to set persisted options.Cannot acquire specified service implementation: '%.192s'.Invalid VCPU range %u-%u.Invalid cpu id %u.Got error %d during FLUSH_LOGS.Problem while dropping database. Can't remove database directory (%s). Please remove it manually.The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored.malformed or very old relay log which does not have FormatDescriptor.Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters.Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!Error in updating version number in %s tablespace.Keyring migration failed.Keyring migration successful.Received RESTART from user %s.  Restarting mysqld (Version: %s).Different lower_case_table_names settings for server ('%u') and data dictionary ('%u').Data dictionary initializing version '%u'.Data dictionary restarting version '%u'.Data dictionary upgrading from version '%u' to '%u'.Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'.Upgrading the data dictionary from dictionary version '%u' is not supported.Upgrading the data dictionary failed, temporary schema name '%-.192s' not available.Data dictionary minor downgrade from version '%u' to '%u'.Minor downgrade of the Data dictionary from dictionary version '%u' is not supported.No data dictionary version number found.Thread pool not supported, requires a minimum of %s.thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d.thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d.thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm.thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server.Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294.thread_pool_max_unused_threads cannot be set higher than %d.Failed to instantiate the connection handler object.Failed to initialize thread pool plugin.Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d.Can't setup connection teardown thread-specific data.Creation of connect handler thread failed.Failed to create thd and authenticate connection.Failed to process connection event.Can't create pool thread (error %d, errno: %d).%.*s.tp_group_low_level_init() failed.Rearm failed even after 30 seconds, can't continue without notify socket.%s: %s buffer is too smallMecab v%s is not supported, the lowest version supported is v%s.Mecab v%s is not verified, the highest version supported is v%s.Mecab: Trying createModel(%s).Mecab: createModel() failed: %s.Mecab: createTagger() failed: %s.Mecab: Unsupported dictionary charset %s.Mecab: Loaded dictionary charset is %s.Mecab: parse() failed: %s.Mecab: parse() failed: out of memory.Mecab: createLattice() failed: %s.---> %s enter.<--- %s exit (%d).<--- %s exit (%s).<--- %s exit.Semi-sync replication initialized for transactions.%s: transaction node allocation failed for: (%s, %lu).%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu).%s: insert (%s, %lu) in entry(%u).%s: probe (%s, %lu) in entry(%u).%s: cleared all nodes.%s: cleared %d nodes back until pos (%s, %lu).Read semi-sync reply magic number error.Read semi-sync reply length error: packet is too small.Read semi-sync reply binlog file length too large.%s: Got reply(%s, %lu) from server %u.%s called twice.Semi-sync replication enabled on the source.Cannot allocate memory to enable semi-sync on the source.Semi-sync replication disabled on the source.SEMISYNC: Forced shutdown. Some updates might not be replicated.%s: Got reply at (%s, %lu).%s: signal all waiting threads.%s: wait pos (%s, %lu), repl(%d).%s: Binlog reply is ahead (%s, %lu).%s: move back wait position (%s, %lu).%s: init wait position (%s, %lu).%s: wait %lu ms for binlog sent (%s, %lu).Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu.Assessment of waiting time for commitTrx failed at wait position (%s, %lu).Semi-sync replication switched OFF.Semi-sync replication switched ON at (%s, %lu).No enough space in the packet for semi-sync extra header, semi-sync replication disabled.%s: server(%d), (%s, %lu) sync(%d), repl(%d).Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu.%s: Transaction skipped at (%s, %lu).Semi-sync source failed on net_flush() before waiting for replica reply.The received ack is smaller than m_greatest_ack.Add the ack into slot %u.Update an exsiting ack in slot %u.Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d).Starting ack receiver thread.Failed to wait on semi-sync dump sockets, error: errno=%d.Stopping ack receiver thread.Failed to register replica to semi-sync ACK receiver thread.Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu).Stop %s binlog_dump to replica (server_id: %d).unregister_trans_observer failed.unregister_binlog_storage_observer failed.unregister_binlog_transmit_observer failed.unregister_replicator OK.Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE).%s: reply - %d.Missing magic number for semi-sync packet, packet len: %lu.Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu.%s: reply (%s, %lu).Semi-sync replica net_flush() reply failed.Semi-sync replica send reply failed: %s (%d).Execution failed on source: %s; error %dSource server does not support semi-sync, fallback to asynchronous replicationSet 'rpl_semi_sync_replica=1' on source failedFailed to stop ack receiver thread on my_thread_join, errno(%d).Failed to read the firewall tablesFailed to register dynamic privilegesStatement was truncated and not recorded: %sStatement with no text was not recordedSUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %sACCESS DENIED for '%s'. Reason: %s Statement: %sSkipped unknown user mode '%s'Reloading cache from diskFIREWALL RESET for '%s'Counters are reset to zero%sAudit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release.Previously exclude list is used, now we start using include list, exclude list is set to NULL.Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy.Both include and exclude lists provided, include list is preferred, exclude list is set to NULL.Could not access '%s' directory.Could not rename file from '%s' to '%s'.File '%s' should not exist. It may be incomplete. The server crashed.Could not rename file from '%s' to '%s'. Remove the file manually.Incomplete file renamed from '%s' to '%s'.Error writing file '%-.200s' (errno: %d - %s).Could not initialize audit log file encryption.Could not initialize audit log file compression.Could not create '%s' file for audit logging.Audit log file (%s) must be manually renamed before audit_log_flush is set to true.%sError parsing JSON event. Event not accessible.Buffer is too small to hold JSON event. Number of events skipped: %zu.Could not open JSON file for reading. Reading next file if exists.JSON file parsing error. Reading next file if existsInvalid column count in the '%s.%s' table.Invalid column definition of the '%s.%s' table.Could not store field of the %s table.Could not update %s table.Could not insert into %s table.Could not delete from %s table.Could not initialize %s table for reading.Could not read %s table.Could not close %s table reading.Both user and host columns of %s table cannot be empty.Filtername column of %s table cannot be empty.Dictionary file not specifiedDictionary file not loadedDictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loadedException while reading the dictionary fileCan't retrieve the %s from the security contextCan't retrieve the security contextEffective value of validate_password_length is changed. New value is %d%sRewritten query failed to parse:%sStartup failed with error "%s"ExitingExit doneUsing SSL configuration from MySQL ServerUsing SSL configuration from Mysqlx PluginNeither MySQL Server nor Mysqlx Plugin has valid SSL configurationUsing %s for TLS connectionsFor more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation%sFailed to parse stored authentication string for %s. Please check if mysql.user table not corruptedError in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problemAuthentication requires either RSA keys or SSL encryptionRSA key cipher length of %u is too long. Max value is %uFailed to open the %s filter tablesFailed to open '%s.%s' %s table%s%s%sPassword salt for user '%s' is corruptOut of memory for component system variable '%s'.variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag.Unknown variable type code 0x%x in component '%s'.Parsing options for variable '%s' failed.Setting persistent options for component variable '%s' failed.The log-filter component "%s" got confused at "%s" (state: %s) ...Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it.Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server.Unable to collect information for column '%-.192s': %-.192s.'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous.A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding.Configuring persisted options failed: "%s".The storage engine '%-.192s' does not provide dynamic table statisticsThis option cannot be set %s.The table '%-.192s' may not be created in the reserved tablespace '%-.192s'.SSL fips mode error: %sinit_connect variable is ignored for user: %s host: %s due to expired password.sql_mode=0x%08x is not supportedOut of memory.Wrong column count or names when loading rules.Some rules failed to load.Got error from storage engine while refreshing rewrite rules.Failed to initialize Connection_event_coordinatorFailed to update connection delay triggered statsFailed to reset connection delay triggered statsUnexpected option type for connection delay.Failed to initialize Connection_delay_actionCould not set %s delay for connection delay.Failed to update connection delay hash for account : %s%s: Force stopping client because exception occurred: %s%s.%u: Maximum number of authentication attempts reached, login failed.Error allocating Buffer_page: %sDetected %u hanging client(s)Error accepting clientInternal error scheduling client for executionPreparation of I/O interfaces failed, X Protocol won't be accessiblesrv_session_init_thread returned errorUnable to use user mysql.session account when connecting the server for internal plugin requests.For more information, please see the X Plugin User Account section in the MySQL documentation%s: Unexpected exception dispatching command: %sException in post: %sInternal error scheduling taskException in event loop: "%s": %sSetup of %s failed, %s%sFailed at SSL configuration: "%s"Error during SSL handshake for client connection (%i)%s: Error during SSL handshake%s: Error creating session for connection from %s%s: Error initializing session for connection: %s%s: Message of size %u received, exceeding the limit of %iMessage is not properly initialized: %sUnable to set minimal number of workers to %u; actual value is %iUnable to accept connection, disconnecting clientAll I/O interfaces are disabled, X Protocol won't be accessible%s: Invalid message %i received during client initialization%s: closing client because of shutdown (state: %i)%s: Error reading from socket %s (%i)%s: peer disconnected while reading message bodyclient_id:%s - %s while reading from socket, closing connection%s.%u: Invalid authentication method %s%s: Unexpected message of type %i received during authenticationError writing to client: %s (%i)Scheduler "%s" started.Scheduler "%s" stopped.Please see the MySQL documentation for '%s' system variables to fix the errorX Plugin ready for connections. %sRetrying `bind()` on TCP/IP port %iShutdown triggered by mysqld abort flagUsing %s account for authentication which has all required permissionsUsing existing %s account for authentication. Incomplete grants will be fixedServer starts handling incoming connectionsStopped handling incoming connections%s: Could not interrupt client session%s: release triggered by timeout in state:%iIPv6 is availableUNIX socket not configuredKill client: %i %sCould not get security context for sessionUnable to switch security context to rootError closing SQL sessionError executing admin command %s: %sError executing empty admin commandUnable to retrieve system variable '%s'Unable to get creation stmt for collection '%s'; query result size: %luUnable to get engine info for collection '%s'; creation stmt: %sError getting result data: %sCapability expired password failed with error: %sFailed to set SO_REUSEADDR flag (error: %d).Could not open internal MySQL sessionUnable to switch context to user %sCan't unregister '%s' user defined function%s: get peer address failed, can't resolve IP to hostnameCapability client interactive failed with error: %sFailed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only.Invalid key typeInvalid key length for given block cipherCould not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets providedkeyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets providedkeyring_file initialization failure due to internal exception inside the plugin.Failed to generate a key due to internal exception inside keyring_file pluginError while %s key: invalid key_typeError while %s key: key_id cannot be emptyFailed to %s due to internal exception inside %s pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileError while reading stat for %s.Please check if file %s was not removed. OS returned this error: %sCould not remove file %s OS retuned this error: %sCould not truncate file %s. OS retuned this error: %sUnknown error %dkeyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path%sError while loading keyring content. The keyring might be malformedCould not flush keys to keyringCould not flush keys to keyring's backupError while fetching key: key_id cannot be emptyError while removing key: key_id cannot be emptyFor keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materialskeyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running.keyring_okv initialization failure due to internal exception inside the pluginInvalid key typeInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_okv pluginCould not find entry for server in configuration file %sCould not find entry for standby server in configuration file %sCould not parse the %s file providedCould not load keys' uids from the OKV serverCould not initialize ssl layerCould not initialize OKV clientCould not connect to the OKV serverCould not remove the keyCould not add attribute, attribute_name=%s attribute value=%sCould not generate the key.Could not store the key.Could not activate the key.Could not fetch generated keyCould not store/generate the key - failed to set key attribute x-key-readyCould not retrieve key signature from custom attributesCould not retrieve key from OKVError loading trust storeError setting the certificate file.Error setting the key file.Private key does not match the certificate public keyIncorrect Keyring fileKeyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value.Found malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileKeyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value.keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided pathCould not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets providedThe keyring_encrypted_file_password must be set to a valid value.Too long keyring_encrypted_file_password value.keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct.keyring_encrypted_file initialization failure due to internal exception inside the pluginFailed to generate a key due to internal exception inside keyring_encrypted_file pluginkeyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct.keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct.Could not open keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %sCould not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %sPath to keyring aws configuration file cannot be emptyPath to keyring_aws storage file cannot be empty.Unable to create/access keyring directory.Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location.keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Serverkeyring_aws_cmk_id has to be setCould not get AWS KMS credentials from the configuration filekeyring_aws initialization failure.keyring_aws initialization failure due to internal exception inside the pluginInvalid key length for given block cipherFailed to generate a key due to internal exception inside keyring_file pluginIncorrect Keyring fileFound malformed keyring backup file - removing itError while restoring keyring from backup file cannot overwrite keyring with backupError while flushing in-memory keyring into keyring fileWrong regionCould not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %sCould not generate a new key. AWS KMS returned this error: %sCould not encrypt key. AWS KMS returned this error: %sCould not re-encrypt key. AWS KMS returned this error: %sCould not decrypt key. AWS KMS returned this error: %sCould not rotate the CMK. AWS KMS returned this error: %sThe requested GTID '%s:%lld' was already used, the transaction will rollback.The group replication applier thread was killed.Error at event handling! Got error: %d.Error when extracting group GTID execution information, some recovery operations may face future issues.An error occurred when trying to reduce the Certification information size for transmission.Failed to create group replication pipeline applier cache!Unblocking the group replication thread waiting for applier to start, as the start group replication was killed.The group replication applier pipeline was not properly disposed. Check the error log for further info.The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group.Fatal error during execution on the Applier process of Group Replication. The server will now leave the group.Error stopping all replication channels while server was leaving the group. %sError sending single primary message informing that primary did apply relay logs.Error updating transaction snapshot version after transaction being positively certified.Error fetching transaction sidno after transaction being positively certified.Broadcast of committed transactions message failed.Unable to parse the group_replication_group_name during the Certification module initialization.Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization.Error updating group_gtid_executed GITD set during the Certification module initialization.Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error.Error when establishing a server connection during the Certification module initialization.Error when extracting this member GTID executed set. Certification module can't be properly initialized.Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization.Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized.Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization.Error during Certification module initialization.Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction.Error updating transaction snapshot version reference for internal storage.Error fetching transaction sidno while adding to the group_gtid_executed set.Error while ensuring the sidno be present in the group_gtid_executed.Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name.Invalid stable transactions set.Error updating stable transactions set.There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues.Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing.Null packet on certifier's queue.Error reading GTIDs from the message.Error processing stable transactions set.Error processing intersection of stable transactions set.Error setting stable transactions set.Error reading group_gtid_extracted from the View_change_log_event.Error reading the write set item '%s' from the View_change_log_event.Error during certification_info initialization.Primary had applied all relay logs, disabled conflict detection.Message received while the plugin is not ready, message discarded.Message received without a proper group replication applier.Error processing message in Certifier.This server was not declared online since it is on status %s.This server was declared online within the replication group.When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually.The member with address %s:%u was declared online within the replication group.Member with address %s:%u has become unreachable.Member with address %s:%u is reachable again.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership.This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership.A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option.The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked.Members removed from the group: %sPrimary server with address %s left the group. Electing new Primary.Members joined the group: %sThere was a previous plugin error while the member joined the group. The member will now exit the group.Group membership changed to %s on view %s.Group membership changed: This member has left the group.Member was expelled from the group due to network failures, changing member status to ERROR.Unable to open session to (re)set read only mode. Skipping.A new primary with address %s:%u was elected. %sUnable to disable super read only flag. Try to disable it manuallyUnable to set super read only flag. Try to set it manually.This server is working as primary member.This server is working as secondary member with primary member address %s:%u.Unable to set any member as primary. No suitable candidate.Error when activating super_read_only mode on start. The member will now exit the group.Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate.Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery.There is already a member with server_uuid %s. The member will now exit the group.Error when extracting information for group change. Operations and checks made to group joiners may be incomplete.Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete.Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete.The START GROUP_REPLICATION command failed since the group already has 9 members.Member version is incompatible with the group.The member contains transactions not present in the group. The member will now exit the group.It was not possible to assess if the member has more transactions than the group. The member will now exit the group.Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join.Error processing local GTID sets when comparing this member transactions against the group.This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %sThe member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group.The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group.The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s]).Error stopping all replication channels while server was leaving the group. %sDetected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs.Unknown error occurred while resetting applier's module logs.Failed to setup the group replication applier thread.Error while starting the group replication applier threadFailed to stop the group replication applier thread.Failed to fetch transaction data containing required transaction info for applierCan't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known.Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member.Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication.Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication.Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication.group_replication_auto_increment_increment is reset to %luauto_increment_offset is reset to %lugroup_replication_auto_increment_increment is set to %luauto_increment_offset is set to %luFailed to fetch transaction context containing required transaction info for certificationFailed to fetch Format_description_log_event containing required server info for applierFailed to fetch Transaction_context_log_event containing required transaction info for certificationFailed to read snapshot version from transaction context event required for certificationFailed to fetch Gtid_log_event containing required transaction info for certificationUnable to update certification result on server side, thread_id: %luUnable to add gtid information to the group_gtid_executed set when gtid was provided for local transactionsUnable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactionsFailed to notify certification outcomeUnable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactionsUnable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactionsFailed to fetch View_change_log_event containing required info for certificationError when contacting the server to ensure the proper logging of a group change in the binlogTimeout when waiting for the server to execute local transactions in order assure the group change proper loggingFailed to fetch Log_event containing required server info for applierUnable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade.Failed to establish an internal server connection to execute plugin operationsSetting super_read_only=ON.Setting super_read_only=OFF.killed session id: %d status: %dkilled failed id: %d failed: %dInternal query: %s result in error. Error number: %ldError copying from empty string Query execution resulted in failure. errno: %dUnable to create a session for executing the queries on the serverThe member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connectionMaximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery.All donors left. Aborting group replication incremental recovery.Establishing group recovery connection with a possible donor. Attempt %d/%dRetrying group recovery connection with another donor. Attempt %d/%dNo valid donors exist in the group, retryingError when configuring the asynchronous recovery channel connection to the donor.Establishing connection to a group replication recovery donor %s at %s port: %d.Error while creating the group replication recovery channel with donor %s at %s port: %d.There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery.Error while starting the group replication incremental recovery receiver/applier threadsTerminating existing group replication donor connection and purging the corresponding logs.Error when stopping the group replication incremental recovery's donor connectionError when purging the group replication recovery's relay logsUnable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown.Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown.Unexpected error when notifying an internal component named %s regarding a group membership event.An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!No memory to generate write identification hashBase 64 encoding of the write identification hash failedBinlog format should be ROW for Group Replicationbinlog_checksum should be NONE for Group ReplicationA transaction_write_set_extraction algorithm should be selected when running Group ReplicationTransaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group ReplicationTransaction cannot be executed while Group Replication is stopping.Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE.Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the pluginTransaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the pluginWe can only use one cache type at a time on session %uFailed to reinit binlog cache log for read on session %uFailed to create the context of the current transaction on session %uFailed to extract the set of items written during the execution of the current transaction on session %uFailed to gather the set of items written during the execution of the current transaction on session %uError on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option.Error while re-initializing an internal cache, for read operations, on session %uError while appending data to an internal cache on session %uError while writing to transaction message on session %uUnable to register for getting notifications regarding the outcome of the transaction on session %uError broadcasting transaction to the group on session %u. Message is too big.Error while broadcasting the transaction to the group on session %uError while waiting for conflict detection procedure to finish on session %uError while re-initializing an internal cache, for write operations, on session %uFailed to create group replication commit cache on session %uFailed to reinit group replication commit cache for write on session %uA previous recovery session is still running. Please stop the group replication plugin and wait for it to stopFatal error during the incremental recovery process of Group Replication. The server will leave the group.Error stopping all replication channels while server was leaving the group. %sUnable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption.Only one server alive. Declaring this server as online within the replication groupError when processing certification information in the incremental recovery processUnable to ensure the execution of group transactions received during recovery.Error while sending message in the group replication incremental recovery process.Unable to read the server value for the super_read_only variable.Unable to read the server values for the read_only and super_read_only variables.Unable to reset the server read mode settings. Try to reset them manually.Due to a plugin error, some transactions were unable to be certified and will now rollback.Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the serviceThis server is working as secondary member with primary member address %s:%u.Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0.group_replication_force_members must be empty on group start. Current value: '%s'It was not possible to guarantee the initialization of plugin structures on server startCould not enable the server read only mode and guarantee a safe recovery executionError on group communication engine initializationCan't start group replication on secondary member with single-primary mode while asynchronous replication channels are running.Error on group communication engine startTimeout on wait for view after joining groupError calling group communication interfacesMember server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s.Member configuration: member_id: %lu; member_uuid: "%s"; single-primary mode: "%s"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: "%s";Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information.Skipping leave operation: concurrent attempt to leave the group is on-going.Skipping leave operation: member already left the group.Going to wait for view modificationWhile leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more detailsRequesting to leave the group despite of not being a memberPlugin 'group_replication' is stopping.Plugin 'group_replication' has been stopped.On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed.On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more detailsOn shutdown there was a timeout on the Group Replication applier termination.Unexpected failure while shutting down registry module!Failure during Group Replication handler initializationFailure when registering the server state observersFailure when registering the transactions state observersFailure when registering the binlog state observersUnable to start Group Replication on bootFailure when stopping Group Replication on plugin uninstallFailure when unregistering the server state observersFailure when unregistering the transactions state observersFailure when unregistering the binlog state observersAll Group Replication server observers have been successfully unregisteredUnable to parse the group_replication_group_name.Unable to parse the group_replication_group_name.Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete.Unable to initialize the Group Replication applier module.Group Replication applier module successfully initialized!Group communication SSL configuration: group_replication_ssl_mode: "%s"; server_key_file: "%s"; server_cert_file: "%s"; client_key_file: "%s"; client_cert_file: "%s"; ca_file: "%s"; ca_path: "%s"; cipher: "%s"; tls_version: "%s"; tls_ciphersuites: "%s"; crl_file: "%s"; crl_path: "%s"; ssl_fips_mode: "%s"MySQL server does not have SSL support and group_replication_ssl_mode is "%s", START GROUP_REPLICATION will abortGroup communication SSL configuration: group_replication_ssl_mode: "%s"Unable to initialize the group communication engineBinlog must be enabled for Group ReplicationGtid mode should be ON for Group ReplicationLOG_REPLICA_UPDATES should be ON for Group ReplicationExtraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm.Applier metadata repository must be set to TABLEConnection metadata repository must be set to TABLE.In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'.Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads.It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled.error_message: %sThe group_replication_group_name option is mandatoryThe group_replication_group_name '%s' is not a valid UUID, its length is too bigThe group_replication_group_name '%s' is not a valid UUIDgroup_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quotagroup_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quotaThe given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limitThere is one group_replication_force_members operation already ongoinggroup_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachableInitialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'Unknown group replication applier pipeline requestedUnable to bootstrap group replication event handling infrastructure. Unknown handler type: %dOne of the group replication applier handlers is null due to an initialization errorA group replication applier handler, marked as unique, is already in use.A group replication applier handler role, that was marked as unique, is already in use.Error on group replication applier handler initializationError when initializing a session thread for internal server connection.Error running internal SQL query: %s. The internal server communication session is not initializedError running internal SQL query: %s. The internal server session was killed or server is shutting down.Error running internal SQL query: %s. Got internal SQL error: %s(%d)Error running internal SQL query: %s. Internal failure.Error, maximum number of retries exceeded when waiting for the internal server session state to be operatingError when trying to fetch security context when contacting the server for internal plugin requests.There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly.Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i.Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %sThis member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option.The server was automatically set into read only mode after an error was detected.Unable to log notification to table (errno: %lu) (res: %d)! Message: %sFailure in group communication engine '%s' initializationUnable to set the group communication engine loggerCurrent debug options are: '%s'.Some debug options in '%s' are not valid.Error calling group communication interfaces while trying to leave the groupMember is not ONLINE, it is not possible to force a new group membershipError calling group communication interfacesError setting group_replication_force_members value '%s' on group communication interfacesThe group_replication_force_members value '%s' was set in the group communication interfacesTimeout on wait for view after setting group_replication_force_members value '%s' into group communication interfacesBroadcast of committed transactions message failed. Message is too big.Error while sending stats messageFlow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%dFlow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lldUnable to convert a packet into an event on the applier. Error: %sFailed to create group replication pipeline cache.Failed to reinit group replication pipeline cache for write.Unable to convert the event into a packet on the applier. Error: %sFailed to flush group replication pipeline cache.Failed to reinit group replication pipeline cache for read.Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details.%sThe replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica IO thread of channel '%s' will error out as the member failed to come ONLINE.The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now.The replica applier thread of channel '%s' will error out as the member failed to come ONLINE.LDAP authentication initialize: failed to create/ get connection from the pool. LDAP authentication de_initialize FailedSkipping group search, No group attribute mentionedPool max size is 0, connection pool is disabledConnection pool initialization, failed to create LDAP object creatorConnection pool initialization, failed to create LDAP objectLDAP TLS configurationLDAP TLS connectionLDAP pool is not created.LDAP pool is initializingLDAP pool is de-initializingPool max size old and new values are 0LDAP pool is re-initializingPlug-in has failed to write the packet.Setting LDAP user name as : %sUser authentication data: %s size: %luUser is authenticated as: %s external user: %sGroup search information base DN: %s scope: %d filter: %s attribute: %sSpecial handling for group search, {GA} foundGroup search special handling, group full DN found. User %s is not member of any group.User %s is member of more than one groupFor user %s has multiple user group names. Please check if group attribute name is correctSearched group name: %sLDAP authentication object creation time_stamp: %s dn: %sCertificate name: %sFailed to pool de-initialized: pool is already reconstructingPool initialization failed: pool is already initializedPool initialization failed: pool is initializingPool initialization failed: pool is de-initializingFailed to pool deinitialized: pool is already reconstructingFailed to pool deinitialized : pool is not readyLdap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializingConnection pool has failed to initializedLdap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit.Set max pool size failed.Plug-in has failed to read the packet from clientLdap_authentication::initialize: creating new LDAP connection. Ldap_authentication::initialize: getting connection from pool. Ldap_authentication::de_initialize putting back connection in the poolLdap_authentication::search_user_group no group attribute foundLdap_connetion_pool::put ldap info nullLdap_connection_pool::put connection is freeing. Ldap_connection_pool::put connection in pushed in the poolLdap_connection_creator::Ldap_connection_creatorstarting TLSLdap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)Ldap_connection_pool::deinit: deleting connection key %s Ldap_connection_pool::get pooled connection key: %sLdap_connection_pool::get create connection key: %sLDAP communication host %s port %uSending authentication method to client : %sSASL request received from mysql client: %sLdap_sasl_authentication::process_sasl rc: %sLdap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %sLDAP authentication started for user name: %s%sLDAP authentication initialize is failed with: %sLDAP authentication failed or group retrieval failed: %sSearch user group has failed: %sLDAP user bind has failed: %sConnection pool get: Failed to create LDAP connection. %sFailed to create new LDAP connection:  %sFailed to establish TLS connection:  %sFailed to search user full dn: %sLdap_connection_pool::reinitThe path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket.Failed to connect to systemd notification socket named %s. Error: '%s'Failed to write '%s' to systemd notification. Error: '%s'Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s.Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory.Can't start server: can't check PID filepath: %svalidate_password status variables registration failed.validate_password status variables unregistration failed.Dictionary file open failedgiven password string could be nullfailed to convert the password string to lower casefailed to convert the password string into a buffermemory allocation failed for string handlerSince the validate_password_policy is mentioned as Strong, dictionary file must be specifiedconvert_to_buffer service failed%s variable registration failed.%s variable unregistration failed.Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet.Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sFailed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sPage still fixed or dirty at shutdown. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sWaited for %u secs for hash index ref_count (%zu) to drop to 0. index: "%s" table: "%s"%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sTable flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!Can't read encryption key from file %s!Cannot close file %s, because n_pending_flushes %zuCannot close file %s, because modification count %lld != flush count %lldCannot close file %s, because it is in useOpen file list len in shard %zu is %lluTablespace %s, waiting for IO to stop for %lld seconds%s%s%s%s%sYou must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu.Max tablespace id is too high, %luTrying to access missing tablespace %luTrying to close/delete tablespace '%s' but there are %lu pending operations on it.Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it.%sCannot delete tablespace %lu because it is not found in the tablespace memory cache.While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %sCannot delete tablespace %lu in DISCARD TABLESPACE: %sCannot rename '%s' to '%s' for space ID %lu because the source file does not exist.Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again.Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended.Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID.Rename waiting for IO to resumeCannot find tablespace for '%s' in the tablespace memory cacheCannot find tablespace for '%s' in the tablespace memory cacheTablespace '%s' is already in the tablespace memory cacheCannot create file '%s'The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL.posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information.Could not write the first page to tablespace '%s'File flush of tablespace '%s' failedCould not find a valid tablespace file for `%s`. %sIgnoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID%s%s%s%sCan't set encryption information for tablespace %s!%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories.%s%s%s%s%s%s%s%s%s%s%s%s%sScan path '%s' is ignored because %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sA general tablespace cannot be located under the datadir. Cannot open file '%s'.A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCannot create a tablespace for table %s because the directory is not a valid location. %s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s).%s%sBlocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it.innodb_log_buffer_size was extended to %lu bytes.The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu.The age of the last checkpoint is %llu, which exceeds the log group capacity %llu.Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %sRedo log was encrypted, but keyring plugin is not loaded.Read redo log encryption metadata successful.Can't set redo log tablespace encryption metadata.Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists.Can't set redo log tablespace to be encrypted in read-only mode.Can't set redo log tablespace to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Flush waiting for archiver to catch up lag LSN: %lluFlush overwriting data to archive - wait too long (1 minute) lag LSN: %llu%sStarting shutdown...Waiting for %s to exitWaiting for %lu active transactions to finishWaiting for master thread to be suspendedWaiting for page_cleaner to finish flushing of buffer poolPending checkpoint_writes: %lu. Pending log flush writes: %lu.Waiting for %lu buffer page I/Os to completeMySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!Background thread %s woke up during shutdownWaiting for archiver to finish archiving page and logBackground thread %s woke up during shutdownWaiting for dirty buffer pages to be flushedLog sequence number at shutdown %llu is lower than at startup %llu!Waiting for archiver to finish archiving page and log############### CORRUPT LOG RECORD FOUND ###############Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %lluHex dump starting %llu bytes before and ending %llu bytes after the corrupted record:Set innodb_force_recovery to ignore this error.The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s%llu pages with log records were left unprocessed!Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %sUpgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s%s%sRedo log format is v%lu. The redo log was created before MySQL 8.0.30.Unknown redo log format (v%lu) in file %s. Please follow the instructions at %sNo valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort.Applying a batch of %llu redo log records ...%s%sApply batch completed!%s%s%s%s%s%sAn optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.
This offline backup may not be consistentExtending tablespace : %lu space name: %s to new size: %lu pages during recovery.Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery.Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu.Recovery skipped, --innodb-read-only set!Log scan progressed past the checkpoint LSN %llu.Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu.Set innodb_force_recovery to ignore this error.Doing recovery: scanned up to log sequence number %lluDatabase was not shutdown normally!Starting crash recovery.The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redoCannot restore from mysqlbackup, InnoDB running in read-only mode!The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore.Opening cloned databaseRedo log is from an earlier version, v%lu.Redo log format v%lu not supported. Current supported format is v%lu.Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu.The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!Can't initiate database recovery, running in read-only-mode.We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!Waiting for recv_writer to finish flushing of buffer poolRecovery parsing buffer extended to %zu.Out of memory while resizing recovery parsing buffer.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sCan't encrypt data of redo log%s%sDecryption of redo log block at offset %llu in file %s failed because there's no keyring configured%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOld log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.comSemaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung.Waiting for %llu table(s) to be droppedWaiting for change buffer merge to complete number of bytes of change buffer just merged: %lluCan't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0.Can't set undo tablespace(s) to be encrypted in read-only-mode.Can't set undo tablespace '%s' to be encrypted.Can't set undo tablespace '%s' to be encrypted. Failed to write header page.Can't set undo tablespace '%s' to be encrypted. Error %d - %sEncryption is enabled for undo tablespace '%s'.Can't rotate encryption on undo tablespace '%s'.Encryption is enabled for undo tablespace '%s'.os_file_get_status() failed on '%s'. Can't determine file permissions.%s can't be opened in %s mode.'%s' not a regular file.Cannot create %sSetting file %s size to %llu MB. Progress : %u%%Cannot resize redo log file %s to %llu MB (%s)Cannot create redo log files in read-only mode (--innodb-read-only).Redo log encryption is enabled, but the keyring is not loaded.Failed to create redo log file %s (error: %d) for start LSN %lluRenaming log file %s to %sNew redo log files created, LSN=%lluUnable to open '%s' (error: %d).Cannot create construction log file '%s' for undo tablespace '%s'.Creating UNDO Tablespace %sSetting file %s size to %llu MBPhysically writing the file fullError in creating %s: probably out of disk spaceCan't set encryption metadata for space %sCannot read first page of '%s' - %sUndo tablespace number %lu was being truncated when mysqld quit.Cannot recover a truncated undo tablespace in read-only modeReconstructing undo tablespace number %lu.Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?UNDO tablespace %s must be %sError creating file for %sError reading encryption for %sUnable to open undo tablespace number %luOpened %llu existing undo tablespaces.Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces.Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found.Could not create undo tablespace '%s'.Error %d - %s - opening newly created undo tablespace '%s'.Created %llu undo tablespaces.Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctlyEncryption is enabled for undo tablespace number %lu.Unable to initialize the header page in undo tablespace number %lu.Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions.Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces.Deleting %llu new independent undo tablespaces that we just created.Waiting for purge to startCreating shared tablespace for temporary tablesThe %s data file must be writable!Could not create the shared %s.Unable to create the shared %s.The %s data file cannot be re-opened after check_file_spec() succeeded!%d threads created by InnoDB had not exited at shutdown!InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again.Plugin initialization aborted %swith error %s.Waiting for %zu buffer page I/Os to complete.PUNCH HOLE support availablePUNCH HOLE support not availableSize of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory.Database upgrade cannot be accomplished in read-only mode.Database upgrade cannot be accomplished with innodb_force_recovery > 0%s%s%s%s%s%s%s%s%s%sMySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang.Compressed tables use zlib %s%sStartup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime.%sUnable to create monitor file %s: %sDisabling background ibuf IO read threads.Cannot initialize AIO sub-systemInitializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c Cannot allocate memory for the buffer poolCompleted initialization of buffer poolSmall buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up.Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.Only one redo log file foundThe redo log file %s size %llu is not a multiple of innodb_page_sizeThe redo log file %s is of different size %llu bytes than other log files %llu bytes!Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only.Cannot open DD tablespace.Starting to delete and rewrite redo log files.Undo from 5.7 found. It will be purged%s%sTablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database.Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pagesCannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.%s started; log sequence number %lluWaiting for purge to completeWaiting for dict_stats_thread to exitQuery counter shows %lld queries still inside InnoDB at shutdownShutdown completed; log sequence number %lluCannot continue operation.%s%s%s%s%s%s%s%s%sUnable to read the existing undo truncate log file '%s'. The error is %sUndo tablespace %s is marked for truncate%sTruncating UNDO tablespace %s%sCannot create truncate log for undo tablespace '%s'.%sFailed to truncate undo tablespace '%s'.%sCompleted truncate of undo tablespace %s.%s%s%s%s%s%s%s%s%s%s%s%s%s%sRollback of non-prepared transactions completed%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sBlocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back.%sgettimeofday() failed: %sCan't create UNDO tablespace %s %s%sResizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sOut of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity.%sLog writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity.Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity.%s%s%s%sCan't set redo log files to be encrypted in read-only mode.Can't set redo log files to be encrypted.Can't set redo log tablespace to be encrypted.Redo log encryption is enabled.Waiting for archiver to finish archiving page and logStarting shutdown...Waiting for %s to exit.Waiting for rollback of %zu recovered transactions, before shutdown.Waiting for master thread to be suspended.Waiting for page_cleaner to finish flushing of buffer pool.Shutdown is waiting for %zu buffer page I/Os to complete.MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!%s%s%s%s%s%s%s%s%s%sInvalid redo log header checksum.Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9%sCannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s%s%sUser has set innodb_thread_concurrency to %lu.STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete.STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete.Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables.Statement violates GTID consistency: CREATE TABLE ... SELECT.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log.When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log.When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%.Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s).%s: Normal shutdown.Can not perform keyring migration : %s.The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group.An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed tableThe lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'.A capture group has an invalid name.Variable '%-.64s' can't be set to the value of '%-.200s'Stopping services failed with error "%s"Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'Got fatal error %d from source when reading data from binary log: '%-.512s'Replication event checksum verification failed while reading from network.Failed to create %sFatal error: %sUnexpected source's heartbeat data: %sThe incident %s occurred on the source. Message: %sSource command %s failed: %sRelay log read failure: %sRelay log write failure: %sReplica failed to initialize connection metadata structure from the repositoryReplica failed to initialize applier metadata structure from the repositoryGot a packet bigger than 'max_allowed_packet' bytesAccess to %.64s '%.64s.%.64s' is rejected.Unknown errorUnknown system variable '%-.64s'A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %sAborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)Out of sort memory, consider increasing server sort buffer size!The table '%-.192s' is full!Create table/tablespace '%-.192s' failed, as disk is full.Handler reported error %d - %sIncorrect information in file: '%-.200s'Can't open file: '%-.200s' (OS errno: %d - %s)Can't find file: '%-.200s' (OS errno: %d - %s)'%-.192s' is locked against change (OS errno: %d - %s)Cannot load from %s.%s. The table is probably corrupted!Error in diagnostics area: MY-%06d - %sIncorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'.The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure.Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'Replica SQL thread ignored the query because of replicate-*-table rulesCannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld.Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld.Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld.Simulated error%sAudit Log filtering has not been installed.Failed to open the %s filter tables.Failed to open '%s.%s' %s table.Filter name cannot be empty.Invalid character in the user name.Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operationNo keyring installed.Invalid character in the host name.Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one.Could not create AES key. OpenSSL's EVP_BytesToKey function failed.Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption.Could not reinitialize audit log filters.User cannot be empty.First character of the user name must be alphanumeric.Specified filter has not been found.Cannot upgrade server earlier than 5.7 to 8.0%s (mysqld %s) initializing of server in progress as process %lu%s (mysqld %s) initializing of server has completedCannot boot server version %lu on data directory built by version %llu. Downgrade is not supportedReceived SHUTDOWN from user %s. Shutting down mysqld (Version: %s).The plugin encountered a critical error and will abort: %sInvalid match mode flag in regular expression.The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica.Cannot update GTID_PURGED with the Group Replication plugin running'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure.Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'.No paths allowed for shared library.Function '%-.192s' already exists.Got Error: %ld from SetEvent.Error allocating SSL BIO.%sOne or several locations were inaccessible while checking PID filepath.Currently unknown variable '%s' was read from the persisted config file.Fatal error in defaults handling. Program aborted!Duplicate variable name '%s'.Failed to initialize system variables.Variable name '%s' not found.Some (%d) threads are still active%sSource tablespace is encrypted but target tablespace is not.Waiting for tablespace_alter_encrypt_thread to exit%s%s%s%s%s%s%s%s%s: Could not add suppression rule for code "%s". Rule-set may be full, or code may not correspond to an error-log message.Invalid value for command line option bind-addresses: '%s'Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled.Error when extracting GTID execution information: %sMessage received without a proper group coordinator module.A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'.A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group.Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'.A primary election was invoked but the requested primary member is not in the group. Request ignored.Error while sending message. Context: %sError while executing a group configuration operation: %sConfiguration operation '%s' terminated. %sStarting group operation local execution: %sTermination of group operation local execution: %sA configuration change was killed in this member. The member will now leave the group as its configuration may have diverged.There was an issue on the primary election process: %s The member will now leave the group.There was an issue when stopping a previous election process: %sIt was not possible to initialize stage logging for this task. The operation will still run without stage tracking.Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove itCould not uninstall Group Replication UDF functions. Try to remove them manually if present.Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the pluginThe function '%s' failed. %sDo not specify the current password while changing it for other users.Incorrect current password. Specify the correct password which has to be replaced.Current password needs to be specified in the REPLACE clause in order to change it.Variable '%-.64s' can't be set to the value of '%-.200s'%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident.Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT.Secondary engine operation failed. %s.DDLs on a table with a secondary engine defined are not allowed.Unable to allocate temporary tablespace for this sessionUnable to switch security context to user: %sStatement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT.Error in parsing %s '%s'.'%s' during upgrade. %sThe designated data directory %s is unusable. You can remove all files that the server added to it.Group search rebinding via root DN: %s Error installing plugin '%s': %sError uninstalling plugin '%s': %sPartitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade.Cannot determine the type of the tablespace named '%s'.%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead.The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented.Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platformDisabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %sCould not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes.sql_mode=0x%08x has been removed and will be ignoredFailed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource.Number of pools: %zuUsing undo tablespace '%s'.%s Unable to save the current state of tablespace '%s' to the data dictionaryCannot create undo tablespace %s at %s because %d undo tablespaces already exist.Error %d opening newly created undo tablespace %s.SDI Compression failed, Z_BUF_ERRORSDI Compression failed, Z_MEM_ERRORSDI Compression failed, Z_STREAM_ERROR%sExpected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?Cannot use %s as an undo tablespace because it does not end with '.ibu'.ib_undo_trunc_empty_fileib_undo_trunc_before_dd_updateib_undo_trunc_before_done_loggingib_undo_trunc_before_rsegs%s Failed to finish truncating Undo Tablespace '%s'The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE.The directory for tablespace %s does not exist or is incorrect.%sClone donor reported : %.512s.Clone received unexpected response from donor : %.512s.Client: %.512s.Server: %.512s.Failed to initialize the performance schema tables service.Failed to add thread pool performance schema tables.Failed to set datadir to '%-.200s' (OS errno: %d - %s)The innodb_undo_directory is not allowed to be an ancestor of the datadir.Failed to fetch key from keyring, please check if keyring is loaded.Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully.Fetched an invalid key from keyring.Error reading a replication log encryption header: %s.Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually.Key %s exists unexpected.Failed to generate key, please check if keyring is loaded.Failed to store key, please check if keyring is loaded.Failed to remove key, please check if keyring is loaded.Unable to recover binlog encryption master key, please check if keyring is loaded.Failed to initialize binlog encryption, please check if keyring is loaded.Failed to rotate binlog encryption master key at startup, please check if keyring is loaded.Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled.Invalid value for command line option admin-address: '%s'Admin interface ready for connections, address: '%s'  port: %dCan't create thread to handle admin connections (errno= %d)RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords.Empty password can not be retained as second password for user '%s'@'%s'.Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed.Current password can not be retained for user '%s'@'%s' because new password is empty.Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Second password was used for login by user: '%s'@'%s'.Error sending transaction '%d:%lld' prepared message from session '%u'.Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members.Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection.Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection.Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members.Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members.Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare.Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit.Error registering transaction from session '%u' to wait for its dependencies to complete commit.Error on session '%u' while waiting for its dependencies to complete commit.Error registering transaction from session '%u' to wait for sync before execution.Error sending sync before execution message from session '%u'.Error on transaction from session '%u' while waiting for sync before execution.Error releasing transaction for execution on session '%u' after wait for sync before execution.Error waiting for group executed transactions commit on session '%u'.There's no unit of measure named '%s'.The function %s uses %s as a unit, but was passed geometry without units ("SRID 0"). Conversion is not possible.Could not parse key-value pairs in property string '%s'Property key '%s' is invalid.Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery.Failed to encrypt content to write into binlog file: %s.Cannot get the server version number from the dictionary tablespace header.Cannot set the server version number in the dictionary tablespace header.Upgrading the server from server version '%u' is not supported.MySQL server upgrading from version '%u' to '%u'.The certification information could not be set in this server: '%s'A request to force a new group membership was issued when the member is leaving the group.Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table.%sSpecial handling for group search, {GA} not foundUser group retrieval: User object has group informationGroup information found in multiple user objects. Search filter configuration is incorrect.User group retrieval: no group attribute found. Incorrect group search attribute. User group retrieval: Group attribute values is NULL. User group retrieval: parsing DN failed. User group retrieval: Group object has user informationReserved port for ldaps using ldapsGet user proxyGet user proxy: User doesn't belongs to any group, user name will be treated as authenticated user.Get user proxy: configured mapping info: %sGet user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user.Process group proxy mappingCheck delimiter after quoteProcessing delimiterProcessing delimiter, separator = not found, resetting position"Processing delimiter, failed to get data for = separator try for separator ,."Processing delimiter, separator , not found, resetting positionProcessing delimiter: No mapping separator is found, end of group informationGetting next mapping informationParsing mapping, current state: %d  delimiter char: %c Parsing mapping info, LDAP group: %s MySQL proxy: %sMapping parsing errorTrimming left spacesChecking if current characters is quoteNot desired state or un-defined states.Invalid value for named_pipe_full_access_group.Retry the statement using a secondary storage engine.'%s' is deprecated and will be removed in a future release. Please use %s insteadCannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege.Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong.Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution.AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege.'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted.Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'.At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON.At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'.For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges.For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted.'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's versionStarted auto-rejoin procedure attempt %lu of %luTimeout while waiting for a view change event during the auto-rejoin procedureAuto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group.The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group.Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'.Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'.Server upgrade started with version %d, but server upgrade of version %d is still pending.Failed to upgrade server.Server upgrade from '%d' to '%d' %s.Table '%s' requires repair.Table '%s' repair %s.Could not open server upgrade info file '%s' for writing. Please make sure the file is writable.Upgrading the sys schema.Running queries to upgrade MySQL server.Upgrading system table data.Found empty sys database. Installing the sys schema.A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed.A sys schema exists with a sys.version view, but it returns no results.Found outdated sys schema version %s.The sys schema is already up to date (version %s).Found %d sys %s, but expected %d. Re-installing the sys schema.Checking '%s' schema.Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments.Error in DDL Log recovery during Post-Recovery processing.Error in Post-Tablespace-Encryption during Post-Recovery processing.Error in DLL Log cleanup during Post-DDL processing.'%s' statement is unsafe because it uses a system function that may return a different value on the replica.Upgrade of help tables %s.Error when waiting for the server to execute local transactions in order assure the group change proper loggingUnable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process.Cannot grant roles to an anonymous user.Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %sNetwork Namespaces is not supported on this platformUnknown network namespace '%s'Network namespace not allowed for wildcard interface addresssetns() failed with error '%s'Wildcard address value not allowed for multivalued bind addressThe path to a special network namespace file is too long. (got %u > max %u)Cannot create tablespace '%s'. The filepath is too long for this OS.The last block of redo had corrupted first_rec_group and became fixed (%u -> %u).Data dictionary upgrade from version '%u' to '%u' completed.Server SSL certificate doesn't verify: %sTruncated a user name for %s that was too long while reading the persisted variables fileTruncated a host name for %s that was too long while reading the persisted variables fileThe wait_timeout period was exceeded, the idle time since last command was too long.'%s' found not encrypted while '%s' is ON. Trying to encrypt it now.CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !clock_gettime() failed: %sPlugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc.Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it.SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead.FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead.The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica.Member version is read compatible with the group.Lock order disabled (reason: init failed).Keyring ID timestamp value is invalid: '%s'Cannot process audit log file. File name timestamp value is missing or invalid: '%s'Cannot process audit log file. File name does not have required format: '%s'Cannot process audit log file. File name keyring ID value is missing: '%s'Audit log file has been successfully processed: '%s'Could not open audit log file for reading: '%s'Invalid audit log file content: '%s'Cannot read password: '%.32s'.Cannot store password: '%.32s'.Cannot remove password: '%.32s'.'audit_log' password has been copied into '%.32s' and will be removed with first purged password.Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'Can't store an array or an object in a scalar key part of the index '%.192s'Cannot use functional index '%-.64s' due to type or collation conversionExceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytesData too long for functional index '%-.64s'Invalid JSON value for CAST for functional index '%-.64s'Out of range JSON value for CAST for functional index '%-.64s'Empty user dn or password is not allowed, not attempting LDAP bind.Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query.The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made.LOCK_ORDER: Failed to write to file <%s>.LOCK_ORDER: Failed to read from file <%s>.LOCK_ORDER message: %sLock order dependencies file <%s> (%d:%d) - (%d:%d) : %sLock order scanner: (%d:%d) - (%d:%d) : %sThe newly created data directory %s by --initialize is unusable. You can remove it.No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page.%s%s%sClone removing all user data for provisioning: %sNon innodb table: %s.%s is not cloned and is empty.Clone shutting down server as RESTART failed. Please start server to complete clone operation.Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete.There was an issue when configuring the remote cloning process: %sThere was an issue when cloning from another server: %sThere was an issue when trying to evaluate the best distributed recovery strategy while joining.%sNo valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.The group replication plugin could not kill the plugin routine for %s. %sThis member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu.This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs.Distributed recovery will transfer data using: %sDue to some issue on the previous step distributed recovery is now executing: %sDue to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group.The '%s' thread of channel '%s' will error out as the server will attempt to clone another serverUnknown table '%-.129s'Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'.XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect.SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user.Invalid argument typeInvalid argument countaudit_log plugin has not been installed using INSTALL PLUGIN syntax.Invalid "max_array_length" argument type.Failed to write to %s: %s (%s)Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information.Incorrect environment variable %s, invalid port: %sThe server was automatically set into offline mode after an error was detected.A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem.Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression).Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u.Option --protocol-compression-algorithms is reset to default value.Fatal error while compressing outgoing data - %s%sUnknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads.Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration.PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads.The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER.Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512sCannot generate password: '%.32s'Failed to generate a random password for root. Probabably not enough enthropy.Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure).Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored.Directory '%s' will not be scanned because it is a hidden directory.Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel.Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64sThe queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found.PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d.An unexpected event sequence was detected by the SQL thread while applying an event.Updating partition file name '%s' to '%s' and all other partition files during upgradeUpdating partition file name '%s' to '%s' and all other partition files during downgradeUpdating partition file name '%s' to '%s' for importUnable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'%s Too many files have been moved, disabling logging of detailed messagesElected primary member %s: %sSchema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1.Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1.Table Partition: %s is not found in InnoDB dictionaryAccess denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset.%sUpgrade cannot proceed due to an existing prepared XA transaction.Could not allocate memory for key_info when migrating table %s.%sApplier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'Failed to delete 5.7 undo tablespace: %s during upgradeEmpty doublewrite file: %sUsing '%s' for doublewriteError reading doublewrite buffer from the system tablespaceCannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation.The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6The doublewrite filename '%s' is incorrect.%sDoublewrite file create failed: %sDBLWRThread: pthread_setaffinity() failed!%s%sDoublewrite file read failed: %sDump of the data file page:%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sDoublewrite load file %s size %lu is not a multiple of the configured page size %lu"Doublewrite file %s truncate failedDoublewrite file %s failed to writ zerosDoublewrite create file %s size %lu is not a multiple of the configured page size %lu"%s%s%s%s%sCould not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts.Failed to delete 5.7 stat tablespace: %s during upgradeInstalling ndbinfo schema version %sInstalled ndbinfo schema is current. Not upgrading.Failed to upgrade ndbinfo schema.%sInnoDB initialization has started.InnoDB initialization has ended.Could not find appropriate reset points.Unable to flush. Page archiving data may be corrupt in case of a crash.Page archiver's doublewrite buffer for %ld is not valid.Page archiver system's recovery failed.Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*.X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket%sColumn '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release.Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size.Plugin 'group_replication' is starting.Cannot create tablespace %s because the directory is not a valid location. %sScanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used.Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints.Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped.Failed to retrieve IP addresses from enabled host network interfaces.Failed to initialize TLS for channel: %s. See below for the description of exact issue.Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value.Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value.Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency.InnoDB redo logging is disabled. All data could be lost in case of a server crash.InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash.Channel %s configured to support TLS. Encrypted connections are now supported for this channel.No TLS configuration was given for channel %s; re-using TLS configuration of channel %s.Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!Upgrade failed because database contains discarded tablespaces.The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated.The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated.Rollback of non-prepared transactions not completed, due to fast shutdownFound an entry in the 'role_edges' table with empty authorization ID; SkippedFound an entry in the 'role_edges' table with unknown authorization ID '%s'; SkippedFound an entry in the 'default_roles' table with empty authorization ID; SkippedFound an entry in the 'default_roles' table with unknown authorization ID '%s'; SkippedCouldn't insert entry in ddl log for ddl.%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%sThe state of undo tablespace %s is set to active implicitly.The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE.The state of undo tablespace %s is set to 'empty'.Delaying truncate of undo tablespace %s due to clone activity.Delaying truncate of undo tablespace %s due to a metadata lock.Injected debug crash point: %sInjected debug failure point: %sTimeout while waiting for a view change event during the leave step before a auto-rejoin attempt.Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s.Could not execute the installation of UDF functions. Check for other errors in the logCould not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it.Could not uninstall UDF functions. Try to remove them manually if present.An empty or illegal privilege identifier was ignored when global privileges were read from disk.%sA tmpdir temporary path "%s" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it.Error-log destination "%s" is not a file. Can not restore error log messages from previous run.None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log.The schema "%.64s" referenced by %.16s "%.128s" does not exist. Please clean up any orphan %.16s before upgrading.Created undo tablespace '%s'.Dropped undo tablespace '%s'.The InnoDB Encryption Master Key has been rotated in %d tablespaces.Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted.Decrypting a page in doublewrite file failed: %s.Encryption key missing: %s.I/O error while writing to file: %s. Retrying ...Failed to write data to file: %sLog component %s failed to initialize.The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source.The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table.The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table.The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source.%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'.Replica Monitor IO thread exiting.The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table.The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table.Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table.Error %s the channel '%s', the operation will be automatically retried.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelThe integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action.%s%s%s%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiBInnoDB: Size of tablespace %s is more than the maximum size allowed.The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools.Detected misconfiguration: replication channel '%.192s' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL '%.192s', or change GTID_MODE to value ON, before starting the replica receiver thread.Could not acquire required component services.Automatic registration of function(s) failed.Automatic registration of Performance schema table(s) failed.%sFailed to auto-prune file '%s', Error (%d): %sFile '%s' auto-prunedReceived an error while processing components from manifest file: %sReceived an error while unloading components read from manifest file: %sManifest file '%s' is not read-only. For better security, please make sure that the file is read-only.No suitable '%s' service implementation found to fulfill the request.Keyring component initialized successfully.The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component.Keyring component encountered an exception while executing : '%s' API of service: '%s'Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'Empty or 0 values for AES encryption mode and/or block size are not permitted.A valid data identifier is required in order to fetch the key required for the AES operation.Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES.Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'.Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'.Maximum permissible size of data is '%zu' bitsError writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error.Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error.Failed to get metadata from current keys metadata iterator position.Key and value length parameters must not be null.Innodb could not acquire service : %sColumn %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade.'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long.The member action "%s" for event "%s" with priority "%u" will be run.The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure.The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure.Unable to parse the member actions configuration sent by the primary.Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.Unable to parse the member actions configuration sent by the group on member join.Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'.The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members.Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s".Member actions configuration was reset.Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`A deprecated TLS version %s is enabled for channel %sUser profile '%s' loaded. Firewall user profiles are deprecated, consider migrating to group profiles.Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID.Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC.group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATICThe group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channelgroup_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s.The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group.Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS.Unable to parse the group_replication_view_change_uuid.Unable to generate sidno for group_replication_view_change_uuid.Unable to parse the group_replication_view_change_uuid during the Certification module initialization.Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization.Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization.Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error.Unable to retrieve group_replication_view_change_uuid during server checks on replication operations.Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignoredaudit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller.Invalid table definition for '%s.%s'.%sCannot install the %.192s plugin when the %.192s plugin is installed.The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version.%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security.Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security.Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information.There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4.There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6).audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON.Retry the statement using the primary storage engine.Parallel initialization of rseg completeTime taken to initialize rseg using %u thread: %u ms.DDL failed to create a thread to load an index, fall back to single threadDebug_check_no_latching failed, slot->type=%dFailed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections.Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'.Unable to parse the replication failover channels configuration sent by the group on member join.Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group.Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'.This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority.This server is back to the group majority. Replication failover channels handling is resumed.Error incrementing member action configuration version for %s.%s table.The '%s' thread of channel '%s' will error out as this server is a group secondary.Clone DDL Notification: %sClone DDL APPLY: %sClone DDL Invalidate : %sEncryption key is loaded for undo tablespace '%s'.Ignoring encryption INFO size in redo log: %zu, expected: %zuOption --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid.Signature verification failed during registration.Buffer too small to hold registration challenge response.FIDO device authenticator data corrupt.FIDO device signature corrupt.Signature verification failed during authentication.Out of memory.Can't initialize logging serviceReplication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0.The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values.Could not open relay log: %sAuthentication plugin not initialized.Cannot use the generated private key file.Unavailable public key with fingerprint %s for user %s in tenancy %s .Cannot obtain the OCI configuration from the IMDS service.Cannot initialize the IAM service.Invalid authentication string details for user: `%s`@`%s`.None of the groups returned by IAM matches any of the entries from authentication string.User is not part of any groups. However, account is configured to use group mapping.Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s .%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiBThe member %s:%u, with UUID: %s, was set as the single preferred consensus leader.Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.All members were set as consensus leaders.Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong.This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group.Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. "%s".Plugin '%-.192s' is not loaded; Ignoring user%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead.%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead.Missing data directory for ICU regular expressions: %s.More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu.Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher.Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes.Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes.Audit Log is disabled. Enable it with audit_log_disable = false.Option --tls-version or --admin-tls-version is set to an invalid value %s.Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions.Number of STANDBY_SERVER values exceeded maximum limit of 64.Source keyring does not have any keys to migrate.Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available.Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available.Keyring has to be loaded through manifest file in order to support secure storage for persisted variablesCould not find master key %s in keyringA new master key %s could not be generatedFailed to encrypt %s using %sFailed to decrypt %s using %sPersisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file.Using jemalloc.dll for my_malloc and ut::malloc etc.%s.%s.%s.Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator.Thread pool plugin started successfully with parameters: %sthread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0%s%sThe redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6.The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file.Failed to read header of the redo log file %s--initialize specified but the redo log directory %s has redo log files inside. Aborting.Failed to list redo log files in the redo log directory %sNeither found %s subdirectory, nor %s* files in %sCannot restore cloned data directory, InnoDB running in read-only mode!Error %d encountered when writing to the redo log file: %s.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity.Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted.Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity.Redo log reclaimed some free space, resuming user threads.Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead.Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead.Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0.Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only).Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2).The redo log file %s comes from other data directory than redo log file %s.The redo log file %s has invalid start_lsn %llu.The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file).Missing redo log file %s (with start_lsn = %llu).The latest found checkpoint is at lsn = %llu in redo log file %s.User has set innodb_redo_log_capacity to %lluM.Redo log has been requested to resize from %lluM to %lluM.Redo log resize has been cancelled.Redo log has been resized to %lluM.Upgrading redo log: %lluM, LSN=%llu.Marked the current redo log file %s as incomplete.Failed to remove redo log file %s.Failed to rename %s when creating redo log file %s (error: %d)Redo log files created by unknown creator %s.Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0.Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo.Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo.Found redo log files with different formats: %s has format v%lu, %s has format v%lu.Missing ib_logfile0 in the directory %s.Failed to initialize services required to handle redo log PFS tables.Failed to create redo log PFS tables.Truncating redo log file %s...Failed to resize unused redo log file %s to %llu MB (%s).Failed to remove unused redo log file %s.Failed to rename unused redo log file %s to %s.Failed to mark unused redo log file %s as in use (by renaming to %s).Failed to mark redo log file %s as unused (by renaming to %s).Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM.Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead.This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group.Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology.Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files.Crash recovery finished in %s engine. %sFailed to commit %s in %s, with failure code %s.Failed to rollback %s in %s, with failure code %s.Failed to prepare %s in %s, with failure code %s.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Invalid arguments to function '%s'. Expected values: %s.Invalid algorithm value '%.20s' in function %s.Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d].Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message.Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message.Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes).Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message.Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message.Received OpenSSL error in function '%s' for algorithm '%s': '%s'In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'.%s%sSetting session values for system variables only makes sense in a user session (failed to set '%.256s').BuildID[sha1]=%sFailed to register dynamic privilege %s.Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity.%sRecovery: Generating index information for INSTANT DDL Table in 8.0.29 formatFailed to switch resource group. %sFailed to switch resource group. Could not acquire resource groups global lock.Failed to switch resource group. Could not acquire lock on resource group %s.Failed to switch resource group. Unable to apply resource group controller %s.Failed to clear instant drop column metadata for table %sCannot open signing key file %s.Out of memory! Cannot create private key.Cannot read signing key file %s.Incomplete key: missing Name/Type for the Key: %s.Duplicate key found in keyring with Name: %s and Owner: %s.Error parsing JSON response %s.Invalid JSON response!HTTP request failed with error: '%s'Variable thread_pool.%s was updated: %s%sStatus code %u: CompletedStatus code %u: %u%% completeStatus code %u: %sInvalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u.Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per groupFound page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lupreader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zubulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zubulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics.%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication.Bulk executor: %sBulk loader: %sThe first file being loaded contained less lines than the ignore clauseBulk reader: %sBulk reader failed to initialize libcurlBulk reader got libcurl error: %sBulk reader got error response from server: %ldBulk reader got error in communication with source server, check the error log for additional detailsMissing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input.The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'.The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'.Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing.Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing.Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'.Unexpected characters after NULL escape (N) found at row %ld in file '%s'.Unexpected characters after column terminator found at row %ld in file '%s'.Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence.Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%sLOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s.C++ Exception caught while %s the %s plugin: [%s]Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it.Record has both instant and version bit set.This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group.Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files.Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging%sColumn name %s and internally generated INSTANT DROP column name %s is causing a conflict.Field number: %llu too large, Total fields in Record: %zu.%sThe connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'The Replica which was connected to source '%s:%d', is now connected to new source '%s:%d', but still has the same server_uuid %s.The server_uuid for source server '%s:%d' has changed from %s to %s. This should not happen unless you have changed it manually.The source server has changed from '%s:%d' with server_uuid %s, to '%s:%d' with server_uuid %s.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'.Replica receiver thread%s: connected to source '%s@%s:%d' with server_uuid=%s, server_id=%d. Starting GTID-based replication.Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu.Builder::finish(): Completed building index=%s of table=%s, err=%zu.%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead.Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes.SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu.Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version.Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time.Plugin 'group_replication' has been started.Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'.Successfully registered slot '%d' for component '%s'.Successfully de-registered slot '%d' from component '%s'.Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources.Transaction ID: %lu found for resurrecting insertsTransaction ID: %lu found for resurrecting updatesIdentified table ID: %lu to acquire lockAcquired lock on table ID: %lu, name: %sRecords read: %lu - Pages read: %luTotal records resurrected: %lu - Total pages read: %lu - Total tables acquired: %luResurrected %lu transactions doing inserts.Resurrected %lu transactions doing updates.Invalid security token provided by '%s' for '%s'@'%s': %s.Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'.Verification failed for security token provided by '%s' for '%s'@'%s' : %s.Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid.None of the groups extracted from security token matches any of the entries from authentication string.Cannot register variable '%s'. Please check if it is not already registered by another component.Cannot unregister variable '%s'. Please check if it was registered properly in the first place.Cannot register function '%s'. Please check if it is not already registered by another component.Cannot unregister function '%s'. Please check if it was registered properly in the first place.Cannot register privilege '%s'. Please check if it is not already registered.Cannot unregister privilege '%s'. Please check if it was registered properly in the first place.Error while executing UDF %s.Error while executing UDF %s: %s.%s failed.%s failed with %u.Lock failed at %s : %u.Lock from %s : %u failed to unlock.Masking component error: '%s'.%s failed.%s failed because %s.Creation of random context failed.Creation of random context failed because %s.Cannot access %s.%s table.Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted.Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode.init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxingExecution of alter table %s %s failed because %s.TP conn (port: managed(delta), active, opened, closed, added, dropped): %sScheduled run of task %s failedInvalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %dCould not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock.Multi-values cannot be converted to MySQL format: %sHeap required to convert columns is not present.MySQL server downgrading from version '%u' to '%u'.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u.Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not.Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases.Failed to get the data dictionary property %s.Failed to set the data dictionary property %s.Server downgrade from '%d' to '%d' %s.%s information schema from version %u to %u.%s performance schema from version %u to %u.Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details.DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'.Member identified %s: '%s' does not exist on Group Replication membership during %s.Deprecated '%s' used %s times, last time used '%s'.Waiting for %u connections to be closed.Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions.Index %s of %s.%s exceeds limit of %lu bytes per column.Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORYUpon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected.The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order.Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed.%sFailed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast).The Group Replication certifier broadcast thread (THD_certifier_broadcast) started.The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped.The group replication applier thread has received KILL request.Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity.The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity.Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed.Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record.InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu.Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes.PK� �\?�*���	��	messages_to_clients.txtnu�[���# Copyright (c) 2017, 2025, Oracle and/or its affiliates.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2.0,
# as published by the Free Software Foundation.
#
# This program is designed to work with certain software (including
# but not limited to OpenSSL) that is licensed under separate terms,
# as designated in a particular file or component or in included license
# documentation.  The authors of MySQL hereby grant you an additional
# permission to link the program and your derivative works with the
# separately licensed software that they have either included with
# the program or referenced in the documentation.
#
# Without limiting anything contained in the foregoing, this file,
# which is part of C Driver for MySQL (Connector/C), is also subject to the
# Universal FOSS Exception, version 1.0, a copy of which can be found at
# http://oss.oracle.com/licenses/universal-foss-exception.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License, version 2.0, for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA

# If you add messages below that use a short language code that is not listed
# here (as one of the bits after "="), the build will intentionally to catch
# typos or different engineers using different short codes for the same language.
#
languages czech=cze latin2, danish=dan latin1, dutch=nla latin1, english=eng latin1, estonian=est latin7, french=fre latin1, german=ger latin1, greek=greek greek, hungarian=hun latin2, italian=ita latin1, japanese=jpn ujis, korean=kor euckr, norwegian-ny=norwegian-ny latin1, norwegian=nor latin1, polish=pol latin2, portuguese=por latin1, romanian=rum latin2, russian=rus koi8r, serbian=serbian cp1250, slovak=slo latin2, spanish=spa latin1, swedish=swe latin1, ukrainian=ukr koi8u, bulgarian=bgn cp1251;

# The build process will use "eng" by default, but it harmless to repeat it here
default-language eng

################################################################################
# Error numbers below 1000 are reserved for "global errors", that is to say,
# error codes and messages provided by mysys that exist both in clients and
# in the server. They are hard-coded in mysys/errors.cc + include/mysys_err.h
# so we are not defining any messages here, but we do skip the the range to
# prevent collisions with the server's error-numbers.
# The client library's range CR_ERROR_FIRST..CR_ERROR_LAST may overlap with
# with this, but is disjunct.
################################################################################

# See the FAQ at the end of the file for more information!

################################################################################
# Error numbers starting at 1000: server-to-client messages =< 5.6
################################################################################

# The build process automatically starts with this offset
# for messages sent from the server to clients. Setting it
# again here is harmless.
start-error-number 1000

OBSOLETE_ER_HASHCHK
        eng "hashchk"
OBSOLETE_ER_NISAMCHK
        eng "isamchk"
ER_NO
        cze "NE"
        dan "NEJ"
        nla "NEE"
        eng "NO"
        est "EI"
        fre "NON"
        ger "Nein"
        greek "ΟΧΙ"
        hun "NEM"
        kor "아니오"
        nor "NEI"
        norwegian-ny "NEI"
        pol "NIE"
        por "NÃO"
        rum "NU"
        rus "НЕТ"
        serbian "NE"
        slo "NIE"
        ukr "НІ"
ER_YES
        cze "ANO"
        dan "JA"
        nla "JA"
        eng "YES"
        est "JAH"
        fre "OUI"
        ger "Ja"
        greek "ΝΑΙ"
        hun "IGEN"
        ita "SI"
        kor "예"
        nor "JA"
        norwegian-ny "JA"
        pol "TAK"
        por "SIM"
        rum "DA"
        rus "ДА"
        serbian "DA"
        slo "Áno"
        spa "SI"
        ukr "ТАК"
ER_CANT_CREATE_FILE
        cze "Nemohu vytvořit soubor '%-.200s' (chybový kód: %d - %s)"
        dan "Kan ikke oprette filen '%-.200s' (Fejlkode: %d - %s)"
        nla "Kan file '%-.200s' niet aanmaken (Errcode: %d - %s)"
        eng "Can't create file '%-.200s' (errno: %d - %s)"
        est "Ei suuda luua faili '%-.200s' (veakood: %d - %s)"
        fre "Ne peut créer le fichier '%-.200s' (Errcode: %d - %s)"
        ger "Kann Datei '%-.200s' nicht erzeugen (Fehler: %d - %s)"
        greek "Αδύνατη η δημιουργία του αρχείου '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "A '%-.200s' file nem hozhato letre (hibakod: %d - %s)"
        ita "Impossibile creare il file '%-.200s' (errno: %d - %s)"
        jpn "ファイル '%-.200s' を作成できません。(エラー番号: %d - %s)"
        kor "화일 '%-.200s'를 만들지 못했습니다. (에러번호: %d - %s)"
        nor "Kan ikke opprette fila '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje opprette fila '%-.200s' (Feilkode: %d - %s)"
        pol "Nie można stworzyć pliku '%-.200s' (Kod błędu: %d - %s)"
        por "Não pode criar o arquivo '%-.200s' (erro no. %d - %s)"
        rum "Nu pot sa creez fisierul '%-.200s' (Eroare: %d - %s)"
        rus "Невозможно создать файл '%-.200s' (ошибка: %d - %s)"
        serbian "Ne mogu da kreiram file '%-.200s' (errno: %d - %s)"
        slo "Nemôžem vytvoriť súbor '%-.200s' (chybový kód: %d - %s)"
        spa "No puedo crear archivo '%-.200s' (Error: %d - %s)"
        swe "Kan inte skapa filen '%-.200s' (Felkod: %d - %s)"
        ukr "Не можу створити файл '%-.200s' (помилка: %d - %s)"
ER_CANT_CREATE_TABLE
        cze "Nemohu vytvořit tabulku '%-.200s' (chybový kód: %d - %s)"
        dan "Kan ikke oprette tabellen '%-.200s' (Fejlkode: %d - %s)"
        nla "Kan tabel '%-.200s' niet aanmaken (Errcode: %d - %s)"
        eng "Can't create table '%-.200s' (errno: %d - %s)"
        est "Ei suuda luua tabelit '%-.200s' (veakood: %d - %s)"
        fre "Ne peut créer la table '%-.200s' (Errcode: %d - %s)"
        ger "Kann Tabelle '%-.200s' nicht erzeugen (Fehler: %d - %s)"
        greek "Αδύνατη η δημιουργία του πίνακα '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "A '%-.200s' tabla nem hozhato letre (hibakod: %d - %s)"
        ita "Impossibile creare la tabella '%-.200s' (errno: %d - %s)"
        jpn "表 '%-.200s' を作成できません。(エラー番号: %d - %s)"
        kor "테이블 '%-.200s'를 만들지 못했습니다. (에러번호: %d - %s)"
        nor "Kan ikke opprette tabellen '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje opprette tabellen '%-.200s' (Feilkode: %d - %s)"
        pol "Nie można stworzyć tabeli '%-.200s' (Kod błędu: %d - %s)"
        por "Não pode criar a tabela '%-.200s' (erro no. %d - %s)"
        rum "Nu pot sa creez tabla '%-.200s' (Eroare: %d - %s)"
        rus "Невозможно создать таблицу '%-.200s' (ошибка: %d - %s)"
        serbian "Ne mogu da kreiram tabelu '%-.200s' (errno: %d - %s)"
        slo "Nemôžem vytvoriť tabuľku '%-.200s' (chybový kód: %d - %s)"
        spa "No puedo crear tabla '%-.200s' (Error: %d - %s)"
        swe "Kan inte skapa tabellen '%-.200s' (Felkod: %d - %s)"
        ukr "Не можу створити таблицю '%-.200s' (помилка: %d - %s)"
ER_CANT_CREATE_DB
        cze "Nemohu vytvořit databázi '%-.192s' (chybový kód: %d - %s)"
        dan "Kan ikke oprette databasen '%-.192s' (Fejlkode: %d - %s)"
        nla "Kan database '%-.192s' niet aanmaken (Errcode: %d - %s)"
        eng "Can't create database '%-.192s' (errno: %d - %s)"
        est "Ei suuda luua andmebaasi '%-.192s' (veakood: %d - %s)"
        fre "Ne peut créer la base '%-.192s' (Erreur %d - %s)"
        ger "Kann Datenbank '%-.192s' nicht erzeugen (Fehler: %d - %s)"
        greek "Αδύνατη η δημιουργία της βάσης δεδομένων '%-.192s' (κωδικός λάθους: %d - %s)"
        hun "Az '%-.192s' adatbazis nem hozhato letre (hibakod: %d - %s)"
        ita "Impossibile creare il database '%-.192s' (errno: %d - %s)"
        jpn "データベース '%-.192s' を作成できません。(エラー番号: %d - %s)"
        kor "데이타베이스 '%-.192s'를 만들지 못했습니다.. (에러번호: %d - %s)"
        nor "Kan ikke opprette databasen '%-.192s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje opprette databasen '%-.192s' (Feilkode: %d - %s)"
        pol "Nie można stworzyć bazy danych '%-.192s' (Kod błędu: %d - %s)"
        por "Não pode criar o banco de dados '%-.192s' (erro no. %d - %s)"
        rum "Nu pot sa creez baza de date '%-.192s' (Eroare: %d - %s)"
        rus "Невозможно создать базу данных '%-.192s' (ошибка: %d - %s)"
        serbian "Ne mogu da kreiram bazu '%-.192s' (errno: %d - %s)"
        slo "Nemôžem vytvoriť databázu '%-.192s' (chybový kód: %d - %s)"
        spa "No puedo crear base de datos '%-.192s' (Error: %d - %s)"
        swe "Kan inte skapa databasen '%-.192s' (Felkod: %d - %s)"
        ukr "Не можу створити базу данних '%-.192s' (помилка: %d - %s)"
ER_DB_CREATE_EXISTS
        cze "Nemohu vytvořit databázi '%-.192s'; databáze již existuje"
        dan "Kan ikke oprette databasen '%-.192s'; databasen eksisterer"
        nla "Kan database '%-.192s' niet aanmaken; database bestaat reeds"
        eng "Can't create database '%-.192s'; database exists"
        est "Ei suuda luua andmebaasi '%-.192s': andmebaas juba eksisteerib"
        fre "Ne peut créer la base '%-.192s'; elle existe déjà"
        ger "Kann Datenbank '%-.192s' nicht erzeugen. Datenbank existiert bereits"
        greek "Αδύνατη η δημιουργία της βάσης δεδομένων '%-.192s'; Η βάση δεδομένων υπάρχει ήδη"
        hun "Az '%-.192s' adatbazis nem hozhato letre Az adatbazis mar letezik"
        ita "Impossibile creare il database '%-.192s'; il database esiste"
        jpn "データベース '%-.192s' を作成できません。データベースはすでに存在します。"
        kor "데이타베이스 '%-.192s'를 만들지 못했습니다.. 데이타베이스가 존재함"
        nor "Kan ikke opprette databasen '%-.192s'; databasen eksisterer"
        norwegian-ny "Kan ikkje opprette databasen '%-.192s'; databasen eksisterer"
        pol "Nie można stworzyć bazy danych '%-.192s'; baza danych już istnieje"
        por "Não pode criar o banco de dados '%-.192s'; este banco de dados já existe"
        rum "Nu pot sa creez baza de date '%-.192s'; baza de date exista deja"
        rus "Невозможно создать базу данных '%-.192s'. База данных уже существует"
        serbian "Ne mogu da kreiram bazu '%-.192s'; baza već postoji."
        slo "Nemôžem vytvoriť databázu '%-.192s'; databáza existuje"
        spa "No puedo crear base de datos '%-.192s'; la base de datos ya existe"
        swe "Databasen '%-.192s' existerar redan"
        ukr "Не можу створити базу данних '%-.192s'. База данних існує"
ER_DB_DROP_EXISTS
        cze "Nemohu zrušit databázi '%-.192s', databáze neexistuje"
        dan "Kan ikke slette (droppe) '%-.192s'; databasen eksisterer ikke"
        nla "Kan database '%-.192s' niet verwijderen; database bestaat niet"
        eng "Can't drop database '%-.192s'; database doesn't exist"
        est "Ei suuda kustutada andmebaasi '%-.192s': andmebaasi ei eksisteeri"
        fre "Ne peut effacer la base '%-.192s'; elle n'existe pas"
        ger "Kann Datenbank '%-.192s' nicht löschen; Datenbank nicht vorhanden"
        greek "Αδύνατη η διαγραφή της βάσης δεδομένων '%-.192s'. Η βάση δεδομένων δεν υπάρχει"
        hun "A(z) '%-.192s' adatbazis nem szuntetheto meg. Az adatbazis nem letezik"
        ita "Impossibile cancellare '%-.192s'; il database non esiste"
        jpn "データベース '%-.192s' を削除できません。データベースは存在しません。"
        kor "데이타베이스 '%-.192s'를 제거하지 못했습니다. 데이타베이스가 존재하지 않음 "
        nor "Kan ikke fjerne (drop) '%-.192s'; databasen eksisterer ikke"
        norwegian-ny "Kan ikkje fjerne (drop) '%-.192s'; databasen eksisterer ikkje"
        pol "Nie można usun?ć bazy danych '%-.192s'; baza danych nie istnieje"
        por "Não pode eliminar o banco de dados '%-.192s'; este banco de dados não existe"
        rum "Nu pot sa drop baza de date '%-.192s'; baza da date este inexistenta"
        rus "Невозможно удалить базу данных '%-.192s'. Такой базы данных нет"
        serbian "Ne mogu da izbrišem bazu '%-.192s'; baza ne postoji."
        slo "Nemôžem zmazať databázu '%-.192s'; databáza neexistuje"
        spa "No puedo eliminar base de datos '%-.192s'; la base de datos no existe"
        swe "Kan inte radera databasen '%-.192s'; databasen finns inte"
        ukr "Не можу видалити базу данних '%-.192s'. База данних не існує"
OBSOLETE_ER_DB_DROP_DELETE
        cze "Chyba při rušení databáze (nemohu vymazat '%-.192s', chyba %d - %s)"
        dan "Fejl ved sletning (drop) af databasen (kan ikke slette '%-.192s', Fejlkode %d - %s)"
        nla "Fout bij verwijderen database (kan '%-.192s' niet verwijderen, Errcode: %d - %s)"
        eng "Error dropping database (can't delete '%-.192s', errno: %d - %s)"
        est "Viga andmebaasi kustutamisel (ei suuda kustutada faili '%-.192s', veakood: %d - %s)"
        fre "Ne peut effacer la base '%-.192s' (erreur %d - %s)"
        ger "Fehler beim Löschen der Datenbank ('%-.192s' kann nicht gelöscht werden, Fehler: %d - %s)"
        greek "Παρουσιάστηκε πρόβλημα κατά τη διαγραφή της βάσης δεδομένων (αδύνατη η διαγραφή '%-.192s', κωδικός λάθους: %d - %s)"
        hun "Adatbazis megszuntetesi hiba ('%-.192s' nem torolheto, hibakod: %d - %s)"
        ita "Errore durante la cancellazione del database (impossibile cancellare '%-.192s', errno: %d - %s)"
        jpn "データベース削除エラー ('%-.192s' を削除できません。エラー番号: %d - %s)"
        kor "데이타베이스 제거 에러('%-.192s'를 삭제할 수 없읍니다, 에러번호: %d - %s)"
        nor "Feil ved fjerning (drop) av databasen (kan ikke slette '%-.192s', feil %d - %s)"
        norwegian-ny "Feil ved fjerning (drop) av databasen (kan ikkje slette '%-.192s', feil %d - %s)"
        pol "Bł?d podczas usuwania bazy danych (nie można usun?ć '%-.192s', bł?d %d - %s)"
        por "Erro ao eliminar banco de dados (não pode eliminar '%-.192s' - erro no. %d - %s)"
        rum "Eroare dropuind baza de date (nu pot sa sterg '%-.192s', Eroare: %d - %s)"
        rus "Ошибка при удалении базы данных (невозможно удалить '%-.192s', ошибка: %d - %s)"
        serbian "Ne mogu da izbrišem bazu (ne mogu da izbrišem '%-.192s', errno: %d - %s)"
        slo "Chyba pri mazaní databázy (nemôžem zmazať '%-.192s', chybový kód: %d - %s)"
        spa "Error eliminando la base de datos(no puedo borrar '%-.192s', error %d - %s)"
        swe "Fel vid radering av databasen (Kan inte radera '%-.192s'. Felkod: %d - %s)"
        ukr "Не можу видалити базу данних (Не можу видалити '%-.192s', помилка: %d - %s)"
ER_DB_DROP_RMDIR
        cze "Chyba při rušení databáze (nemohu vymazat adresář '%-.192s', chyba %d - %s)"
        dan "Fejl ved sletting af database (kan ikke slette folderen '%-.192s', Fejlkode %d - %s)"
        nla "Fout bij verwijderen database (kan rmdir '%-.192s' niet uitvoeren, Errcode: %d - %s)"
        eng "Error dropping database (can't rmdir '%-.192s', errno: %d - %s)"
        est "Viga andmebaasi kustutamisel (ei suuda kustutada kataloogi '%-.192s', veakood: %d - %s)"
        fre "Erreur en effaçant la base (rmdir '%-.192s', erreur %d - %s)"
        ger "Fehler beim Löschen der Datenbank (Verzeichnis '%-.192s' kann nicht gelöscht werden, Fehler: %d - %s)"
        greek "Παρουσιάστηκε πρόβλημα κατά τη διαγραφή της βάσης δεδομένων (αδύνατη η διαγραφή του φακέλλου '%-.192s', κωδικός λάθους: %d - %s)"
        hun "Adatbazis megszuntetesi hiba ('%-.192s' nem szuntetheto meg, hibakod: %d - %s)"
        ita "Errore durante la cancellazione del database (impossibile rmdir '%-.192s', errno: %d - %s)"
        jpn "データベース削除エラー (ディレクトリ '%-.192s' を削除できません。エラー番号: %d - %s)"
        kor "데이타베이스 제거 에러(rmdir '%-.192s'를 할 수 없읍니다, 에러번호: %d - %s)"
        nor "Feil ved sletting av database (kan ikke slette katalogen '%-.192s', feil %d - %s)"
        norwegian-ny "Feil ved sletting av database (kan ikkje slette katalogen '%-.192s', feil %d - %s)"
        pol "Bł?d podczas usuwania bazy danych (nie można wykonać rmdir '%-.192s', bł?d %d - %s)"
        por "Erro ao eliminar banco de dados (não pode remover diretório '%-.192s' - erro no. %d - %s)"
        rum "Eroare dropuind baza de date (nu pot sa rmdir '%-.192s', Eroare: %d - %s)"
        rus "Невозможно удалить базу данных (невозможно удалить каталог '%-.192s', ошибка: %d - %s)"
        serbian "Ne mogu da izbrišem bazu (ne mogu da izbrišem direktorijum '%-.192s', errno: %d - %s)"
        slo "Chyba pri mazaní databázy (nemôžem vymazať adresár '%-.192s', chybový kód: %d - %s)"
        spa "Error eliminando la base de datos (No puedo borrar directorio '%-.192s', error %d - %s)"
        swe "Fel vid radering av databasen (Kan inte radera biblioteket '%-.192s'. Felkod: %d - %s)"
        ukr "Не можу видалити базу данних (Не можу видалити теку '%-.192s', помилка: %d - %s)"
OBSOLETE_ER_CANT_DELETE_FILE
        cze "Chyba při výmazu '%-.192s' (chybový kód: %d - %s)"
        dan "Fejl ved sletning af '%-.192s' (Fejlkode: %d - %s)"
        nla "Fout bij het verwijderen van '%-.192s' (Errcode: %d - %s)"
        eng "Error on delete of '%-.192s' (errno: %d - %s)"
        est "Viga '%-.192s' kustutamisel (veakood: %d - %s)"
        fre "Erreur en effaçant '%-.192s' (Errcode: %d - %s)"
        ger "Fehler beim Löschen von '%-.192s' (Fehler: %d - %s)"
        greek "Παρουσιάστηκε πρόβλημα κατά τη διαγραφή '%-.192s' (κωδικός λάθους: %d - %s)"
        hun "Torlesi hiba: '%-.192s' (hibakod: %d - %s)"
        ita "Errore durante la cancellazione di '%-.192s' (errno: %d - %s)"
        jpn "ファイル '%-.192s' の削除エラー (エラー番号: %d - %s)"
        kor "'%-.192s' 삭제 중 에러 (에러번호: %d - %s)"
        nor "Feil ved sletting av '%-.192s' (Feilkode: %d - %s)"
        norwegian-ny "Feil ved sletting av '%-.192s' (Feilkode: %d - %s)"
        pol "Bł?d podczas usuwania '%-.192s' (Kod błędu: %d - %s)"
        por "Erro na remoção de '%-.192s' (erro no. %d - %s)"
        rum "Eroare incercind sa delete '%-.192s' (Eroare: %d - %s)"
        rus "Ошибка при удалении '%-.192s' (ошибка: %d - %s)"
        serbian "Greška pri brisanju '%-.192s' (errno: %d - %s)"
        slo "Chyba pri mazaní '%-.192s' (chybový kód: %d - %s)"
        spa "Error en el borrado de '%-.192s' (Error: %d - %s)"
        swe "Kan inte radera filen '%-.192s' (Felkod: %d - %s)"
        ukr "Не можу видалити '%-.192s' (помилка: %d - %s)"
ER_CANT_FIND_SYSTEM_REC
        cze "Nemohu číst záznam v systémové tabulce"
        dan "Kan ikke læse posten i systemfolderen"
        nla "Kan record niet lezen in de systeem tabel"
        eng "Can't read record in system table"
        est "Ei suuda lugeda kirjet süsteemsest tabelist"
        fre "Ne peut lire un enregistrement de la table 'system'"
        ger "Datensatz in der Systemtabelle nicht lesbar"
        greek "Αδύνατη η ανάγνωση εγγραφής από πίνακα του συστήματος"
        hun "Nem olvashato rekord a rendszertablaban"
        ita "Impossibile leggere il record dalla tabella di sistema"
        jpn "システム表のレコードを読み込めません。"
        kor "system 테이블에서 레코드를 읽을 수 없습니다."
        nor "Kan ikke lese posten i systemkatalogen"
        norwegian-ny "Kan ikkje lese posten i systemkatalogen"
        pol "Nie można odczytać rekordu z tabeli systemowej"
        por "Não pode ler um registro numa tabela do sistema"
        rum "Nu pot sa citesc cimpurile in tabla de system (system table)"
        rus "Невозможно прочитать запись в системной таблице"
        serbian "Ne mogu da pročitam slog iz sistemske tabele"
        slo "Nemôžem čítať záznam v systémovej tabuľke"
        spa "No puedo leer el registro en la tabla del sistema"
        swe "Hittar inte posten i systemregistret"
        ukr "Не можу зчитати запис з системної таблиці"
ER_CANT_GET_STAT
        cze "Nemohu získat stav '%-.200s' (chybový kód: %d - %s)"
        dan "Kan ikke læse status af '%-.200s' (Fejlkode: %d - %s)"
        nla "Kan de status niet krijgen van '%-.200s' (Errcode: %d - %s)"
        eng "Can't get status of '%-.200s' (errno: %d - %s)"
        est "Ei suuda lugeda '%-.200s' olekut (veakood: %d - %s)"
        fre "Ne peut obtenir le status de '%-.200s' (Errcode: %d - %s)"
        ger "Kann Status von '%-.200s' nicht ermitteln (Fehler: %d - %s)"
        greek "Αδύνατη η λήψη πληροφοριών για την κατάσταση του '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "A(z) '%-.200s' statusza nem allapithato meg (hibakod: %d - %s)"
        ita "Impossibile leggere lo stato di '%-.200s' (errno: %d - %s)"
        jpn "'%-.200s' の状態を取得できません。(エラー番号: %d - %s)"
        kor "'%-.200s'의 상태를 얻지 못했습니다. (에러번호: %d - %s)"
        nor "Kan ikke lese statusen til '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje lese statusen til '%-.200s' (Feilkode: %d - %s)"
        pol "Nie można otrzymać statusu '%-.200s' (Kod błędu: %d - %s)"
        por "Não pode obter o status de '%-.200s' (erro no. %d - %s)"
        rum "Nu pot sa obtin statusul lui '%-.200s' (Eroare: %d - %s)"
        rus "Невозможно получить статусную информацию о '%-.200s' (ошибка: %d - %s)"
        serbian "Ne mogu da dobijem stanje file-a '%-.200s' (errno: %d - %s)"
        slo "Nemôžem zistiť stav '%-.200s' (chybový kód: %d - %s)"
        spa "No puedo obtener el estado de '%-.200s' (Error: %d - %s)"
        swe "Kan inte läsa filinformationen (stat) från '%-.200s' (Felkod: %d - %s)"
        ukr "Не можу отримати статус '%-.200s' (помилка: %d - %s)"
OBSOLETE_ER_CANT_GET_WD
        cze "Chyba při zjišťování pracovní adresář (chybový kód: %d - %s)"
        dan "Kan ikke læse aktive folder (Fejlkode: %d - %s)"
        nla "Kan de werkdirectory niet krijgen (Errcode: %d - %s)"
        eng "Can't get working directory (errno: %d - %s)"
        est "Ei suuda identifitseerida jooksvat kataloogi (veakood: %d - %s)"
        fre "Ne peut obtenir le répertoire de travail (Errcode: %d - %s)"
        ger "Kann Arbeitsverzeichnis nicht ermitteln (Fehler: %d - %s)"
        greek "Ο φάκελλος εργασίας δεν βρέθηκε (κωδικός λάθους: %d - %s)"
        hun "A munkakonyvtar nem allapithato meg (hibakod: %d - %s)"
        ita "Impossibile leggere la directory di lavoro (errno: %d - %s)"
        jpn "作業ディレクトリを取得できません。(エラー番号: %d - %s)"
        kor "수행 디렉토리를 찾지 못했습니다. (에러번호: %d - %s)"
        nor "Kan ikke lese aktiv katalog(Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje lese aktiv katalog(Feilkode: %d - %s)"
        pol "Nie można rozpoznać aktualnego katalogu (Kod błędu: %d - %s)"
        por "Não pode obter o diretório corrente (erro no. %d - %s)"
        rum "Nu pot sa obtin directorul current (working directory) (Eroare: %d - %s)"
        rus "Невозможно определить рабочий каталог (ошибка: %d - %s)"
        serbian "Ne mogu da dobijem trenutni direktorijum (errno: %d - %s)"
        slo "Nemôžem zistiť pracovný adresár (chybový kód: %d - %s)"
        spa "No puedo acceder al directorio (Error: %d - %s)"
        swe "Kan inte inte läsa aktivt bibliotek. (Felkod: %d - %s)"
        ukr "Не можу визначити робочу теку (помилка: %d - %s)"
ER_CANT_LOCK
        cze "Nemohu uzamknout soubor (chybový kód: %d - %s)"
        dan "Kan ikke låse fil (Fejlkode: %d - %s)"
        nla "Kan de file niet blokeren (Errcode: %d - %s)"
        eng "Can't lock file (errno: %d - %s)"
        est "Ei suuda lukustada faili (veakood: %d - %s)"
        fre "Ne peut verrouiller le fichier (Errcode: %d - %s)"
        ger "Datei kann nicht gesperrt werden (Fehler: %d - %s)"
        greek "Το αρχείο δεν μπορεί να κλειδωθεί (κωδικός λάθους: %d - %s)"
        hun "A file nem zarolhato. (hibakod: %d - %s)"
        ita "Impossibile il locking il file (errno: %d - %s)"
        jpn "ファイルをロックできません。(エラー番号: %d - %s)"
        kor "화일을 잠그지(lock) 못했습니다. (에러번호: %d - %s)"
        nor "Kan ikke låse fila (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje låse fila (Feilkode: %d - %s)"
        pol "Nie można zablokować pliku (Kod błędu: %d - %s)"
        por "Não pode travar o arquivo (erro no. %d - %s)"
        rum "Nu pot sa lock fisierul (Eroare: %d - %s)"
        rus "Невозможно поставить блокировку на файле (ошибка: %d - %s)"
        serbian "Ne mogu da zaključam file (errno: %d - %s)"
        slo "Nemôžem zamknúť súbor (chybový kód: %d - %s)"
        spa "No puedo bloquear archivo: (Error: %d - %s)"
        swe "Kan inte låsa filen. (Felkod: %d - %s)"
        ukr "Не можу заблокувати файл (помилка: %d - %s)"
ER_CANT_OPEN_FILE
        cze "Nemohu otevřít soubor '%-.200s' (chybový kód: %d - %s)"
        dan "Kan ikke åbne fil: '%-.200s' (Fejlkode: %d - %s)"
        nla "Kan de file '%-.200s' niet openen (Errcode: %d - %s)"
        eng "Can't open file: '%-.200s' (errno: %d - %s)"
        est "Ei suuda avada faili '%-.200s' (veakood: %d - %s)"
        fre "Ne peut ouvrir le fichier: '%-.200s' (Errcode: %d - %s)"
        ger "Kann Datei '%-.200s' nicht öffnen (Fehler: %d - %s)"
        greek "Δεν είναι δυνατό να ανοιχτεί το αρχείο: '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "A '%-.200s' file nem nyithato meg (hibakod: %d - %s)"
        ita "Impossibile aprire il file: '%-.200s' (errno: %d - %s)"
        jpn "ファイル '%-.200s' をオープンできません。(エラー番号: %d - %s)"
        kor "화일을 열지 못했습니다.: '%-.200s' (에러번호: %d - %s)"
        nor "Kan ikke åpne fila: '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje åpne fila: '%-.200s' (Feilkode: %d - %s)"
        pol "Nie można otworzyć pliku: '%-.200s' (Kod błędu: %d - %s)"
        por "Não pode abrir o arquivo '%-.200s' (erro no. %d - %s)"
        rum "Nu pot sa deschid fisierul: '%-.200s' (Eroare: %d - %s)"
        rus "Невозможно открыть файл: '%-.200s' (ошибка: %d - %s)"
        serbian "Ne mogu da otvorim file: '%-.200s' (errno: %d - %s)"
        slo "Nemôžem otvoriť súbor: '%-.200s' (chybový kód: %d - %s)"
        spa "No puedo abrir archivo: '%-.200s' (Error: %d - %s)"
        swe "Kan inte använda '%-.200s' (Felkod: %d - %s)"
        ukr "Не можу відкрити файл: '%-.200s' (помилка: %d - %s)"
ER_FILE_NOT_FOUND
        cze "Nemohu najít soubor '%-.200s' (chybový kód: %d - %s)"
        dan "Kan ikke finde fila: '%-.200s' (Fejlkode: %d - %s)"
        nla "Kan de file: '%-.200s' niet vinden (Errcode: %d - %s)"
        eng "Can't find file: '%-.200s' (errno: %d - %s)"
        est "Ei suuda leida faili '%-.200s' (veakood: %d - %s)"
        fre "Ne peut trouver le fichier: '%-.200s' (Errcode: %d - %s)"
        ger "Kann Datei '%-.200s' nicht finden (Fehler: %d - %s)"
        greek "Δεν βρέθηκε το αρχείο: '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "A(z) '%-.200s' file nem talalhato (hibakod: %d - %s)"
        ita "Impossibile trovare il file: '%-.200s' (errno: %d - %s)"
        jpn "ファイル '%-.200s' が見つかりません。(エラー番号: %d - %s)"
        kor "화일을 찾지 못했습니다.: '%-.200s' (에러번호: %d - %s)"
        nor "Kan ikke finne fila: '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje finne fila: '%-.200s' (Feilkode: %d - %s)"
        pol "Nie można znaleĽć pliku: '%-.200s' (Kod błędu: %d - %s)"
        por "Não pode encontrar o arquivo '%-.200s' (erro no. %d - %s)"
        rum "Nu pot sa gasesc fisierul: '%-.200s' (Eroare: %d - %s)"
        rus "Невозможно найти файл: '%-.200s' (ошибка: %d - %s)"
        serbian "Ne mogu da pronađem file: '%-.200s' (errno: %d - %s)"
        slo "Nemôžem nájsť súbor: '%-.200s' (chybový kód: %d - %s)"
        spa "No puedo encontrar archivo: '%-.200s' (Error: %d - %s)"
        swe "Hittar inte filen '%-.200s' (Felkod: %d - %s)"
        ukr "Не можу знайти файл: '%-.200s' (помилка: %d - %s)"
ER_CANT_READ_DIR
        cze "Nemohu číst adresář '%-.192s' (chybový kód: %d - %s)"
        dan "Kan ikke læse folder '%-.192s' (Fejlkode: %d - %s)"
        nla "Kan de directory niet lezen van '%-.192s' (Errcode: %d - %s)"
        eng "Can't read dir of '%-.192s' (errno: %d - %s)"
        est "Ei suuda lugeda kataloogi '%-.192s' (veakood: %d - %s)"
        fre "Ne peut lire le répertoire de '%-.192s' (Errcode: %d - %s)"
        ger "Verzeichnis von '%-.192s' nicht lesbar (Fehler: %d - %s)"
        greek "Δεν είναι δυνατό να διαβαστεί ο φάκελλος του '%-.192s' (κωδικός λάθους: %d - %s)"
        hun "A(z) '%-.192s' konyvtar nem olvashato. (hibakod: %d - %s)"
        ita "Impossibile leggere la directory di '%-.192s' (errno: %d - %s)"
        jpn "ディレクトリ '%-.192s' を読み込めません。(エラー番号: %d - %s)"
        kor "'%-.192s'디렉토리를 읽지 못했습니다. (에러번호: %d - %s)"
        nor "Kan ikke lese katalogen '%-.192s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje lese katalogen '%-.192s' (Feilkode: %d - %s)"
        pol "Nie można odczytać katalogu '%-.192s' (Kod błędu: %d - %s)"
        por "Não pode ler o diretório de '%-.192s' (erro no. %d - %s)"
        rum "Nu pot sa citesc directorul '%-.192s' (Eroare: %d - %s)"
        rus "Невозможно прочитать каталог '%-.192s' (ошибка: %d - %s)"
        serbian "Ne mogu da pročitam direktorijum '%-.192s' (errno: %d - %s)"
        slo "Nemôžem čítať adresár '%-.192s' (chybový kód: %d - %s)"
        spa "No puedo leer el directorio de '%-.192s' (Error: %d - %s)"
        swe "Kan inte läsa från bibliotek '%-.192s' (Felkod: %d - %s)"
        ukr "Не можу прочитати теку '%-.192s' (помилка: %d - %s)"
OBSOLETE_ER_CANT_SET_WD
        cze "Nemohu změnit adresář na '%-.192s' (chybový kód: %d - %s)"
        dan "Kan ikke skifte folder til '%-.192s' (Fejlkode: %d - %s)"
        nla "Kan de directory niet veranderen naar '%-.192s' (Errcode: %d - %s)"
        eng "Can't change dir to '%-.192s' (errno: %d - %s)"
        est "Ei suuda siseneda kataloogi '%-.192s' (veakood: %d - %s)"
        fre "Ne peut changer le répertoire pour '%-.192s' (Errcode: %d - %s)"
        ger "Kann nicht in das Verzeichnis '%-.192s' wechseln (Fehler: %d - %s)"
        greek "Αδύνατη η αλλαγή του τρέχοντος καταλόγου σε '%-.192s' (κωδικός λάθους: %d - %s)"
        hun "Konyvtarvaltas nem lehetseges a(z) '%-.192s'-ba. (hibakod: %d - %s)"
        ita "Impossibile cambiare la directory in '%-.192s' (errno: %d - %s)"
        jpn "ディレクトリ '%-.192s' に移動できません。(エラー番号: %d - %s)"
        kor "'%-.192s'디렉토리로 이동할 수 없었습니다. (에러번호: %d - %s)"
        nor "Kan ikke skifte katalog til '%-.192s' (Feilkode: %d - %s)"
        norwegian-ny "Kan ikkje skifte katalog til '%-.192s' (Feilkode: %d - %s)"
        pol "Nie można zmienić katalogu na '%-.192s' (Kod błędu: %d - %s)"
        por "Não pode mudar para o diretório '%-.192s' (erro no. %d - %s)"
        rum "Nu pot sa schimb directorul '%-.192s' (Eroare: %d - %s)"
        rus "Невозможно перейти в каталог '%-.192s' (ошибка: %d - %s)"
        serbian "Ne mogu da promenim direktorijum na '%-.192s' (errno: %d - %s)"
        slo "Nemôžem vojsť do adresára '%-.192s' (chybový kód: %d - %s)"
        spa "No puedo cambiar al directorio de '%-.192s' (Error: %d - %s)"
        swe "Kan inte byta till '%-.192s' (Felkod: %d - %s)"
        ukr "Не можу перейти у теку '%-.192s' (помилка: %d - %s)"
ER_CHECKREAD
        cze "Záznam byl změněn od posledního čtení v tabulce '%-.192s'"
        dan "Posten er ændret siden sidste læsning '%-.192s'"
        nla "Record is veranderd sinds de laatste lees activiteit in de tabel '%-.192s'"
        eng "Record has changed since last read in table '%-.192s'"
        est "Kirje tabelis '%-.192s' on muutunud viimasest lugemisest saadik"
        fre "Enregistrement modifié depuis sa dernière lecture dans la table '%-.192s'"
        ger "Datensatz hat sich seit dem letzten Zugriff auf Tabelle '%-.192s' geändert"
        greek "Η εγγραφή έχει αλλάξει από την τελευταία φορά που ανασύρθηκε από τον πίνακα '%-.192s'"
        hun "A(z) '%-.192s' tablaban talalhato rekord megvaltozott az utolso olvasas ota"
        ita "Il record e` cambiato dall'ultima lettura della tabella '%-.192s'"
        jpn "表 '%-.192s' の最後の読み込み時点から、レコードが変化しました。"
        kor "테이블 '%-.192s'에서 마지막으로 읽은 후 Record가 변경되었습니다."
        nor "Posten har blitt endret siden den ble lest '%-.192s'"
        norwegian-ny "Posten har vorte endra sidan den sist vart lesen '%-.192s'"
        pol "Rekord został zmieniony od ostaniego odczytania z tabeli '%-.192s'"
        por "Registro alterado desde a última leitura da tabela '%-.192s'"
        rum "Cimpul a fost schimbat de la ultima citire a tabelei '%-.192s'"
        rus "Запись изменилась с момента последней выборки в таблице '%-.192s'"
        serbian "Slog je promenjen od zadnjeg čitanja tabele '%-.192s'"
        slo "Záznam bol zmenený od posledného čítania v tabuľke '%-.192s'"
        spa "El registro ha cambiado desde la ultima lectura de la tabla '%-.192s'"
        swe "Posten har förändrats sedan den lästes i register '%-.192s'"
        ukr "Запис було змінено з часу останнього читання з таблиці '%-.192s'"
OBSOLETE_ER_DISK_FULL
        cze "Disk je plný (%s), čekám na uvolnění nějakého místa ... (chybový kód: %d - %s)"
        dan "Ikke mere diskplads (%s). Venter på at få frigjort plads... (Fejlkode: %d - %s)"
        nla "Schijf vol (%s). Aan het wachten totdat er ruimte vrij wordt gemaakt... (Errcode: %d - %s)"
        eng "Disk full (%s); waiting for someone to free some space... (errno: %d - %s)"
        est "Ketas täis (%s). Ootame kuni tekib vaba ruumi... (veakood: %d - %s)"
        fre "Disque plein (%s). J'attend que quelqu'un libère de l'espace... (Errcode: %d - %s)"
        ger "Festplatte voll (%s). Warte, bis jemand Platz schafft ... (Fehler: %d - %s)"
        greek "Δεν υπάρχει χώρος στο δίσκο (%s). Παρακαλώ, περιμένετε να ελευθερωθεί χώρος... (κωδικός λάθους: %d - %s)"
        hun "A lemez megtelt (%s). (hibakod: %d - %s)"
        ita "Disco pieno (%s). In attesa che qualcuno liberi un po' di spazio... (errno: %d - %s)"
        jpn "ディスク領域不足です(%s)。(エラー番号: %d - %s)"
        kor "Disk full (%s). 다른 사람이 지울때까지 기다립니다... (에러번호: %d - %s)"
        nor "Ikke mer diskplass (%s). Venter på å få frigjort plass... (Feilkode: %d - %s)"
        norwegian-ny "Ikkje meir diskplass (%s). Ventar på å få frigjort plass... (Feilkode: %d - %s)"
        pol "Dysk pełny (%s). Oczekiwanie na zwolnienie miejsca... (Kod błędu: %d - %s)"
        por "Disco cheio (%s). Aguardando alguém liberar algum espaço... (erro no. %d - %s)"
        rum "Hard-disk-ul este plin (%s). Astept sa se elibereze ceva spatiu... (Eroare: %d - %s)"
        rus "Диск заполнен. (%s). Ожидаем, пока кто-то не уберет после себя мусор... (ошибка: %d - %s)"
        serbian "Disk je pun (%s). Čekam nekoga da dođe i oslobodi nešto mesta... (errno: %d - %s)"
        slo "Disk je plný (%s), čakám na uvoľnenie miesta... (chybový kód: %d - %s)"
        spa "Disco lleno (%s). Esperando para que se libere algo de espacio... (Error: %d - %s)"
        swe "Disken är full (%s). Väntar tills det finns ledigt utrymme... (Felkod: %d - %s)"
        ukr "Диск заповнений (%s). Вичикую, доки звільниться трохи місця... (помилка: %d - %s)"
ER_DUP_KEY 23000
        cze "Nemohu zapsat, zdvojený klíč v tabulce '%-.192s'"
        dan "Kan ikke skrive, flere ens nøgler i tabellen '%-.192s'"
        nla "Kan niet schrijven, dubbele zoeksleutel in tabel '%-.192s'"
        eng "Can't write; duplicate key in table '%-.192s'"
        est "Ei saa kirjutada, korduv võti tabelis '%-.192s'"
        fre "Ecriture impossible, doublon dans une clé de la table '%-.192s'"
        ger "Kann nicht speichern, Grund: doppelter Schlüssel in Tabelle '%-.192s'"
        greek "Δεν είναι δυνατή η καταχώρηση, η τιμή υπάρχει ήδη στον πίνακα '%-.192s'"
        hun "Irasi hiba, duplikalt kulcs a '%-.192s' tablaban."
        ita "Scrittura impossibile: chiave duplicata nella tabella '%-.192s'"
        jpn "書き込めません。表 '%-.192s' に重複するキーがあります。"
        kor "기록할 수 없읍니다., 테이블 '%-.192s'에서 중복 키"
        nor "Kan ikke skrive, flere like nøkler i tabellen '%-.192s'"
        norwegian-ny "Kan ikkje skrive, flere like nyklar i tabellen '%-.192s'"
        pol "Nie można zapisać, powtórzone klucze w tabeli '%-.192s'"
        por "Não pode gravar. Chave duplicada na tabela '%-.192s'"
        rum "Nu pot sa scriu (can't write), cheie duplicata in tabela '%-.192s'"
        rus "Невозможно произвести запись, дублирующийся ключ в таблице '%-.192s'"
        serbian "Ne mogu da pišem pošto postoji duplirani ključ u tabeli '%-.192s'"
        slo "Nemôžem zapísať, duplikát kľúča v tabuľke '%-.192s'"
        spa "No puedo escribir, clave duplicada en la tabla '%-.192s'"
        swe "Kan inte skriva, dubbel söknyckel i register '%-.192s'"
        ukr "Не можу записати, дублюючийся ключ в таблиці '%-.192s'"
OBSOLETE_ER_ERROR_ON_CLOSE
        cze "Chyba při zavírání '%-.192s' (chybový kód: %d - %s)"
        dan "Fejl ved lukning af '%-.192s' (Fejlkode: %d - %s)"
        nla "Fout bij het sluiten van '%-.192s' (Errcode: %d - %s)"
        eng "Error on close of '%-.192s' (errno: %d - %s)"
        est "Viga faili '%-.192s' sulgemisel (veakood: %d - %s)"
        fre "Erreur a la fermeture de '%-.192s' (Errcode: %d - %s)"
        ger "Fehler beim Schließen von '%-.192s' (Fehler: %d - %s)"
        greek "Παρουσιάστηκε πρόβλημα κλείνοντας το '%-.192s' (κωδικός λάθους: %d - %s)"
        hun "Hiba a(z) '%-.192s' zarasakor. (hibakod: %d - %s)"
        ita "Errore durante la chiusura di '%-.192s' (errno: %d - %s)"
        jpn "'%-.192s' のクローズ時エラー (エラー番号: %d - %s)"
        kor "'%-.192s'닫는 중 에러 (에러번호: %d - %s)"
        nor "Feil ved lukking av '%-.192s' (Feilkode: %d - %s)"
        norwegian-ny "Feil ved lukking av '%-.192s' (Feilkode: %d - %s)"
        pol "Bł?d podczas zamykania '%-.192s' (Kod błędu: %d - %s)"
        por "Erro ao fechar '%-.192s' (erro no. %d - %s)"
        rum "Eroare inchizind '%-.192s' (errno: %d - %s)"
        rus "Ошибка при закрытии '%-.192s' (ошибка: %d - %s)"
        serbian "Greška pri zatvaranju '%-.192s' (errno: %d - %s)"
        slo "Chyba pri zatváraní '%-.192s' (chybový kód: %d - %s)"
        spa "Error en el cierre de '%-.192s' (Error: %d - %s)"
        swe "Fick fel vid stängning av '%-.192s' (Felkod: %d - %s)"
        ukr "Не можу закрити '%-.192s' (помилка: %d - %s)"
ER_ERROR_ON_READ
        cze "Chyba při čtení souboru '%-.200s' (chybový kód: %d - %s)"
        dan "Fejl ved læsning af '%-.200s' (Fejlkode: %d - %s)"
        nla "Fout bij het lezen van file '%-.200s' (Errcode: %d - %s)"
        eng "Error reading file '%-.200s' (errno: %d - %s)"
        est "Viga faili '%-.200s' lugemisel (veakood: %d - %s)"
        fre "Erreur en lecture du fichier '%-.200s' (Errcode: %d - %s)"
        ger "Fehler beim Lesen der Datei '%-.200s' (Fehler: %d - %s)"
        greek "Πρόβλημα κατά την ανάγνωση του αρχείου '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "Hiba a '%-.200s'file olvasasakor. (hibakod: %d - %s)"
        ita "Errore durante la lettura del file '%-.200s' (errno: %d - %s)"
        jpn "ファイル '%-.200s' の読み込みエラー (エラー番号: %d - %s)"
        kor "'%-.200s'화일 읽기 에러 (에러번호: %d - %s)"
        nor "Feil ved lesing av '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Feil ved lesing av '%-.200s' (Feilkode: %d - %s)"
        pol "Bł?d podczas odczytu pliku '%-.200s' (Kod błędu: %d - %s)"
        por "Erro ao ler arquivo '%-.200s' (erro no. %d - %s)"
        rum "Eroare citind fisierul '%-.200s' (errno: %d - %s)"
        rus "Ошибка чтения файла '%-.200s' (ошибка: %d - %s)"
        serbian "Greška pri čitanju file-a '%-.200s' (errno: %d - %s)"
        slo "Chyba pri čítaní súboru '%-.200s' (chybový kód: %d - %s)"
        spa "Error leyendo el fichero '%-.200s' (Error: %d - %s)"
        swe "Fick fel vid läsning av '%-.200s' (Felkod %d - %s)"
        ukr "Не можу прочитати файл '%-.200s' (помилка: %d - %s)"
ER_ERROR_ON_RENAME
        cze "Chyba při přejmenování '%-.210s' na '%-.210s' (chybový kód: %d - %s)"
        dan "Fejl ved omdøbning af '%-.210s' til '%-.210s' (Fejlkode: %d - %s)"
        nla "Fout bij het hernoemen van '%-.210s' naar '%-.210s' (Errcode: %d - %s)"
        eng "Error on rename of '%-.210s' to '%-.210s' (errno: %d - %s)"
        est "Viga faili '%-.210s' ümbernimetamisel '%-.210s'-ks (veakood: %d - %s)"
        fre "Erreur en renommant '%-.210s' en '%-.210s' (Errcode: %d - %s)"
        ger "Fehler beim Umbenennen von '%-.210s' in '%-.210s' (Fehler: %d - %s)"
        greek "Πρόβλημα κατά την μετονομασία του αρχείου '%-.210s' to '%-.210s' (κωδικός λάθους: %d - %s)"
        hun "Hiba a '%-.210s' file atnevezesekor '%-.210s'. (hibakod: %d - %s)"
        ita "Errore durante la rinominazione da '%-.210s' a '%-.210s' (errno: %d - %s)"
        jpn "'%-.210s' の名前を '%-.210s' に変更できません (エラー番号: %d - %s)"
        kor "'%-.210s'를 '%-.210s'로 이름 변경중 에러 (에러번호: %d - %s)"
        nor "Feil ved omdøping av '%-.210s' til '%-.210s' (Feilkode: %d - %s)"
        norwegian-ny "Feil ved omdøyping av '%-.210s' til '%-.210s' (Feilkode: %d - %s)"
        pol "Bł?d podczas zmieniania nazwy '%-.210s' na '%-.210s' (Kod błędu: %d - %s)"
        por "Erro ao renomear '%-.210s' para '%-.210s' (erro no. %d - %s)"
        rum "Eroare incercind sa renumesc '%-.210s' in '%-.210s' (errno: %d - %s)"
        rus "Ошибка при переименовании '%-.210s' в '%-.210s' (ошибка: %d - %s)"
        serbian "Greška pri promeni imena '%-.210s' na '%-.210s' (errno: %d - %s)"
        slo "Chyba pri premenovávaní '%-.210s' na '%-.210s' (chybový kód: %d - %s)"
        spa "Error en el renombrado de '%-.210s' a '%-.210s' (Error: %d - %s)"
        swe "Kan inte byta namn från '%-.210s' till '%-.210s' (Felkod: %d - %s)"
        ukr "Не можу перейменувати '%-.210s' у '%-.210s' (помилка: %d - %s)"
ER_ERROR_ON_WRITE
        cze "Chyba při zápisu do souboru '%-.200s' (chybový kód: %d - %s)"
        dan "Fejl ved skriving av filen '%-.200s' (Fejlkode: %d - %s)"
        nla "Fout bij het wegschrijven van file '%-.200s' (Errcode: %d - %s)"
        eng "Error writing file '%-.200s' (errno: %d - %s)"
        est "Viga faili '%-.200s' kirjutamisel (veakood: %d - %s)"
        fre "Erreur d'écriture du fichier '%-.200s' (Errcode: %d - %s)"
        ger "Fehler beim Speichern der Datei '%-.200s' (Fehler: %d - %s)"
        greek "Πρόβλημα κατά την αποθήκευση του αρχείου '%-.200s' (κωδικός λάθους: %d - %s)"
        hun "Hiba a '%-.200s' file irasakor. (hibakod: %d - %s)"
        ita "Errore durante la scrittura del file '%-.200s' (errno: %d - %s)"
        jpn "ファイル '%-.200s' の書き込みエラー (エラー番号: %d - %s)"
        kor "'%-.200s'화일 기록 중 에러 (에러번호: %d - %s)"
        nor "Feil ved skriving av fila '%-.200s' (Feilkode: %d - %s)"
        norwegian-ny "Feil ved skriving av fila '%-.200s' (Feilkode: %d - %s)"
        pol "Bł?d podczas zapisywania pliku '%-.200s' (Kod błędu: %d - %s)"
        por "Erro ao gravar arquivo '%-.200s' (erro no. %d - %s)"
        rum "Eroare scriind fisierul '%-.200s' (errno: %d - %s)"
        rus "Ошибка записи в файл '%-.200s' (ошибка: %d - %s)"
        serbian "Greška pri upisu '%-.200s' (errno: %d - %s)"
        slo "Chyba pri zápise do súboru '%-.200s' (chybový kód: %d - %s)"
        spa "Error escribiendo el archivo '%-.200s' (Error: %d - %s)"
        swe "Fick fel vid skrivning till '%-.200s' (Felkod %d - %s)"
        ukr "Не можу записати файл '%-.200s' (помилка: %d - %s)"
ER_FILE_USED
        cze "'%-.192s' je zamčen proti změnám"
        dan "'%-.192s' er låst mod opdateringer"
        nla "'%-.192s' is geblokeerd tegen veranderingen"
        eng "'%-.192s' is locked against change"
        est "'%-.192s' on lukustatud muudatuste vastu"
        fre "'%-.192s' est verrouillé contre les modifications"
        ger "'%-.192s' ist für Änderungen gesperrt"
        greek "'%-.192s' δεν επιτρέπονται αλλαγές"
        hun "'%-.192s' a valtoztatas ellen zarolva"
        ita "'%-.192s' e` soggetto a lock contro i cambiamenti"
        jpn "'%-.192s' はロックされています。"
        kor "'%-.192s'가 변경할 수 없도록 잠겨있읍니다."
        nor "'%-.192s' er låst mot oppdateringer"
        norwegian-ny "'%-.192s' er låst mot oppdateringar"
        pol "'%-.192s' jest zablokowany na wypadek zmian"
        por "'%-.192s' está com travamento contra alterações"
        rum "'%-.192s' este blocat pentry schimbari (loccked against change)"
        rus "'%-.192s' заблокирован для изменений"
        serbian "'%-.192s' je zaključan za upis"
        slo "'%-.192s' je zamknutý proti zmenám"
        spa "'%-.192s' esta bloqueado contra cambios"
        swe "'%-.192s' är låst mot användning"
        ukr "'%-.192s' заблокований на внесення змін"
OBSOLETE_ER_FILSORT_ABORT
        cze "Třídění přerušeno"
        dan "Sortering afbrudt"
        nla "Sorteren afgebroken"
        eng "Sort aborted"
        est "Sorteerimine katkestatud"
        fre "Tri alphabétique abandonné"
        ger "Sortiervorgang abgebrochen"
        greek "Η διαδικασία ταξινόμισης ακυρώθηκε"
        hun "Sikertelen rendezes"
        ita "Operazione di ordinamento abbandonata"
        jpn "ソート処理を中断しました。"
        kor "소트가 중단되었습니다."
        nor "Sortering avbrutt"
        norwegian-ny "Sortering avbrote"
        pol "Sortowanie przerwane"
        por "Ordenação abortada"
        rum "Sortare intrerupta"
        rus "Сортировка прервана"
        serbian "Sortiranje je prekinuto"
        slo "Triedenie prerušené"
        spa "Ordeancion cancelada"
        swe "Sorteringen avbruten"
        ukr "Сортування перервано"
OBSOLETE_ER_FORM_NOT_FOUND
        cze "Pohled '%-.192s' pro '%-.192s' neexistuje"
        dan "View '%-.192s' eksisterer ikke for '%-.192s'"
        nla "View '%-.192s' bestaat niet voor '%-.192s'"
        eng "View '%-.192s' doesn't exist for '%-.192s'"
        est "Vaade '%-.192s' ei eksisteeri '%-.192s' jaoks"
        fre "La vue (View) '%-.192s' n'existe pas pour '%-.192s'"
        ger "View '%-.192s' existiert für '%-.192s' nicht"
        greek "Το View '%-.192s' δεν υπάρχει για '%-.192s'"
        hun "A(z) '%-.192s' nezet nem letezik a(z) '%-.192s'-hoz"
        ita "La view '%-.192s' non esiste per '%-.192s'"
        jpn "ビュー '%-.192s' は '%-.192s' に存在しません。"
        kor "뷰 '%-.192s'가 '%-.192s'에서는 존재하지 않읍니다."
        nor "View '%-.192s' eksisterer ikke for '%-.192s'"
        norwegian-ny "View '%-.192s' eksisterar ikkje for '%-.192s'"
        pol "Widok '%-.192s' nie istnieje dla '%-.192s'"
        por "Visão '%-.192s' não existe para '%-.192s'"
        rum "View '%-.192s' nu exista pentru '%-.192s'"
        rus "Представление '%-.192s' не существует для '%-.192s'"
        serbian "View '%-.192s' ne postoji za '%-.192s'"
        slo "Pohľad '%-.192s' neexistuje pre '%-.192s'"
        spa "La vista '%-.192s' no existe para '%-.192s'"
        swe "Formulär '%-.192s' finns inte i '%-.192s'"
        ukr "Вигляд '%-.192s' не існує для '%-.192s'"
ER_GET_ERRNO
        cze "Obsluha tabulky vrátila chybu %d - '%-.192s'"
        dan "Modtog fejl %d - '%-.192s' fra tabel håndteringen"
        nla "Fout %d - '%-.192s' van tabel handler"
        eng "Got error %d - '%-.192s' from storage engine"
        est "Tabeli handler tagastas vea %d - '%-.192s'"
        fre "Reçu l'erreur %d - '%-.192s' du handler de la table"
        ger "Fehler %d - '%-.192s' (Speicher-Engine)"
        greek "Ελήφθη μήνυμα λάθους %d - '%-.192s' από τον χειριστή πίνακα (table handler)"
        hun "%d - '%-.192s' hibajelzes a tablakezelotol"
        ita "Rilevato l'errore %d - '%-.192s' dal gestore delle tabelle"
        jpn "ストレージエンジンがエラー %d - '%-.192s' を返しました。"
        kor "테이블 handler에서 %d - '%-.192s' 에러가 발생 하였습니다."
        nor "Mottok feil %d - '%-.192s' fra tabell håndterer"
        norwegian-ny "Mottok feil %d - '%-.192s' fra tabell handterar"
        pol "Otrzymano bł?d %d - '%-.192s' z obsługi tabeli"
        por "Obteve erro %d - '%-.192s' no manipulador de tabelas"
        rum "Eroarea %d - '%-.192s' obtinuta din handlerul tabelei"
        rus "Получена ошибка %d - '%-.192s' от обработчика таблиц"
        serbian "Handler tabela je vratio grešku %d - '%-.192s'"
        slo "Obsluha tabuľky vrátila chybu %d - '%-.192s'"
        spa "Error %d - '%-.192s' desde el manejador de la tabla"
        swe "Fick felkod %d - '%-.192s' från databashanteraren"
        ukr "Отримано помилку %d - '%-.192s' від дескриптора таблиці"
ER_ILLEGAL_HA
        cze "Obsluha tabulky '%-.192s' nemá tento parametr"
        dan "Denne mulighed eksisterer ikke for tabeltypen '%-.192s'"
        nla "Tabel handler voor '%-.192s' heeft deze optie niet"
        eng "Table storage engine for '%-.192s' doesn't have this option"
        est "Tabeli '%-.192s' handler ei toeta antud operatsiooni"
        fre "Le handler de la table '%-.192s' n'a pas cette option"
        ger "Diese Option gibt es nicht (Speicher-Engine für '%-.192s')"
        greek "Ο χειριστής πίνακα (table handler) για '%-.192s' δεν διαθέτει αυτή την επιλογή"
        hun "A(z) '%-.192s' tablakezelonek nincs ilyen opcioja"
        ita "Il gestore delle tabelle per '%-.192s' non ha questa opzione"
        jpn "表 '%-.192s' のストレージエンジンでは提供されないオプションです。"
        kor "'%-.192s'의 테이블 handler는 이러한 옵션을 제공하지 않읍니다."
        nor "Tabell håndtereren for '%-.192s' har ikke denne muligheten"
        norwegian-ny "Tabell håndteraren for '%-.192s' har ikkje denne moglegheita"
        pol "Obsługa tabeli '%-.192s' nie posiada tej opcji"
        por "Manipulador de tabela para '%-.192s' não tem esta opção"
        rum "Handlerul tabelei pentru '%-.192s' nu are aceasta optiune"
        rus "Обработчик таблицы '%-.192s' не поддерживает эту возможность"
        serbian "Handler tabela za '%-.192s' nema ovu opciju"
        slo "Obsluha tabuľky '%-.192s' nemá tento parameter"
        spa "El manejador de la tabla de '%-.192s' no tiene esta opcion"
	swe "Tabellhanteraren for tabell '%-.192s' stödjer ej detta"
        ukr "Дескриптор таблиці '%-.192s' не має цієї властивості"
ER_KEY_NOT_FOUND
        cze "Nemohu najít záznam v '%-.192s'"
        dan "Kan ikke finde posten i '%-.192s'"
        nla "Kan record niet vinden in '%-.192s'"
        eng "Can't find record in '%-.192s'"
        est "Ei suuda leida kirjet '%-.192s'-s"
        fre "Ne peut trouver l'enregistrement dans '%-.192s'"
        ger "Kann Datensatz in '%-.192s' nicht finden"
        greek "Αδύνατη η ανεύρεση εγγραφής στο '%-.192s'"
        hun "Nem talalhato a rekord '%-.192s'-ben"
        ita "Impossibile trovare il record in '%-.192s'"
        jpn "'%-.192s' にレコードが見つかりません。"
        kor "'%-.192s'에서 레코드를 찾을 수 없읍니다."
        nor "Kan ikke finne posten i '%-.192s'"
        norwegian-ny "Kan ikkje finne posten i '%-.192s'"
        pol "Nie można znaleĽć rekordu w '%-.192s'"
        por "Não pode encontrar registro em '%-.192s'"
        rum "Nu pot sa gasesc recordul in '%-.192s'"
        rus "Невозможно найти запись в '%-.192s'"
        serbian "Ne mogu da pronađem slog u '%-.192s'"
        slo "Nemôžem nájsť záznam v '%-.192s'"
        spa "No puedo encontrar el registro en '%-.192s'"
	swe "Hittar inte posten '%-.192s'"
        ukr "Не можу записати у '%-.192s'"
ER_NOT_FORM_FILE
        cze "Nesprávná informace v souboru '%-.200s'"
        dan "Forkert indhold i: '%-.200s'"
        nla "Verkeerde info in file: '%-.200s'"
        eng "Incorrect information in file: '%-.200s'"
        est "Vigane informatsioon failis '%-.200s'"
        fre "Information erronnée dans le fichier: '%-.200s'"
        ger "Falsche Information in Datei '%-.200s'"
        greek "Λάθος πληροφορίες στο αρχείο: '%-.200s'"
        hun "Ervenytelen info a file-ban: '%-.200s'"
        ita "Informazione errata nel file: '%-.200s'"
        jpn "ファイル '%-.200s' 内の情報が不正です。"
        kor "화일의 부정확한 정보: '%-.200s'"
        nor "Feil informasjon i filen: '%-.200s'"
        norwegian-ny "Feil informasjon i fila: '%-.200s'"
        pol "Niewła?ciwa informacja w pliku: '%-.200s'"
        por "Informação incorreta no arquivo '%-.200s'"
        rum "Informatie incorecta in fisierul: '%-.200s'"
        rus "Некорректная информация в файле '%-.200s'"
        serbian "Pogrešna informacija u file-u: '%-.200s'"
        slo "Nesprávna informácia v súbore: '%-.200s'"
        spa "Informacion erronea en el archivo: '%-.200s'"
        swe "Felaktig fil: '%-.200s'"
        ukr "Хибна інформація у файлі: '%-.200s'"
ER_NOT_KEYFILE
        cze "Nesprávný klíč pro tabulku '%-.200s'; pokuste se ho opravit"
        dan "Fejl i indeksfilen til tabellen '%-.200s'; prøv at reparere den"
        nla "Verkeerde zoeksleutel file voor tabel: '%-.200s'; probeer het te repareren"
        eng "Incorrect key file for table '%-.200s'; try to repair it"
        est "Tabeli '%-.200s' võtmefail on vigane; proovi seda parandada"
        fre "Index corrompu dans la table: '%-.200s'; essayez de le réparer"
        ger "Fehlerhafte Index-Datei für Tabelle '%-.200s'; versuche zu reparieren"
        greek "Λάθος αρχείο ταξινόμισης (key file) για τον πίνακα: '%-.200s'; Παρακαλώ, διορθώστε το!"
        hun "Ervenytelen kulcsfile a tablahoz: '%-.200s'; probalja kijavitani!"
        ita "File chiave errato per la tabella : '%-.200s'; prova a riparalo"
        jpn "表 '%-.200s' の索引ファイル(key file)の内容が不正です。修復を試行してください。"
        kor "'%-.200s' 테이블의 부정확한 키 존재. 수정하시오!"
        nor "Tabellen '%-.200s' har feil i nøkkelfilen; forsøk å reparer den"
        norwegian-ny "Tabellen '%-.200s' har feil i nykkelfila; prøv å reparere den"
        pol "Niewła?ciwy plik kluczy dla tabeli: '%-.200s'; spróbuj go naprawić"
        por "Arquivo de índice incorreto para tabela '%-.200s'; tente repará-lo"
        rum "Cheia fisierului incorecta pentru tabela: '%-.200s'; incearca s-o repari"
        rus "Некорректный индексный файл для таблицы: '%-.200s'. Попробуйте восстановить его"
        serbian "Pogrešan key file za tabelu: '%-.200s'; probajte da ga ispravite"
        slo "Nesprávny kľúč pre tabuľku '%-.200s'; pokúste sa ho opraviť"
        spa "Clave de archivo erronea para la tabla: '%-.200s'; intente repararlo"
        swe "Fatalt fel vid hantering av register '%-.200s'; kör en reparation"
        ukr "Хибний файл ключей для таблиці: '%-.200s'; Спробуйте його відновити"
ER_OLD_KEYFILE
        cze "Starý klíčový soubor pro '%-.192s'; opravte ho."
        dan "Gammel indeksfil for tabellen '%-.192s'; reparer den"
        nla "Oude zoeksleutel file voor tabel '%-.192s'; repareer het!"
        eng "Old key file for table '%-.192s'; repair it!"
        est "Tabeli '%-.192s' võtmefail on aegunud; paranda see!"
        fre "Vieux fichier d'index pour la table '%-.192s'; réparez le!"
        ger "Alte Index-Datei für Tabelle '%-.192s'. Bitte reparieren"
        greek "Παλαιό αρχείο ταξινόμισης (key file) για τον πίνακα '%-.192s'; Παρακαλώ, διορθώστε το!"
        hun "Regi kulcsfile a '%-.192s'tablahoz; probalja kijavitani!"
        ita "File chiave vecchio per la tabella '%-.192s'; riparalo!"
        jpn "表 '%-.192s' の索引ファイル(key file)は古い形式です。修復してください。"
        kor "'%-.192s' 테이블의 이전버젼의 키 존재. 수정하시오!"
        nor "Gammel nøkkelfil for tabellen '%-.192s'; reparer den!"
        norwegian-ny "Gammel nykkelfil for tabellen '%-.192s'; reparer den!"
        pol "Plik kluczy dla tabeli '%-.192s' jest starego typu; napraw go!"
        por "Arquivo de índice desatualizado para tabela '%-.192s'; repare-o!"
        rum "Cheia fisierului e veche pentru tabela '%-.192s'; repar-o!"
        rus "Старый индексный файл для таблицы '%-.192s'; отремонтируйте его!"
        serbian "Zastareo key file za tabelu '%-.192s'; ispravite ga"
        slo "Starý kľúčový súbor pre '%-.192s'; opravte ho!"
        spa "Clave de archivo antigua para la tabla '%-.192s'; reparelo!"
        swe "Gammal nyckelfil '%-.192s'; reparera registret"
        ukr "Старий файл ключей для таблиці '%-.192s'; Відновіть його!"
ER_OPEN_AS_READONLY
        cze "'%-.192s' je jen pro čtení"
        dan "'%-.192s' er skrivebeskyttet"
        nla "'%-.192s' is alleen leesbaar"
        eng "Table '%-.192s' is read only"
        est "Tabel '%-.192s' on ainult lugemiseks"
        fre "'%-.192s' est en lecture seulement"
        ger "Tabelle '%-.192s' ist nur lesbar"
        greek "'%-.192s' επιτρέπεται μόνο η ανάγνωση"
        hun "'%-.192s' irasvedett"
        ita "'%-.192s' e` di sola lettura"
        jpn "表 '%-.192s' は読み込み専用です。"
        kor "테이블 '%-.192s'는 읽기전용 입니다."
        nor "'%-.192s' er skrivebeskyttet"
        norwegian-ny "'%-.192s' er skrivetryggja"
        pol "'%-.192s' jest tylko do odczytu"
        por "Tabela '%-.192s' é somente para leitura"
        rum "Tabela '%-.192s' e read-only"
        rus "Таблица '%-.192s' предназначена только для чтения"
        serbian "Tabelu '%-.192s' je dozvoljeno samo čitati"
        slo "'%-.192s' is čítať only"
        spa "'%-.192s' es de solo lectura"
        swe "'%-.192s' är skyddad mot förändring"
        ukr "Таблиця '%-.192s' тільки для читання"
ER_OUTOFMEMORY HY001 S1001
        cze "Málo paměti. Přestartujte daemona a zkuste znovu (je potřeba %d bytů)"
        dan "Ikke mere hukommelse. Genstart serveren og prøv igen (mangler %d bytes)"
        nla "Geen geheugen meer. Herstart server en probeer opnieuw (%d bytes nodig)"
        eng "Out of memory; restart server and try again (needed %d bytes)"
        est "Mälu  sai otsa. Proovi MySQL uuesti käivitada (puudu jäi %d baiti)"
        fre "Manque de mémoire. Redémarrez le démon et ré-essayez (%d octets nécessaires)"
        ger "Kein Speicher vorhanden (%d Bytes benötigt). Bitte Server neu starten"
        greek "Δεν υπάρχει διαθέσιμη μνήμη. Προσπαθήστε πάλι, επανεκινώντας τη διαδικασία (demon) (χρειάζονται %d bytes)"
        hun "Nincs eleg memoria. Inditsa ujra a demont, es probalja ismet. (%d byte szukseges.)"
        ita "Memoria esaurita. Fai ripartire il demone e riprova (richiesti %d bytes)"
        jpn "メモリが不足しています。サーバーを再起動してみてください。(%d バイトの割り当てに失敗)"
        kor "Out of memory. 데몬을 재 실행 후 다시 시작하시오 (needed %d bytes)"
        nor "Ikke mer minne. Star på nytt tjenesten og prøv igjen (trengte %d byter)"
        norwegian-ny "Ikkje meir minne. Start på nytt tenesten og prøv igjen (trengte %d bytar)"
        pol "Zbyt mało pamięci. Uruchom ponownie demona i spróbuj ponownie (potrzeba %d bajtów)"
        por "Sem memória. Reinicie o programa e tente novamente (necessita de %d bytes)"
        rum "Out of memory. Porneste daemon-ul din nou si incearca inca o data (e nevoie de %d bytes)"
        rus "Недостаточно памяти. Перезапустите сервер и попробуйте еще раз (нужно %d байт)"
        serbian "Nema memorije. Restartujte MySQL server i probajte ponovo (potrebno je %d byte-ova)"
        slo "Málo pamäti. Reštartujte daemona a skúste znova (je potrebných %d bytov)"
        spa "Memoria insuficiente. Reinicie el demonio e intentelo otra vez (necesita %d bytes)"
        swe "Oväntat slut på minnet, starta om programmet och försök på nytt (Behövde %d bytes)"
        ukr "Брак пам'яті. Рестартуйте сервер та спробуйте знову (потрібно %d байтів)"
ER_OUT_OF_SORTMEMORY HY001 S1001
        cze "Málo paměti pro třídění. Zvyšte velikost třídícího bufferu"
        dan "Ikke mere sorteringshukommelse. Øg sorteringshukommelse (sort buffer size) for serveren"
        nla "Geen geheugen om te sorteren. Verhoog de server sort buffer size"
        eng "Out of sort memory, consider increasing server sort buffer size"
        est "Mälu sai sorteerimisel otsa. Suurenda MySQL-i sorteerimispuhvrit"
        fre "Manque de mémoire pour le tri. Augmentez-la."
        ger "Kein Speicher zum Sortieren vorhanden. sort_buffer_size sollte im Server erhöht werden"
        greek "Δεν υπάρχει διαθέσιμη μνήμη για ταξινόμιση. Αυξήστε το sort buffer size για τη διαδικασία (demon)"
        hun "Nincs eleg memoria a rendezeshez. Novelje a rendezo demon puffermeretet"
        ita "Memoria per gli ordinamenti esaurita. Incrementare il 'sort_buffer' al demone"
        jpn "ソートメモリが不足しています。ソートバッファサイズ(sort buffer size)の増加を検討してください。"
        kor "Out of sort memory. daemon sort buffer의 크기를 증가시키세요"
        nor "Ikke mer sorteringsminne. Vurder å øke sorteringsminnet (sort buffer size) for tjenesten"
        norwegian-ny "Ikkje meir sorteringsminne. Vurder å auke sorteringsminnet (sorteringsbuffer storleik) for tenesten"
        pol "Zbyt mało pamięci dla sortowania. Zwiększ wielko?ć bufora demona dla sortowania"
        por "Não há memória suficiente para ordenação. Considere aumentar o tamanho do retentor (buffer) de ordenação."
        rum "Out of memory pentru sortare. Largeste marimea buffer-ului pentru sortare in daemon (sort buffer size)"
        rus "Недостаточно памяти для сортировки. Увеличьте размер буфера сортировки на сервере"
        serbian "Nema memorije za sortiranje. Povećajte veličinu sort buffer-a MySQL server-u"
        slo "Málo pamäti pre triedenie, zvýšte veľkosť triediaceho bufferu"
        spa "Memoria de ordenacion insuficiente. Incremente el tamano del buffer de ordenacion"
        swe "Sorteringsbufferten räcker inte till. Kontrollera startparametrarna"
        ukr "Брак пам'яті для сортування. Треба збільшити розмір буфера сортування у сервера"
OBSOLETE_ER_UNEXPECTED_EOF
        cze "Neočekávaný konec souboru při čtení '%-.192s' (chybový kód: %d - %s)"
        dan "Uventet afslutning på fil (eof) ved læsning af filen '%-.192s' (Fejlkode: %d - %s)"
        nla "Onverwachte eof gevonden tijdens het lezen van file '%-.192s' (Errcode: %d - %s)"
        eng "Unexpected EOF found when reading file '%-.192s' (errno: %d - %s)"
        est "Ootamatu faililõpumärgend faili '%-.192s' lugemisel (veakood: %d - %s)"
        fre "Fin de fichier inattendue en lisant '%-.192s' (Errcode: %d - %s)"
        ger "Unerwartetes Ende beim Lesen der Datei '%-.192s' (Fehler: %d - %s)"
        greek "Κατά τη διάρκεια της ανάγνωσης, βρέθηκε απροσδόκητα το τέλος του αρχείου '%-.192s' (κωδικός λάθους: %d - %s)"
        hun "Varatlan filevege-jel a '%-.192s'olvasasakor. (hibakod: %d - %s)"
        ita "Fine del file inaspettata durante la lettura del file '%-.192s' (errno: %d - %s)"
        jpn "ファイル '%-.192s' を読み込み中に予期せずファイルの終端に達しました。(エラー番号: %d - %s)"
        kor "'%-.192s' 화일을 읽는 도중 잘못된 eof을 발견 (에러번호: %d - %s)"
        nor "Uventet slutt på fil (eof) ved lesing av filen '%-.192s' (Feilkode: %d - %s)"
        norwegian-ny "Uventa slutt på fil (eof) ved lesing av fila '%-.192s' (Feilkode: %d - %s)"
        pol "Nieoczekiwany 'eof' napotkany podczas czytania z pliku '%-.192s' (Kod błędu: %d - %s)"
        por "Encontrado fim de arquivo inesperado ao ler arquivo '%-.192s' (erro no. %d - %s)"
        rum "Sfirsit de fisier neasteptat in citirea fisierului '%-.192s' (errno: %d - %s)"
        rus "Неожиданный конец файла '%-.192s' (ошибка: %d - %s)"
        serbian "Neočekivani kraj pri čitanju file-a '%-.192s' (errno: %d - %s)"
        slo "Neočakávaný koniec súboru pri čítaní '%-.192s' (chybový kód: %d - %s)"
        spa "Inesperado fin de ficheroU mientras leiamos el archivo '%-.192s' (Error: %d - %s)"
        swe "Oväntat filslut vid läsning från '%-.192s' (Felkod: %d - %s)"
        ukr "Хибний кінець файлу '%-.192s' (помилка: %d - %s)"
ER_CON_COUNT_ERROR 08004
        cze "Příliš mnoho spojení"
        dan "For mange forbindelser (connections)"
        nla "Te veel verbindingen"
        eng "Too many connections"
        est "Liiga palju samaaegseid ühendusi"
        fre "Trop de connexions"
        ger "Zu viele Verbindungen"
        greek "Υπάρχουν πολλές συνδέσεις..."
        hun "Tul sok kapcsolat"
        ita "Troppe connessioni"
        jpn "接続が多すぎます。"
        kor "너무 많은 연결... max_connection을 증가 시키시오..."
        nor "For mange tilkoblinger (connections)"
        norwegian-ny "For mange tilkoplingar (connections)"
        pol "Zbyt wiele poł?czeń"
        por "Excesso de conexões"
        rum "Prea multe conectiuni"
        rus "Слишком много соединений"
        serbian "Previše konekcija"
        slo "Príliš mnoho spojení"
        spa "Demasiadas conexiones"
        swe "För många anslutningar"
        ukr "Забагато з'єднань"
ER_OUT_OF_RESOURCES
        cze "Málo prostoru/paměti pro thread"
        dan "Udgået for tråde/hukommelse"
        nla "Geen thread geheugen meer; controleer of mysqld of andere processen al het beschikbare geheugen gebruikt. Zo niet, dan moet u wellicht 'ulimit' gebruiken om mysqld toe te laten meer geheugen te benutten, of u kunt extra swap ruimte toevoegen"
        eng "Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space"
        est "Mälu sai otsa. Võimalik, et aitab swap-i lisamine või käsu 'ulimit' abil MySQL-le rohkema mälu kasutamise lubamine"
        fre "Manque de 'threads'/mémoire"
        ger "Kein Speicher mehr vorhanden. Prüfen Sie, ob mysqld oder ein anderer Prozess den gesamten Speicher verbraucht. Wenn nicht, sollten Sie mit 'ulimit' dafür sorgen, dass mysqld mehr Speicher benutzen darf, oder mehr Swap-Speicher einrichten"
        greek "Πρόβλημα με τη διαθέσιμη μνήμη (Out of thread space/memory)"
        hun "Elfogyott a thread-memoria"
        ita "Fine dello spazio/memoria per i thread"
        jpn "メモリが不足しています。mysqld やその他のプロセスがメモリーを使い切っていないか確認して下さい。メモリーを使い切っていない場合、'ulimit'の設定等で mysqld のメモリー使用最大量を多くするか、スワップ領域を増やす必要があるかもしれません。"
# This message failed to convert from euc-kr, skipped
        nor "Tomt for tråd plass/minne"
        norwegian-ny "Tomt for tråd plass/minne"
        pol "Zbyt mało miejsca/pamięci dla w?tku"
        por "Sem memória. Verifique se o mysqld ou algum outro processo está usando toda memória disponível. Se não, você pode ter que usar 'ulimit' para permitir ao mysqld usar mais memória ou você pode adicionar mais área de 'swap'"
        rum "Out of memory;  Verifica daca mysqld sau vreun alt proces foloseste toate memoria disponbila. Altfel, trebuie sa folosesi 'ulimit' ca sa permiti lui memoria disponbila. Altfel, trebuie sa folosesi 'ulimit' ca sa permiti lui mysqld sa foloseasca mai multa memorie ori adauga mai mult spatiu pentru swap (swap space)"
        rus "Недостаточно памяти; удостоверьтесь, что mysqld или какой-либо другой процесс не занимает всю доступную память. Если нет, то вы можете использовать ulimit, чтобы выделить для mysqld больше памяти, или увеличить объем файла подкачки"
        serbian "Nema memorije; Proverite da li MySQL server ili neki drugi proces koristi svu slobodnu memoriju. (UNIX: Ako ne, probajte da upotrebite 'ulimit' komandu da biste dozvolili daemon-u da koristi više memorije ili probajte da dodate više swap memorije)"
        slo "Málo miesta-pamäti pre vlákno"
        spa "Memoria/espacio de tranpaso insuficiente"
        swe "Fick slut på minnet.  Kontrollera om mysqld eller någon annan process använder allt tillgängligt minne. Om inte, försök använda 'ulimit' eller allokera mera swap"
        ukr "Брак пам'яті;  Перевірте чи mysqld або якісь інші процеси використовують усю доступну пам'ять. Як ні, то ви можете скористатися 'ulimit', аби дозволити mysqld використовувати більше пам'яті або ви можете додати більше місця під свап"
ER_BAD_HOST_ERROR 08S01
        cze "Nemohu zjistit jméno stroje pro Vaši adresu"
        dan "Kan ikke få værtsnavn for din adresse"
        nla "Kan de hostname niet krijgen van uw adres"
        eng "Can't get hostname for your address"
        est "Ei suuda lahendada IP aadressi masina nimeks"
        fre "Ne peut obtenir de hostname pour votre adresse"
        ger "Kann Hostnamen für diese Adresse nicht erhalten"
        greek "Δεν έγινε γνωστό το hostname για την address σας"
        hun "A gepnev nem allapithato meg a cimbol"
        ita "Impossibile risalire al nome dell'host dall'indirizzo (risoluzione inversa)"
        jpn "IPアドレスからホスト名を解決できません。"
        kor "당신의 컴퓨터의 호스트이름을 얻을 수 없읍니다."
        nor "Kan ikke få tak i vertsnavn for din adresse"
        norwegian-ny "Kan ikkje få tak i vertsnavn for di adresse"
        pol "Nie można otrzymać nazwy hosta dla twojego adresu"
        por "Não pode obter nome do 'host' para seu endereço"
        rum "Nu pot sa obtin hostname-ul adresei tale"
        rus "Невозможно получить имя хоста для вашего адреса"
        serbian "Ne mogu da dobijem ime host-a za vašu IP adresu"
        slo "Nemôžem zistiť meno hostiteľa pre vašu adresu"
        spa "No puedo obtener el nombre de maquina de tu direccion"
        swe "Kan inte hitta 'hostname' för din adress"
        ukr "Не можу визначити ім'я хосту для вашої адреси"
ER_HANDSHAKE_ERROR 08S01
        cze "Chyba při ustavování spojení"
        dan "Forkert håndtryk (handshake)"
        nla "Verkeerde handshake"
        eng "Bad handshake"
        est "Väär handshake"
        fre "Mauvais 'handshake'"
        ger "Ungültiger Handshake"
        greek "Η αναγνώριση (handshake) δεν έγινε σωστά"
        hun "A kapcsolatfelvetel nem sikerult (Bad handshake)"
        ita "Negoziazione impossibile"
        jpn "ハンドシェイクエラー"
        nor "Feil håndtrykk (handshake)"
        norwegian-ny "Feil handtrykk (handshake)"
        pol "Zły uchwyt(handshake)"
        por "Negociação de acesso falhou"
        rum "Prost inceput de conectie (bad handshake)"
        rus "Некорректное приветствие"
        serbian "Loš početak komunikacije (handshake)"
        slo "Chyba pri nadväzovaní spojenia"
        spa "Protocolo erroneo"
        swe "Fel vid initiering av kommunikationen med klienten"
        ukr "Невірна установка зв'язку"
ER_DBACCESS_DENIED_ERROR 42000
        cze "Přístup pro uživatele '%-.48s'@'%-.64s' k databázi '%-.192s' není povolen"
        dan "Adgang nægtet bruger: '%-.48s'@'%-.64s' til databasen '%-.192s'"
        nla "Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' naar database '%-.192s'"
        eng "Access denied for user '%-.48s'@'%-.64s' to database '%-.192s'"
        est "Ligipääs keelatud kasutajale '%-.48s'@'%-.64s' andmebaasile '%-.192s'"
        fre "Accès refusé pour l'utilisateur: '%-.48s'@'@%-.64s'. Base '%-.192s'"
        ger "Benutzer '%-.48s'@'%-.64s' hat keine Zugriffsberechtigung für Datenbank '%-.192s'"
        greek "Δεν επιτέρεται η πρόσβαση στο χρήστη: '%-.48s'@'%-.64s' στη βάση δεδομένων '%-.192s'"
        hun "A(z) '%-.48s'@'%-.64s' felhasznalo szamara tiltott eleres az '%-.192s' adabazishoz."
        ita "Accesso non consentito per l'utente: '%-.48s'@'%-.64s' al database '%-.192s'"
        jpn "ユーザー '%-.48s'@'%-.64s' によるデータベース '%-.192s' へのアクセスは拒否されました。"
        kor "'%-.48s'@'%-.64s' 사용자는 '%-.192s' 데이타베이스에 접근이 거부 되었습니다."
        nor "Tilgang nektet for bruker: '%-.48s'@'%-.64s' til databasen '%-.192s' nektet"
        norwegian-ny "Tilgang ikkje tillate for brukar: '%-.48s'@'%-.64s' til databasen '%-.192s' nekta"
        por "Acesso negado para o usuário '%-.48s'@'%-.64s' ao banco de dados '%-.192s'"
        rum "Acces interzis pentru utilizatorul: '%-.48s'@'%-.64s' la baza de date '%-.192s'"
        rus "Для пользователя '%-.48s'@'%-.64s' доступ к базе данных '%-.192s' закрыт"
        serbian "Pristup je zabranjen korisniku '%-.48s'@'%-.64s' za bazu '%-.192s'"
        slo "Zakázaný prístup pre užívateľa: '%-.48s'@'%-.64s' k databázi '%-.192s'"
        spa "Acceso negado para usuario: '%-.48s'@'%-.64s' para la base de datos '%-.192s'"
        swe "Användare '%-.48s'@'%-.64s' är ej berättigad att använda databasen %-.192s"
        ukr "Доступ заборонено для користувача: '%-.48s'@'%-.64s' до бази данних '%-.192s'"
ER_ACCESS_DENIED_ERROR 28000
        cze "Přístup pro uživatele '%-.48s'@'%-.64s' (s heslem %s)"
        dan "Adgang nægtet bruger: '%-.48s'@'%-.64s' (Bruger adgangskode: %s)"
        nla "Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s' (Wachtwoord gebruikt: %s)"
        eng "Access denied for user '%-.48s'@'%-.64s' (using password: %s)"
        est "Ligipääs keelatud kasutajale '%-.48s'@'%-.64s' (kasutab parooli: %s)"
        fre "Accès refusé pour l'utilisateur: '%-.48s'@'@%-.64s' (mot de passe: %s)"
        ger "Benutzer '%-.48s'@'%-.64s' hat keine Zugriffsberechtigung (verwendetes Passwort: %s)"
        greek "Δεν επιτέρεται η πρόσβαση στο χρήστη: '%-.48s'@'%-.64s' (χρήση password: %s)"
        hun "A(z) '%-.48s'@'%-.64s' felhasznalo szamara tiltott eleres. (Hasznalja a jelszot: %s)"
        ita "Accesso non consentito per l'utente: '%-.48s'@'%-.64s' (Password: %s)"
        jpn "ユーザー '%-.48s'@'%-.64s' のアクセスは拒否されました。(using password: %s)"
        kor "'%-.48s'@'%-.64s' 사용자는 접근이 거부 되었습니다. (using password: %s)"
        nor "Tilgang nektet for bruker: '%-.48s'@'%-.64s' (Bruker passord: %s)"
        norwegian-ny "Tilgang ikke tillate for brukar: '%-.48s'@'%-.64s' (Brukar passord: %s)"
        por "Acesso negado para o usuário '%-.48s'@'%-.64s' (senha usada: %s)"
        rum "Acces interzis pentru utilizatorul: '%-.48s'@'%-.64s' (Folosind parola: %s)"
        rus "Доступ закрыт для пользователя '%-.48s'@'%-.64s' (был использован пароль: %s)"
        serbian "Pristup je zabranjen korisniku '%-.48s'@'%-.64s' (koristi lozinku: '%s')"
        slo "Zakázaný prístup pre užívateľa: '%-.48s'@'%-.64s' (použitie hesla: %s)"
        spa "Acceso negado para usuario: '%-.48s'@'%-.64s' (Usando clave: %s)"
        swe "Användare '%-.48s'@'%-.64s' är ej berättigad att logga in (Använder lösen: %s)"
        ukr "Доступ заборонено для користувача: '%-.48s'@'%-.64s' (Використано пароль: %s)"
ER_NO_DB_ERROR 3D000
        cze "Nebyla vybrána žádná databáze"
        dan "Ingen database valgt"
        nla "Geen database geselecteerd"
        eng "No database selected"
        est "Andmebaasi ei ole valitud"
        fre "Aucune base n'a été sélectionnée"
        ger "Keine Datenbank ausgewählt"
        greek "Δεν επιλέχθηκε βάση δεδομένων"
        hun "Nincs kivalasztott adatbazis"
        ita "Nessun database selezionato"
        jpn "データベースが選択されていません。"
        kor "선택된 데이타베이스가 없습니다."
        nor "Ingen database valgt"
        norwegian-ny "Ingen database vald"
        pol "Nie wybrano żadnej bazy danych"
        por "Nenhum banco de dados foi selecionado"
        rum "Nici o baza de data nu a fost selectata inca"
        rus "База данных не выбрана"
        serbian "Ni jedna baza nije selektovana"
        slo "Nebola vybraná databáza"
        spa "Base de datos no seleccionada"
        swe "Ingen databas i användning"
        ukr "Базу данних не вибрано"
ER_UNKNOWN_COM_ERROR 08S01
        cze "Neznámý příkaz"
        dan "Ukendt kommando"
        nla "Onbekend commando"
        eng "Unknown command"
        est "Tundmatu käsk"
        fre "Commande inconnue"
        ger "Unbekannter Befehl"
        greek "Αγνωστη εντολή"
        hun "Ervenytelen parancs"
        ita "Comando sconosciuto"
        jpn "不明なコマンドです。"
        kor "명령어가 뭔지 모르겠어요..."
        nor "Ukjent kommando"
        norwegian-ny "Ukjent kommando"
        pol "Nieznana komenda"
        por "Comando desconhecido"
        rum "Comanda invalida"
        rus "Неизвестная команда коммуникационного протокола"
        serbian "Nepoznata komanda"
        slo "Neznámy príkaz"
        spa "Comando desconocido"
        swe "Okänt kommando"
        ukr "Невідома команда"
ER_BAD_NULL_ERROR 23000
        cze "Sloupec '%-.192s' nemůže být null"
        dan "Kolonne '%-.192s' kan ikke være NULL"
        nla "Kolom '%-.192s' kan niet null zijn"
        eng "Column '%-.192s' cannot be null"
        est "Tulp '%-.192s' ei saa omada nullväärtust"
        fre "Le champ '%-.192s' ne peut être vide (null)"
        ger "Feld '%-.192s' darf nicht NULL sein"
        greek "Το πεδίο '%-.192s' δεν μπορεί να είναι κενό (null)"
        hun "A(z) '%-.192s' oszlop erteke nem lehet nulla"
        ita "La colonna '%-.192s' non puo` essere nulla"
        jpn "列 '%-.192s' は null にできません。"
        kor "칼럼 '%-.192s'는 널(Null)이 되면 안됩니다. "
        nor "Kolonne '%-.192s' kan ikke vere null"
        norwegian-ny "Kolonne '%-.192s' kan ikkje vere null"
        pol "Kolumna '%-.192s' nie może być null"
        por "Coluna '%-.192s' não pode ser vazia"
        rum "Coloana '%-.192s' nu poate sa fie null"
        rus "Столбец '%-.192s' не может принимать величину NULL"
        serbian "Kolona '%-.192s' ne može biti NULL"
        slo "Pole '%-.192s' nemôže byť null"
        spa "La columna '%-.192s' no puede ser nula"
        swe "Kolumn '%-.192s' får inte vara NULL"
        ukr "Стовбець '%-.192s' не може бути нульовим"
ER_BAD_DB_ERROR 42000
        cze "Neznámá databáze '%-.192s'"
        dan "Ukendt database '%-.192s'"
        nla "Onbekende database '%-.192s'"
        eng "Unknown database '%-.192s'"
        est "Tundmatu andmebaas '%-.192s'"
        fre "Base '%-.192s' inconnue"
        ger "Unbekannte Datenbank '%-.192s'"
        greek "Αγνωστη βάση δεδομένων '%-.192s'"
        hun "Ervenytelen adatbazis: '%-.192s'"
        ita "Database '%-.192s' sconosciuto"
        jpn "'%-.192s' は不明なデータベースです。"
        kor "데이타베이스 '%-.192s'는 알수 없음"
        nor "Ukjent database '%-.192s'"
        norwegian-ny "Ukjent database '%-.192s'"
        pol "Nieznana baza danych '%-.192s'"
        por "Banco de dados '%-.192s' desconhecido"
        rum "Baza de data invalida '%-.192s'"
        rus "Неизвестная база данных '%-.192s'"
        serbian "Nepoznata baza '%-.192s'"
        slo "Neznáma databáza '%-.192s'"
        spa "Base de datos desconocida '%-.192s'"
        swe "Okänd databas: '%-.192s'"
        ukr "Невідома база данних '%-.192s'"
ER_TABLE_EXISTS_ERROR 42S01
        cze "Tabulka '%-.192s' již existuje"
        dan "Tabellen '%-.192s' findes allerede"
        nla "Tabel '%-.192s' bestaat al"
        eng "Table '%-.192s' already exists"
        est "Tabel '%-.192s' juba eksisteerib"
        fre "La table '%-.192s' existe déjà"
        ger "Tabelle '%-.192s' bereits vorhanden"
        greek "Ο πίνακας '%-.192s' υπάρχει ήδη"
        hun "A(z) '%-.192s' tabla mar letezik"
        ita "La tabella '%-.192s' esiste gia`"
        jpn "表 '%-.192s' はすでに存在します。"
        kor "테이블 '%-.192s'는 이미 존재함"
        nor "Tabellen '%-.192s' eksisterer allerede"
        norwegian-ny "Tabellen '%-.192s' eksisterar allereide"
        pol "Tabela '%-.192s' już istnieje"
        por "Tabela '%-.192s' já existe"
        rum "Tabela '%-.192s' exista deja"
        rus "Таблица '%-.192s' уже существует"
        serbian "Tabela '%-.192s' već postoji"
        slo "Tabuľka '%-.192s' už existuje"
        spa "La tabla  '%-.192s' ya existe"
        swe "Tabellen '%-.192s' finns redan"
        ukr "Таблиця '%-.192s' вже існує"
ER_BAD_TABLE_ERROR 42S02
        cze "Neznámá tabulka '%-.129s'"
        dan "Ukendt tabel '%-.129s'"
        nla "Onbekende tabel '%-.129s'"
        eng "Unknown table '%-.129s'"
        est "Tundmatu tabel '%-.129s'"
        fre "Table '%-.129s' inconnue"
        ger "Unbekannte Tabelle '%-.129s'"
        greek "Αγνωστος πίνακας '%-.129s'"
        hun "Ervenytelen tabla: '%-.129s'"
        ita "Tabella '%-.129s' sconosciuta"
        jpn "'%-.129s' は不明な表です。"
        kor "테이블 '%-.129s'는 알수 없음"
        nor "Ukjent tabell '%-.129s'"
        norwegian-ny "Ukjent tabell '%-.129s'"
        pol "Nieznana tabela '%-.129s'"
        por "Tabela '%-.129s' desconhecida"
        rum "Tabela '%-.129s' este invalida"
        rus "Неизвестная таблица '%-.129s'"
        serbian "Nepoznata tabela '%-.129s'"
        slo "Neznáma tabuľka '%-.129s'"
        spa "Tabla '%-.129s' desconocida"
        swe "Okänd tabell '%-.129s'"
        ukr "Невідома таблиця '%-.129s'"
ER_NON_UNIQ_ERROR 23000
        cze "Sloupec '%-.192s' v %-.192s není zcela jasný"
        dan "Felt: '%-.192s' i tabel %-.192s er ikke entydigt"
        nla "Kolom: '%-.192s' in %-.192s is niet eenduidig"
        eng "Column '%-.192s' in %-.192s is ambiguous"
        est "Väli '%-.192s' %-.192s-s ei ole ühene"
        fre "Champ: '%-.192s' dans %-.192s est ambigu"
        ger "Feld '%-.192s' in %-.192s ist nicht eindeutig"
        greek "Το πεδίο: '%-.192s' σε %-.192s δεν έχει καθοριστεί"
        hun "A(z) '%-.192s' oszlop %-.192s-ben ketertelmu"
        ita "Colonna: '%-.192s' di %-.192s e` ambigua"
        jpn "列 '%-.192s' は %-.192s 内で曖昧です。"
        kor "칼럼: '%-.192s' in '%-.192s' 이 모호함"
        nor "Felt: '%-.192s' i tabell %-.192s er ikke entydig"
        norwegian-ny "Kolonne: '%-.192s' i tabell %-.192s er ikkje eintydig"
        pol "Kolumna: '%-.192s' w  %-.192s jest dwuznaczna"
        por "Coluna '%-.192s' em '%-.192s' é ambígua"
        rum "Coloana: '%-.192s' in %-.192s este ambigua"
        rus "Столбец '%-.192s' в %-.192s задан неоднозначно"
        serbian "Kolona '%-.192s' u %-.192s nije jedinstvena u kontekstu"
        slo "Pole: '%-.192s' v %-.192s je nejasné"
        spa "La columna: '%-.192s' en %-.192s es ambigua"
        swe "Kolumn '%-.192s' i %-.192s är inte unik"
        ukr "Стовбець '%-.192s' у %-.192s визначений неоднозначно"
ER_SERVER_SHUTDOWN 08S01
        cze "Probíhá ukončování práce serveru"
        dan "Database nedlukning er i gang"
        nla "Bezig met het stoppen van de server"
        eng "Server shutdown in progress"
        est "Serveri seiskamine käib"
        fre "Arrêt du serveur en cours"
        ger "Der Server wird heruntergefahren"
        greek "Εναρξη διαδικασίας αποσύνδεσης του εξυπηρετητή (server shutdown)"
        hun "A szerver leallitasa folyamatban"
        ita "Shutdown del server in corso"
        jpn "サーバーをシャットダウン中です。"
        kor "Server가 셧다운 중입니다."
        nor "Database nedkobling er i gang"
        norwegian-ny "Tenar nedkopling er i gang"
        pol "Trwa kończenie działania serwera"
        por "'Shutdown' do servidor em andamento"
        rum "Terminarea serverului este in desfasurare"
        rus "Сервер находится в процессе остановки"
        serbian "Gašenje servera je u toku"
        slo "Prebieha ukončovanie práce servera"
        spa "Desconexion de servidor en proceso"
        swe "Servern går nu ned"
        ukr "Завершується работа сервера"
ER_BAD_FIELD_ERROR 42S22 S0022
        cze "Neznámý sloupec '%-.192s' v %-.192s"
        dan "Ukendt kolonne '%-.192s' i tabel %-.192s"
        nla "Onbekende kolom '%-.192s' in %-.192s"
        eng "Unknown column '%-.192s' in '%-.192s'"
        est "Tundmatu tulp '%-.192s' '%-.192s'-s"
        fre "Champ '%-.192s' inconnu dans %-.192s"
        ger "Unbekanntes Tabellenfeld '%-.192s' in %-.192s"
        greek "Αγνωστο πεδίο '%-.192s' σε '%-.192s'"
        hun "A(z) '%-.192s' oszlop ervenytelen '%-.192s'-ben"
        ita "Colonna sconosciuta '%-.192s' in '%-.192s'"
        jpn "列 '%-.192s' は '%-.192s' にはありません。"
        kor "Unknown 칼럼 '%-.192s' in '%-.192s'"
        nor "Ukjent kolonne '%-.192s' i tabell %-.192s"
        norwegian-ny "Ukjent felt '%-.192s' i tabell %-.192s"
        pol "Nieznana kolumna '%-.192s' w  %-.192s"
        por "Coluna '%-.192s' desconhecida em '%-.192s'"
        rum "Coloana invalida '%-.192s' in '%-.192s'"
        rus "Неизвестный столбец '%-.192s' в '%-.192s'"
        serbian "Nepoznata kolona '%-.192s' u '%-.192s'"
        slo "Neznáme pole '%-.192s' v '%-.192s'"
        spa "La columna '%-.192s' en %-.192s es desconocida"
        swe "Okänd kolumn '%-.192s' i %-.192s"
        ukr "Невідомий стовбець '%-.192s' у '%-.192s'"

# When using this error code, please use ER(ER_WRONG_FIELD_WITH_GROUP_V2)
# for the message string.
ER_WRONG_FIELD_WITH_GROUP 42000 S1009
        cze "Použité '%-.192s' nebylo v group by"
        dan "Brugte '%-.192s' som ikke var i group by"
        nla "Opdracht gebruikt '%-.192s' dat niet in de GROUP BY voorkomt"
        eng "'%-.192s' isn't in GROUP BY"
        est "'%-.192s' puudub GROUP BY klauslis"
        fre "'%-.192s' n'est pas dans 'group by'"
        ger "'%-.192s' ist nicht in GROUP BY vorhanden"
        greek "Χρησιμοποιήθηκε '%-.192s' που δεν υπήρχε στο group by"
        hun "Used '%-.192s' with wasn't in group by"
        ita "Usato '%-.192s' che non e` nel GROUP BY"
        jpn "'%-.192s' はGROUP BY句で指定されていません。"
        kor "'%-.192s'은 GROUP BY속에 없음"
        nor "Brukte '%-.192s' som ikke var i group by"
        norwegian-ny "Brukte '%-.192s' som ikkje var i group by"
        pol "Użyto '%-.192s' bez umieszczenia w group by"
        por "'%-.192s' não está em 'GROUP BY'"
        rum "'%-.192s' nu exista in clauza GROUP BY"
        rus "'%-.192s' не присутствует в GROUP BY"
        serbian "Entitet '%-.192s' nije naveden u komandi 'GROUP BY'"
        slo "Použité '%-.192s' nebolo v 'group by'"
        spa "Usado '%-.192s' el cual no esta group by"
        swe "'%-.192s' finns inte i GROUP BY"
        ukr "'%-.192s' не є у GROUP BY"
ER_WRONG_GROUP_FIELD 42000 S1009
        cze "Nemohu použít group na '%-.192s'"
        dan "Kan ikke gruppere på '%-.192s'"
        nla "Kan '%-.192s' niet groeperen"
        eng "Can't group on '%-.192s'"
        est "Ei saa grupeerida '%-.192s' järgi"
        fre "Ne peut regrouper '%-.192s'"
        ger "Gruppierung über '%-.192s' nicht möglich"
        greek "Αδύνατη η ομαδοποίηση (group on) '%-.192s'"
        hun "A group nem hasznalhato: '%-.192s'"
        ita "Impossibile raggruppare per '%-.192s'"
        jpn "'%-.192s' でのグループ化はできません。"
        kor "'%-.192s'를 그룹할 수 없음"
        nor "Kan ikke gruppere på '%-.192s'"
        norwegian-ny "Kan ikkje gruppere på '%-.192s'"
        pol "Nie można grupować po '%-.192s'"
        por "Não pode agrupar em '%-.192s'"
        rum "Nu pot sa grupez pe (group on) '%-.192s'"
        rus "Невозможно произвести группировку по '%-.192s'"
        serbian "Ne mogu da grupišem po '%-.192s'"
        slo "Nemôžem použiť 'group' na '%-.192s'"
        spa "No puedo agrupar por '%-.192s'"
        swe "Kan inte använda GROUP BY med '%-.192s'"
        ukr "Не можу групувати по '%-.192s'"
ER_WRONG_SUM_SELECT 42000 S1009
        cze "Příkaz obsahuje zároveň funkci sum a sloupce"
        dan "Udtrykket har summer (sum) funktioner og kolonner i samme udtryk"
        nla "Opdracht heeft totaliseer functies en kolommen in dezelfde opdracht"
        eng "Statement has sum functions and columns in same statement"
        est "Lauses on korraga nii tulbad kui summeerimisfunktsioonid"
        fre "Vous demandez la fonction sum() et des champs dans la même commande"
        ger "Die Verwendung von Summierungsfunktionen und Spalten im selben Befehl ist nicht erlaubt"
        greek "Η διατύπωση περιέχει sum functions και columns στην ίδια διατύπωση"
        ita "Il comando ha una funzione SUM e una colonna non specificata nella GROUP BY"
        jpn "集計関数と通常の列が同時に指定されています。"
        kor "Statement 가 sum기능을 동작중이고 칼럼도 동일한 statement입니다."
        nor "Uttrykket har summer (sum) funksjoner og kolonner i samme uttrykk"
        norwegian-ny "Uttrykket har summer (sum) funksjoner og kolonner i same uttrykk"
        pol "Zapytanie ma funkcje sumuj?ce i kolumny w tym samym zapytaniu"
        por "Cláusula contém funções de soma e colunas juntas"
        rum "Comanda are functii suma si coloane in aceeasi comanda"
        rus "Выражение содержит групповые функции и столбцы, но не включает GROUP BY. А как вы умудрились получить это сообщение об ошибке?"
        serbian "Izraz ima 'SUM' agregatnu funkciju i kolone u isto vreme"
        slo "Príkaz obsahuje zároveň funkciu 'sum' a poľa"
        spa "El estamento tiene funciones de suma y columnas en el mismo estamento"
        swe "Kommandot har både sum functions och enkla funktioner"
        ukr "У виразі використано підсумовуючі функції поряд з іменами стовбців"
ER_WRONG_VALUE_COUNT 21S01
        cze "Počet sloupců neodpovídá zadané hodnotě"
        dan "Kolonne tæller stemmer ikke med antallet af værdier"
        nla "Het aantal kolommen komt niet overeen met het aantal opgegeven waardes"
        eng "Column count doesn't match value count"
        est "Tulpade arv erineb väärtuste arvust"
        ger "Die Anzahl der Spalten entspricht nicht der Anzahl der Werte"
        greek "Το Column count δεν ταιριάζει με το value count"
        hun "Az oszlopban levo ertek nem egyezik meg a szamitott ertekkel"
        ita "Il numero delle colonne non e` uguale al numero dei valori"
        jpn "列数が値の個数と一致しません。"
        kor "칼럼의 카운트가 값의 카운트와 일치하지 않습니다."
        nor "Felt telling stemmer verdi telling"
        norwegian-ny "Kolonne telling stemmer verdi telling"
        pol "Liczba kolumn nie odpowiada liczbie warto?ci"
        por "Contagem de colunas não confere com a contagem de valores"
        rum "Numarul de coloane nu este acelasi cu numarul valoarei"
        rus "Количество столбцов не совпадает с количеством значений"
        serbian "Broj kolona ne odgovara broju vrednosti"
        slo "Počet polí nezodpovedá zadanej hodnote"
        spa "La columna con count no tiene valores para contar"
        swe "Antalet kolumner motsvarar inte antalet värden"
        ukr "Кількість стовбців не співпадає з кількістю значень"
ER_TOO_LONG_IDENT 42000 S1009
        cze "Jméno identifikátoru '%-.100s' je příliš dlouhé"
        dan "Navnet '%-.100s' er for langt"
        nla "Naam voor herkenning '%-.100s' is te lang"
        eng "Identifier name '%-.100s' is too long"
        est "Identifikaatori '%-.100s' nimi on liiga pikk"
        fre "Le nom de l'identificateur '%-.100s' est trop long"
        ger "Name des Bezeichners '%-.100s' ist zu lang"
        greek "Το identifier name '%-.100s' είναι πολύ μεγάλο"
        hun "A(z) '%-.100s' azonositonev tul hosszu."
        ita "Il nome dell'identificatore '%-.100s' e` troppo lungo"
        jpn "識別子名 '%-.100s' は長すぎます。"
        kor "Identifier '%-.100s'는 너무 길군요."
        nor "Identifikator '%-.100s' er for lang"
        norwegian-ny "Identifikator '%-.100s' er for lang"
        pol "Nazwa identyfikatora '%-.100s' jest zbyt długa"
        por "Nome identificador '%-.100s' é longo demais"
        rum "Numele indentificatorului '%-.100s' este prea lung"
        rus "Слишком длинный идентификатор '%-.100s'"
        serbian "Ime '%-.100s' je predugačko"
        slo "Meno identifikátora '%-.100s' je príliš dlhé"
        spa "El nombre del identificador '%-.100s' es demasiado grande"
        swe "Kolumnnamn '%-.100s' är för långt"
        ukr "Ім'я ідентифікатора '%-.100s' задовге"
ER_DUP_FIELDNAME 42S21 S1009
        cze "Zdvojené jméno sloupce '%-.192s'"
        dan "Feltnavnet '%-.192s' findes allerede"
        nla "Dubbele kolom naam '%-.192s'"
        eng "Duplicate column name '%-.192s'"
        est "Kattuv tulba nimi '%-.192s'"
        fre "Nom du champ '%-.192s' déjà utilisé"
        ger "Doppelter Spaltenname: '%-.192s'"
        greek "Επανάληψη column name '%-.192s'"
        hun "Duplikalt oszlopazonosito: '%-.192s'"
        ita "Nome colonna duplicato '%-.192s'"
        jpn "列名 '%-.192s' は重複してます。"
        kor "중복된 칼럼 이름: '%-.192s'"
        nor "Feltnavnet '%-.192s' eksisterte fra før"
        norwegian-ny "Feltnamnet '%-.192s' eksisterte frå før"
        pol "Powtórzona nazwa kolumny '%-.192s'"
        por "Nome da coluna '%-.192s' duplicado"
        rum "Numele coloanei '%-.192s' e duplicat"
        rus "Дублирующееся имя столбца '%-.192s'"
        serbian "Duplirano ime kolone '%-.192s'"
        slo "Opakované meno poľa '%-.192s'"
        spa "Nombre de columna duplicado '%-.192s'"
        swe "Kolumnnamn '%-.192s finns flera gånger"
        ukr "Дублююче ім'я стовбця '%-.192s'"
ER_DUP_KEYNAME 42000 S1009
        cze "Zdvojené jméno klíče '%-.192s'"
        dan "Indeksnavnet '%-.192s' findes allerede"
        nla "Dubbele zoeksleutel naam '%-.192s'"
        eng "Duplicate key name '%-.192s'"
        est "Kattuv võtme nimi '%-.192s'"
        fre "Nom de clef '%-.192s' déjà utilisé"
        ger "Doppelter Name für Schlüssel vorhanden: '%-.192s'"
        greek "Επανάληψη key name '%-.192s'"
        hun "Duplikalt kulcsazonosito: '%-.192s'"
        ita "Nome chiave duplicato '%-.192s'"
        jpn "索引名 '%-.192s' は重複しています。"
        kor "중복된 키 이름 : '%-.192s'"
        nor "Nøkkelnavnet '%-.192s' eksisterte fra før"
        norwegian-ny "Nøkkelnamnet '%-.192s' eksisterte frå før"
        pol "Powtórzony nazwa klucza '%-.192s'"
        por "Nome da chave '%-.192s' duplicado"
        rum "Numele cheiei '%-.192s' e duplicat"
        rus "Дублирующееся имя ключа '%-.192s'"
        serbian "Duplirano ime ključa '%-.192s'"
        slo "Opakované meno kľúča '%-.192s'"
        spa "Nombre de clave duplicado '%-.192s'"
        swe "Nyckelnamn '%-.192s' finns flera gånger"
        ukr "Дублююче ім'я ключа '%-.192s'"
# When using this error code, please use ER(ER_DUP_ENTRY_WITH_KEY_NAME)
# for the message string.  See, for example, code in handler.cc.
ER_DUP_ENTRY 23000 S1009
	cze "Zdvojený klíč '%-.192s' (číslo klíče %d)"
	dan "Ens værdier '%-.192s' for indeks %d"
	nla "Dubbele ingang '%-.192s' voor zoeksleutel %d"
	eng "Duplicate entry '%-.192s' for key %d"
	est "Kattuv väärtus '%-.192s' võtmele %d"
	fre "Duplicata du champ '%-.192s' pour la clef %d"
	ger "Doppelter Eintrag '%-.192s' für Schlüssel %d"
	greek "Διπλή εγγραφή '%-.192s' για το κλειδί %d"
	hun "Duplikalt bejegyzes '%-.192s' a %d kulcs szerint."
	ita "Valore duplicato '%-.192s' per la chiave %d"
	jpn "'%-.192s' は索引 %d で重複しています。"
	kor "중복된 입력 값 '%-.192s': key %d"
	nor "Like verdier '%-.192s' for nøkkel %d"
	norwegian-ny "Like verdiar '%-.192s' for nykkel %d"
	pol "Powtórzone wystąpienie '%-.192s' dla klucza %d"
	por "Entrada '%-.192s' duplicada para a chave %d"
	rum "Cimpul '%-.192s' e duplicat pentru cheia %d"
	rus "Дублирующаяся запись '%-.192s' по ключу %d"
	serbian "Dupliran unos '%-.192s' za ključ '%d'"
	slo "Opakovaný kľúč '%-.192s' (číslo kľúča %d)"
	spa "Entrada duplicada '%-.192s' para la clave %d"
	swe "Dublett '%-.192s' för nyckel %d"
	ukr "Дублюючий запис '%-.192s' для ключа %d"
ER_WRONG_FIELD_SPEC 42000 S1009
        cze "Chybná specifikace sloupce '%-.192s'"
        dan "Forkert kolonnespecifikaton for felt '%-.192s'"
        nla "Verkeerde kolom specificatie voor kolom '%-.192s'"
        eng "Incorrect column specifier for column '%-.192s'"
        est "Vigane tulba kirjeldus tulbale '%-.192s'"
        fre "Mauvais paramètre de champ pour le champ '%-.192s'"
        ger "Falsche Spezifikation für Feld '%-.192s'"
        greek "Εσφαλμένο column specifier για το πεδίο '%-.192s'"
        hun "Rossz oszlopazonosito: '%-.192s'"
        ita "Specifica errata per la colonna '%-.192s'"
        jpn "列 '%-.192s' の定義が不正です。"
        kor "칼럼 '%-.192s'의 부정확한 칼럼 정의자"
        nor "Feil kolonne spesifikator for felt '%-.192s'"
        norwegian-ny "Feil kolonne spesifikator for kolonne '%-.192s'"
        pol "Błędna specyfikacja kolumny dla kolumny '%-.192s'"
        por "Especificador de coluna incorreto para a coluna '%-.192s'"
        rum "Specificandul coloanei '%-.192s' este incorect"
        rus "Некорректный определитель столбца для столбца '%-.192s'"
        serbian "Pogrešan naziv kolone za kolonu '%-.192s'"
        slo "Chyba v špecifikácii poľa '%-.192s'"
        spa "Especificador de columna erroneo para la columna '%-.192s'"
        swe "Felaktigt kolumntyp för kolumn '%-.192s'"
        ukr "Невірний специфікатор стовбця '%-.192s'"
ER_PARSE_ERROR 42000 s1009
        cze "%s blízko '%-.80s' na řádku %d"
        dan "%s nær '%-.80s' på linje %d"
        nla "%s bij '%-.80s' in regel %d"
        eng "%s near '%-.80s' at line %d"
        est "%s '%-.80s' ligidal real %d"
        fre "%s près de '%-.80s' à la ligne %d"
        ger "%s bei '%-.80s' in Zeile %d"
        greek "%s πλησίον '%-.80s' στη γραμμή %d"
        hun "A %s a '%-.80s'-hez kozeli a %d sorban"
        ita "%s vicino a '%-.80s' linea %d"
        jpn "%s : '%-.80s' 付近 %d 行目"
        kor "'%s' 에러 같읍니다. ('%-.80s' 명령어 라인 %d)"
        nor "%s nær '%-.80s' på linje %d"
        norwegian-ny "%s attmed '%-.80s' på line %d"
        pol "%s obok '%-.80s' w linii %d"
        por "%s próximo a '%-.80s' na linha %d"
        rum "%s linga '%-.80s' pe linia %d"
        rus "%s около '%-.80s' на строке %d"
        serbian "'%s' u iskazu '%-.80s' na liniji %d"
        slo "%s blízko '%-.80s' na riadku %d"
        spa "%s cerca '%-.80s' en la linea %d"
        swe "%s nära '%-.80s' på rad %d"
        ukr "%s біля '%-.80s' в строці %d"
ER_EMPTY_QUERY 42000
        cze "Výsledek dotazu je prázdný"
        dan "Forespørgsel var tom"
        nla "Query was leeg"
        eng "Query was empty"
        est "Tühi päring"
        fre "Query est vide"
        ger "Leere Abfrage"
        greek "Το ερώτημα (query) που θέσατε ήταν κενό"
        hun "Ures lekerdezes."
        ita "La query e` vuota"
        jpn "クエリが空です。"
        kor "쿼리결과가 없습니다."
        nor "Forespørsel var tom"
        norwegian-ny "Førespurnad var tom"
        pol "Zapytanie było puste"
        por "Consulta (query) estava vazia"
        rum "Query-ul a fost gol"
        rus "Запрос оказался пустым"
        serbian "Upit je bio prazan"
        slo "Výsledok požiadavky bol prázdny"
        spa "La query estaba vacia"
        swe "Frågan var tom"
        ukr "Пустий запит"
ER_NONUNIQ_TABLE 42000 S1009
        cze "Nejednoznačná tabulka/alias: '%-.192s'"
        dan "Tabellen/aliaset: '%-.192s' er ikke unikt"
        nla "Niet unieke waarde tabel/alias: '%-.192s'"
        eng "Not unique table/alias: '%-.192s'"
        est "Ei ole unikaalne tabel/alias '%-.192s'"
        fre "Table/alias: '%-.192s' non unique"
        ger "Tabellenname/Alias '%-.192s' nicht eindeutig"
        greek "Αδύνατη η ανεύρεση unique table/alias: '%-.192s'"
        hun "Nem egyedi tabla/alias: '%-.192s'"
        ita "Tabella/alias non unico: '%-.192s'"
        jpn "表名／別名 '%-.192s' は一意ではありません。"
        kor "Unique 하지 않은 테이블/alias: '%-.192s'"
        nor "Ikke unikt tabell/alias: '%-.192s'"
        norwegian-ny "Ikkje unikt tabell/alias: '%-.192s'"
        pol "Tabela/alias nie s? unikalne: '%-.192s'"
        por "Tabela/alias '%-.192s' não única"
        rum "Tabela/alias: '%-.192s' nu este unic"
        rus "Повторяющаяся таблица/псевдоним '%-.192s'"
        serbian "Tabela ili alias nisu bili jedinstveni: '%-.192s'"
        slo "Nie jednoznačná tabuľka/alias: '%-.192s'"
        spa "Tabla/alias: '%-.192s' es no unica"
        swe "Icke unikt tabell/alias: '%-.192s'"
        ukr "Неунікальна таблиця/псевдонім: '%-.192s'"
ER_INVALID_DEFAULT 42000 S1009
        cze "Chybná defaultní hodnota pro '%-.192s'"
        dan "Ugyldig standardværdi for '%-.192s'"
        nla "Foutieve standaard waarde voor '%-.192s'"
        eng "Invalid default value for '%-.192s'"
        est "Vigane vaikeväärtus '%-.192s' jaoks"
        fre "Valeur par défaut invalide pour '%-.192s'"
        ger "Fehlerhafter Vorgabewert (DEFAULT) für '%-.192s'"
        greek "Εσφαλμένη προκαθορισμένη τιμή (default value) για '%-.192s'"
        hun "Ervenytelen ertek: '%-.192s'"
        ita "Valore di default non valido per '%-.192s'"
        jpn "'%-.192s' へのデフォルト値が無効です。"
        kor "'%-.192s'의 유효하지 못한 디폴트 값을 사용하셨습니다."
        nor "Ugyldig standardverdi for '%-.192s'"
        norwegian-ny "Ugyldig standardverdi for '%-.192s'"
        pol "Niewła?ciwa warto?ć domy?lna dla '%-.192s'"
        por "Valor padrão (default) inválido para '%-.192s'"
        rum "Valoarea de default este invalida pentru '%-.192s'"
        rus "Некорректное значение по умолчанию для '%-.192s'"
        serbian "Loša default vrednost za '%-.192s'"
        slo "Chybná implicitná hodnota pre '%-.192s'"
        spa "Valor por defecto invalido para '%-.192s'"
        swe "Ogiltigt DEFAULT värde för '%-.192s'"
        ukr "Невірне значення по замовчуванню для '%-.192s'"
ER_MULTIPLE_PRI_KEY 42000 S1009
        cze "Definováno více primárních klíčů"
        dan "Flere primærnøgler specificeret"
        nla "Meerdere primaire zoeksleutels gedefinieerd"
        eng "Multiple primary key defined"
        est "Mitut primaarset võtit ei saa olla"
        fre "Plusieurs clefs primaires définies"
        ger "Mehrere Primärschlüssel (PRIMARY KEY) definiert"
        greek "Περισσότερα από ένα primary key ορίστηκαν"
        hun "Tobbszoros elsodleges kulcs definialas."
        ita "Definite piu` chiave primarie"
        jpn "PRIMARY KEY が複数定義されています。"
        kor "Multiple primary key가 정의되어 있슴"
        nor "Fleire primærnøkle spesifisert"
        norwegian-ny "Fleire primærnyklar spesifisert"
        pol "Zdefiniowano wiele kluczy podstawowych"
        por "Definida mais de uma chave primária"
        rum "Chei primare definite de mai multe ori"
        rus "Указано несколько первичных ключей"
        serbian "Definisani višestruki primarni ključevi"
        slo "Zadefinovaných viac primárnych kľúčov"
        spa "Multiples claves primarias definidas"
        swe "Flera PRIMARY KEY använda"
        ukr "Первинного ключа визначено неодноразово"
ER_TOO_MANY_KEYS 42000 S1009
        cze "Zadáno příliš mnoho klíčů, je povoleno nejvíce %d klíčů"
        dan "For mange nøgler specificeret. Kun %d nøgler må bruges"
        nla "Teveel zoeksleutels gedefinieerd. Maximaal zijn %d zoeksleutels toegestaan"
        eng "Too many keys specified; max %d keys allowed"
        est "Liiga palju võtmeid. Maksimaalselt võib olla %d võtit"
        fre "Trop de clefs sont définies. Maximum de %d clefs alloué"
        ger "Zu viele Schlüssel definiert. Maximal %d Schlüssel erlaubt"
        greek "Πάρα πολλά key ορίσθηκαν. Το πολύ %d επιτρέπονται"
        hun "Tul sok kulcs. Maximum %d kulcs engedelyezett."
        ita "Troppe chiavi. Sono ammesse max %d chiavi"
        jpn "索引の数が多すぎます。最大 %d 個までです。"
        kor "너무 많은 키가 정의되어 있읍니다.. 최대 %d의 키가 가능함"
        nor "For mange nøkler spesifisert. Maks %d nøkler tillatt"
        norwegian-ny "For mange nykler spesifisert. Maks %d nyklar tillatt"
        pol "Okre?lono zbyt wiele kluczy. Dostępnych jest maksymalnie %d kluczy"
        por "Especificadas chaves demais. O máximo permitido são %d chaves"
        rum "Prea multe chei. Numarul de chei maxim este %d"
        rus "Указано слишком много ключей. Разрешается указывать не более %d ключей"
        serbian "Navedeno je previše ključeva. Maksimum %d ključeva je dozvoljeno"
        slo "Zadaných ríliš veľa kľúčov. Najviac %d kľúčov je povolených"
        spa "Demasiadas claves primarias declaradas. Un maximo de %d claves son permitidas"
        swe "För många nycklar använda. Man får ha högst %d nycklar"
        ukr "Забагато ключів зазначено. Дозволено не більше %d ключів"
ER_TOO_MANY_KEY_PARTS 42000 S1009
        cze "Zadáno příliš mnoho část klíčů, je povoleno nejvíce %d částí"
        dan "For mange nøgledele specificeret. Kun %d dele må bruges"
        nla "Teveel zoeksleutel onderdelen gespecificeerd. Maximaal %d onderdelen toegestaan"
        eng "Too many key parts specified; max %d parts allowed"
        est "Võti koosneb liiga paljudest osadest. Maksimaalselt võib olla %d osa"
        fre "Trop de parties specifiées dans la clef. Maximum de %d parties"
        ger "Zu viele Teilschlüssel definiert. Maximal %d Teilschlüssel erlaubt"
        greek "Πάρα πολλά key parts ορίσθηκαν. Το πολύ %d επιτρέπονται"
        hun "Tul sok kulcsdarabot definialt. Maximum %d resz engedelyezett"
        ita "Troppe parti di chiave specificate. Sono ammesse max %d parti"
        jpn "索引のキー列指定が多すぎます。最大 %d 個までです。"
        kor "너무 많은 키 부분(parts)들이 정의되어 있읍니다.. 최대 %d 부분이 가능함"
        nor "For mange nøkkeldeler spesifisert. Maks %d deler tillatt"
        norwegian-ny "For mange nykkeldelar spesifisert. Maks %d delar tillatt"
        pol "Okre?lono zbyt wiele czę?ci klucza. Dostępnych jest maksymalnie %d czę?ci"
        por "Especificadas partes de chave demais. O máximo permitido são %d partes"
        rum "Prea multe chei. Numarul de chei maxim este %d"
        rus "Указано слишком много частей составного ключа. Разрешается указывать не более %d частей"
        serbian "Navedeno je previše delova ključa. Maksimum %d delova je dozvoljeno"
        slo "Zadaných ríliš veľa častí kľúčov. Je povolených najviac %d častí"
        spa "Demasiadas partes de clave declaradas. Un maximo de %d partes son permitidas"
        swe "För många nyckeldelar använda. Man får ha högst %d nyckeldelar"
        ukr "Забагато частин ключа зазначено. Дозволено не більше %d частин"
ER_TOO_LONG_KEY 42000 S1009
        cze "Zadaný klíč byl příliš dlouhý, největší délka klíče je %d"
        dan "Specificeret nøgle var for lang. Maksimal nøglelængde er %d"
        nla "Gespecificeerde zoeksleutel was te lang. De maximale lengte is %d"
        eng "Specified key was too long; max key length is %d bytes"
        est "Võti on liiga pikk. Maksimaalne võtmepikkus on %d"
        fre "La clé est trop longue. Longueur maximale: %d"
        ger "Schlüssel ist zu lang. Die maximale Schlüssellänge beträgt %d"
        greek "Το κλειδί που ορίσθηκε είναι πολύ μεγάλο. Το μέγιστο μήκος είναι %d"
        hun "A megadott kulcs tul hosszu. Maximalis kulcshosszusag: %d"
        ita "La chiave specificata e` troppo lunga. La max lunghezza della chiave e` %d"
        jpn "索引のキーが長すぎます。最大 %d バイトまでです。"
        kor "정의된 키가 너무 깁니다. 최대 키의 길이는 %d입니다."
        nor "Spesifisert nøkkel var for lang. Maks nøkkellengde er is %d"
        norwegian-ny "Spesifisert nykkel var for lang. Maks nykkellengde er %d"
        pol "Zdefinowany klucz jest zbyt długi. Maksymaln? długo?ci? klucza jest %d"
        por "Chave especificada longa demais. O comprimento de chave máximo permitido é %d"
        rum "Cheia specificata este prea lunga. Marimea maxima a unei chei este de %d"
        rus "Указан слишком длинный ключ. Максимальная длина ключа составляет %d байт"
        serbian "Navedeni ključ je predug. Maksimalna dužina ključa je %d"
        slo "Zadaný kľúč je príliš dlhý, najväčšia dĺžka kľúča je %d"
        spa "Declaracion de clave demasiado larga. La maxima longitud de clave es %d"
        swe "För lång nyckel. Högsta tillåtna nyckellängd är %d"
        ukr "Зазначений ключ задовгий. Найбільша довжина ключа %d байтів"
ER_KEY_COLUMN_DOES_NOT_EXITS 42000 S1009
        cze "Klíčový sloupec '%-.192s' v tabulce neexistuje"
        dan "Nøglefeltet '%-.192s' eksisterer ikke i tabellen"
        nla "Zoeksleutel kolom '%-.192s' bestaat niet in tabel"
        eng "Key column '%-.192s' doesn't exist in table"
        est "Võtme tulp '%-.192s' puudub tabelis"
        fre "La clé '%-.192s' n'existe pas dans la table"
        ger "In der Tabelle gibt es kein Schlüsselfeld '%-.192s'"
        greek "Το πεδίο κλειδί '%-.192s' δεν υπάρχει στον πίνακα"
        hun "A(z) '%-.192s'kulcsoszlop nem letezik a tablaban"
        ita "La colonna chiave '%-.192s' non esiste nella tabella"
        jpn "キー列 '%-.192s' は表にありません。"
        kor "Key 칼럼 '%-.192s'는 테이블에 존재하지 않습니다."
        nor "Nøkkel felt '%-.192s' eksiterer ikke i tabellen"
        norwegian-ny "Nykkel kolonne '%-.192s' eksiterar ikkje i tabellen"
        pol "Kolumna '%-.192s' zdefiniowana w kluczu nie istnieje w tabeli"
        por "Coluna chave '%-.192s' não existe na tabela"
        rum "Coloana cheie '%-.192s' nu exista in tabela"
        rus "Ключевой столбец '%-.192s' в таблице не существует"
        serbian "Ključna kolona '%-.192s' ne postoji u tabeli"
        slo "Kľúčový stĺpec '%-.192s' v tabuľke neexistuje"
        spa "La columna clave '%-.192s' no existe en la tabla"
        swe "Nyckelkolumn '%-.192s' finns inte"
        ukr "Ключовий стовбець '%-.192s' не існує у таблиці"
ER_BLOB_USED_AS_KEY 42000 S1009
        cze "Blob sloupec '%-.192s' nemůže být použit jako klíč"
        dan "BLOB feltet '%-.192s' kan ikke bruges ved specifikation af indeks"
        nla "BLOB kolom '%-.192s' kan niet gebruikt worden bij zoeksleutel specificatie"
        eng "BLOB column '%-.192s' can't be used in key specification with the used table type"
        est "BLOB-tüüpi tulpa '%-.192s' ei saa kasutada võtmena"
        fre "Champ BLOB '%-.192s' ne peut être utilisé dans une clé"
        ger "BLOB-Feld '%-.192s' kann beim verwendeten Tabellentyp nicht als Schlüssel verwendet werden"
        greek "Πεδίο τύπου Blob '%-.192s' δεν μπορεί να χρησιμοποιηθεί στον ορισμό ενός κλειδιού (key specification)"
        hun "Blob objektum '%-.192s' nem hasznalhato kulcskent"
        ita "La colonna BLOB '%-.192s' non puo` essere usata nella specifica della chiave"
        jpn "指定されたストレージエンジンでは、BLOB列 '%-.192s' は索引キーにできません。"
        kor "BLOB 칼럼 '%-.192s'는 키 정의에서 사용될 수 없습니다."
        nor "Blob felt '%-.192s' kan ikke brukes ved spesifikasjon av nøkler"
        norwegian-ny "Blob kolonne '%-.192s' kan ikkje brukast ved spesifikasjon av nyklar"
        pol "Kolumna typu Blob '%-.192s' nie może być użyta w specyfikacji klucza"
        por "Coluna BLOB '%-.192s' não pode ser utilizada na especificação de chave para o tipo de tabela usado"
        rum "Coloana de tip BLOB '%-.192s' nu poate fi folosita in specificarea cheii cu tipul de tabla folosit"
        rus "Столбец типа BLOB '%-.192s' не может быть использован как значение ключа в таблице такого типа"
        serbian "BLOB kolona '%-.192s' ne može biti upotrebljena za navođenje ključa sa tipom tabele koji se trenutno koristi"
        slo "Blob pole '%-.192s' nemôže byť použité ako kľúč"
        spa "La columna Blob '%-.192s' no puede ser usada en una declaracion de clave"
        swe "En BLOB '%-.192s' kan inte vara nyckel med den använda tabelltypen"
        ukr "BLOB стовбець '%-.192s' не може бути використаний у визначенні ключа в цьому типі таблиці"
ER_TOO_BIG_FIELDLENGTH 42000 S1009
        cze "Příliš velká délka sloupce '%-.192s' (nejvíce %lu). Použijte BLOB"
        dan "For stor feltlængde for kolonne '%-.192s' (maks = %lu). Brug BLOB i stedet"
        nla "Te grote kolomlengte voor '%-.192s' (max = %lu). Maak hiervoor gebruik van het type BLOB"
        eng "Column length too big for column '%-.192s' (max = %lu); use BLOB or TEXT instead"
        est "Tulba '%-.192s' pikkus on liiga pikk (maksimaalne pikkus: %lu). Kasuta BLOB väljatüüpi"
        fre "Champ '%-.192s' trop long (max = %lu). Utilisez un BLOB"
        ger "Feldlänge für Feld '%-.192s' zu groß (maximal %lu). BLOB- oder TEXT-Spaltentyp verwenden!"
        greek "Πολύ μεγάλο μήκος για το πεδίο '%-.192s' (max = %lu). Παρακαλώ χρησιμοποιείστε τον τύπο BLOB"
        hun "A(z) '%-.192s' oszlop tul hosszu. (maximum = %lu). Hasznaljon BLOB tipust inkabb."
        ita "La colonna '%-.192s' e` troppo grande (max=%lu). Utilizza un BLOB."
        jpn "列 '%-.192s' のサイズ定義が大きすぎます (最大 %lu まで)。代わりに BLOB または TEXT を使用してください。"
        kor "칼럼 '%-.192s'의 칼럼 길이가 너무 깁니다 (최대 = %lu). 대신에 BLOB를 사용하세요."
        nor "For stor nøkkellengde for kolonne '%-.192s' (maks = %lu). Bruk BLOB istedenfor"
        norwegian-ny "For stor nykkellengde for felt '%-.192s' (maks = %lu). Bruk BLOB istadenfor"
        pol "Zbyt duża długo?ć kolumny '%-.192s' (maks. = %lu). W zamian użyj typu BLOB"
        por "Comprimento da coluna '%-.192s' grande demais (max = %lu); use BLOB em seu lugar"
        rum "Lungimea coloanei '%-.192s' este prea lunga (maximum = %lu). Foloseste BLOB mai bine"
        rus "Слишком большая длина столбца '%-.192s' (максимум = %lu). Используйте тип BLOB или TEXT вместо текущего"
        serbian "Previše podataka za kolonu '%-.192s' (maksimum je %lu). Upotrebite BLOB polje"
        slo "Príliš veľká dĺžka pre pole '%-.192s' (maximum = %lu). Použite BLOB"
        spa "Longitud de columna demasiado grande para la columna '%-.192s' (maximo = %lu).Usar BLOB en su lugar"
        swe "För stor kolumnlängd angiven för '%-.192s' (max= %lu). Använd en BLOB instället"
        ukr "Задовга довжина стовбця '%-.192s' (max = %lu). Використайте тип BLOB"
ER_WRONG_AUTO_KEY 42000 S1009
        cze "Můžete mít pouze jedno AUTO pole a to musí být definováno jako klíč"
        dan "Der kan kun specificeres eet AUTO_INCREMENT-felt, og det skal være indekseret"
        nla "Er kan slechts 1 autofield zijn en deze moet als zoeksleutel worden gedefinieerd."
        eng "Incorrect table definition; there can be only one auto column and it must be defined as a key"
        est "Vigane tabelikirjeldus; Tabelis tohib olla üks auto_increment tüüpi tulp ning see peab olema defineeritud võtmena"
        fre "Un seul champ automatique est permis et il doit être indexé"
        ger "Falsche Tabellendefinition. Es darf nur eine AUTO_INCREMENT-Spalte geben, und diese muss als Schlüssel definiert werden"
        greek "Μπορεί να υπάρχει μόνο ένα auto field και πρέπει να έχει ορισθεί σαν key"
        hun "Csak egy auto mezo lehetseges, es azt kulcskent kell definialni."
        ita "Puo` esserci solo un campo AUTO e deve essere definito come chiave"
        jpn "不正な表定義です。AUTO_INCREMENT列は１個までで、索引を定義する必要があります。"
        kor "부정확한 테이블 정의; 테이블은 하나의 auto 칼럼이 존재하고 키로 정의되어져야 합니다."
        nor "Bare ett auto felt kan være definert som nøkkel."
        norwegian-ny "Bare eitt auto felt kan være definert som nøkkel."
        pol "W tabeli może być tylko jedno pole auto i musi ono być zdefiniowane jako klucz"
        por "Definição incorreta de tabela. Somente é permitido um único campo auto-incrementado e ele tem que ser definido como chave"
        rum "Definitia tabelei este incorecta; Nu pot fi mai mult de o singura coloana de tip auto si aceasta trebuie definita ca cheie"
        rus "Некорректное определение таблицы: может существовать только один автоинкрементный столбец, и он должен быть определен как ключ"
        serbian "Pogrešna definicija tabele; U tabeli može postojati samo jedna 'AUTO' kolona i ona mora biti istovremeno definisana kao kolona ključa"
        slo "Môžete mať iba jedno AUTO pole a to musí byť definované ako kľúč"
        spa "Puede ser solamente un campo automatico y este debe ser definido como una clave"
        swe "Det får finnas endast ett AUTO_INCREMENT-fält och detta måste vara en nyckel"
        ukr "Невірне визначення таблиці; Може бути лише один автоматичний стовбець, що повинен бути визначений як ключ"
ER_READY
        cze "%s: připraven na spojení\nVersion: '%s'  socket: '%s'  port: %d"
        dan "%s: klar til tilslutninger\nVersion: '%s'  socket: '%s'  port: %d"
        nla "%s: klaar voor verbindingen\nVersion: '%s'  socket: '%s'  port: %d"
        eng "%s: ready for connections.\nVersion: '%s'  socket: '%s'  port: %d"
        est "%s: ootab ühendusi\nVersion: '%s'  socket: '%s'  port: %d"
        fre "%s: Prêt pour des connexions\nVersion: '%s'  socket: '%s'  port: %d"
        ger "%s: Bereit für Verbindungen.\nVersion: '%s'  Socket: '%s'  Port: %d"
        greek "%s: σε αναμονή συνδέσεων\nVersion: '%s'  socket: '%s'  port: %d"
        hun "%s: kapcsolatra kesz\nVersion: '%s'  socket: '%s'  port: %d"
        ita "%s: Pronto per le connessioni\nVersion: '%s'  socket: '%s'  port: %d"
        jpn "%s: 接続準備完了。\nバージョン: '%s'  socket: '%s'  port: %d"
        kor "%s: 연결 준비중입니다\nVersion: '%s'  socket: '%s'  port: %d"
        nor "%s: klar for tilkoblinger\nVersion: '%s'  socket: '%s'  port: %d"
        norwegian-ny "%s: klar for tilkoblingar\nVersion: '%s'  socket: '%s'  port: %d"
        pol "%s: gotowe do poł?czenia\nVersion: '%s'  socket: '%s'  port: %d"
        por "%s: Pronto para conexões\nVersion: '%s'  socket: '%s'  port: %d"
        rum "%s: sint gata pentru conectii\nVersion: '%s'  socket: '%s'  port: %d"
        rus "%s: Готов принимать соединения.\nВерсия: '%s'  сокет: '%s'  порт: %d"
        serbian "%s: Spreman za konekcije\nVersion: '%s'  socket: '%s'  port: %d"
        slo "%s: pripravený na spojenie\nVersion: '%s'  socket: '%s'  port: %d"
        spa "%s: preparado para conexiones\nVersion: '%s'  socket: '%s'  port: %d"
        swe "%s: klar att ta emot klienter\nVersion: '%s'  socket: '%s'  port: %d"
        ukr "%s: Готовий для з'єднань!\nVersion: '%s'  socket: '%s'  port: %d"
OBSOLETE_ER_NORMAL_SHUTDOWN
        cze "%s: normální ukončení\n"
        dan "%s: Normal nedlukning\n"
        nla "%s: Normaal afgesloten \n"
        eng "%s: Normal shutdown\n"
        est "%s: MySQL lõpetas\n"
        fre "%s: Arrêt normal du serveur\n"
        ger "%s: Normal heruntergefahren\n"
        greek "%s: Φυσιολογική διαδικασία shutdown\n"
        hun "%s: Normal leallitas\n"
        ita "%s: Shutdown normale\n"
        jpn "%s: 通常シャットダウン\n"
        kor "%s: 정상적인 shutdown\n"
        nor "%s: Normal avslutning\n"
        norwegian-ny "%s: Normal nedkopling\n"
        pol "%s: Standardowe zakończenie działania\n"
        por "%s: 'Shutdown' normal\n"
        rum "%s: Terminare normala\n"
        rus "%s: Корректная остановка\n"
        serbian "%s: Normalno gašenje\n"
        slo "%s: normálne ukončenie\n"
        spa "%s: Apagado normal\n"
        swe "%s: Normal avslutning\n"
        ukr "%s: Нормальне завершення\n"
OBSOLETE_ER_GOT_SIGNAL
        cze "%s: přijat signal %d, končím\n"
        dan "%s: Fangede signal %d. Afslutter!!\n"
        nla "%s: Signaal %d. Systeem breekt af!\n"
        eng "%s: Got signal %d. Aborting!\n"
        est "%s: sain signaali %d. Lõpetan!\n"
        fre "%s: Reçu le signal %d. Abandonne!\n"
        ger "%s: Signal %d erhalten. Abbruch!\n"
        greek "%s: Ελήφθη το μήνυμα %d. Η διαδικασία εγκαταλείπεται!\n"
        hun "%s: %d jelzes. Megszakitva!\n"
        ita "%s: Ricevuto segnale %d. Interruzione!\n"
        jpn "%s: シグナル %d を受信しました。強制終了します！\n"
        kor "%s: %d 신호가 들어왔음. 중지!\n"
        nor "%s: Oppdaget signal %d. Avslutter!\n"
        norwegian-ny "%s: Oppdaga signal %d. Avsluttar!\n"
        pol "%s: Otrzymano sygnał %d. Kończenie działania!\n"
        por "%s: Obteve sinal %d. Abortando!\n"
        rum "%s: Semnal %d obtinut. Aborting!\n"
        rus "%s: Получен сигнал %d. Прекращаем!\n"
        serbian "%s: Dobio signal %d. Prekidam!\n"
        slo "%s: prijatý signál %d, ukončenie (Abort)!\n"
        spa "%s: Recibiendo signal %d. Abortando!\n"
        swe "%s: Fick signal %d. Avslutar!\n"
        ukr "%s: Отримано сигнал %d. Перериваюсь!\n"
ER_SHUTDOWN_COMPLETE
        cze "%s: ukončení práce hotovo\n"
        dan "%s: Server lukket\n"
        nla "%s: Afsluiten afgerond\n"
        eng "%s: Shutdown complete\n"
        est "%s: Lõpp\n"
        fre "%s: Arrêt du serveur terminé\n"
        ger "%s: Herunterfahren beendet\n"
        greek "%s: Η διαδικασία Shutdown ολοκληρώθηκε\n"
        hun "%s: A leallitas kesz\n"
        ita "%s: Shutdown completato\n"
        jpn "%s: シャットダウン完了\n"
        kor "%s: Shutdown 이 완료됨!\n"
        nor "%s: Avslutning komplett\n"
        norwegian-ny "%s: Nedkopling komplett\n"
        pol "%s: Zakończenie działania wykonane\n"
        por "%s: 'Shutdown' completo\n"
        rum "%s: Terminare completa\n"
        rus "%s: Остановка завершена\n"
        serbian "%s: Gašenje završeno\n"
        slo "%s: práca ukončená\n"
        spa "%s: Apagado completado\n"
        swe "%s: Avslutning klar\n"
        ukr "%s: Роботу завершено\n"
ER_FORCING_CLOSE 08S01
        cze "%s: násilné uzavření threadu %ld uživatele '%-.48s'\n"
        dan "%s: Forceret nedlukning af tråd: %ld  bruger: '%-.48s'\n"
        nla "%s: Afsluiten afgedwongen van thread %ld  gebruiker: '%-.48s'\n"
        eng "%s: Forcing close of thread %ld  user: '%-.48s'\n"
        est "%s: Sulgen jõuga lõime %ld  kasutaja: '%-.48s'\n"
        fre "%s: Arrêt forcé de la tâche (thread) %ld  utilisateur: '%-.48s'\n"
        ger "%s: Thread %ld zwangsweise beendet. Benutzer: '%-.48s'\n"
        greek "%s: Το thread θα κλείσει %ld  user: '%-.48s'\n"
        hun "%s: A(z) %ld thread kenyszeritett zarasa. Felhasznalo: '%-.48s'\n"
        ita "%s: Forzata la chiusura del thread %ld utente: '%-.48s'\n"
        jpn "%s: スレッド %ld を強制終了します (ユーザー: '%-.48s')\n"
        kor "%s: thread %ld의 강제 종료 user: '%-.48s'\n"
        nor "%s: Påtvinget avslutning av tråd %ld  bruker: '%-.48s'\n"
        norwegian-ny "%s: Påtvinga avslutning av tråd %ld  brukar: '%-.48s'\n"
        pol "%s: Wymuszenie zamknięcia w?tku %ld  użytkownik: '%-.48s'\n"
        por "%s: Forçando finalização da 'thread' %ld - usuário '%-.48s'\n"
        rum "%s: Terminare fortata a thread-ului %ld  utilizatorului: '%-.48s'\n"
        rus "%s: Принудительно закрываем поток %ld  пользователя: '%-.48s'\n"
        serbian "%s: Usiljeno gašenje thread-a %ld koji pripada korisniku: '%-.48s'\n"
        slo "%s: násilné ukončenie vlákna %ld užívateľa '%-.48s'\n"
        spa "%s: Forzando a cerrar el thread %ld  usuario: '%-.48s'\n"
        swe "%s: Stänger av tråd %ld; användare: '%-.48s'\n"
        ukr "%s: Прискорюю закриття гілки %ld користувача: '%-.48s'\n"
ER_IPSOCK_ERROR 08S01
        cze "Nemohu vytvořit IP socket"
        dan "Kan ikke oprette IP socket"
        nla "Kan IP-socket niet openen"
        eng "Can't create IP socket"
        est "Ei suuda luua IP socketit"
        fre "Ne peut créer la connexion IP (socket)"
        ger "Kann IP-Socket nicht erzeugen"
        greek "Δεν είναι δυνατή η δημιουργία IP socket"
        hun "Az IP socket nem hozhato letre"
        ita "Impossibile creare il socket IP"
        jpn "IPソケットを作成できません。"
        kor "IP 소켓을 만들지 못했습니다."
        nor "Kan ikke opprette IP socket"
        norwegian-ny "Kan ikkje opprette IP socket"
        pol "Nie można stworzyć socket'u IP"
        por "Não pode criar o soquete IP"
        rum "Nu pot crea IP socket"
        rus "Невозможно создать IP-сокет"
        serbian "Ne mogu da kreiram IP socket"
        slo "Nemôžem vytvoriť IP socket"
        spa "No puedo crear IP socket"
        swe "Kan inte skapa IP-socket"
        ukr "Не можу створити IP роз'єм"
ER_NO_SUCH_INDEX 42S12 S1009
        cze "Tabulka '%-.192s' nemá index odpovídající CREATE INDEX. Vytvořte tabulku znovu"
        dan "Tabellen '%-.192s' har ikke den nøgle, som blev brugt i CREATE INDEX. Genopret tabellen"
        nla "Tabel '%-.192s' heeft geen INDEX zoals deze gemaakt worden met CREATE INDEX. Maak de tabel opnieuw"
        eng "Table '%-.192s' has no index like the one used in CREATE INDEX; recreate the table"
        est "Tabelil '%-.192s' puuduvad võtmed. Loo tabel uuesti"
        fre "La table '%-.192s' n'a pas d'index comme celle utilisée dans CREATE INDEX. Recréez la table"
        ger "Tabelle '%-.192s' besitzt keinen wie den in CREATE INDEX verwendeten Index. Tabelle neu anlegen"
        greek "Ο πίνακας '%-.192s' δεν έχει ευρετήριο (index) σαν αυτό που χρησιμοποιείτε στην CREATE INDEX. Παρακαλώ, ξαναδημιουργήστε τον πίνακα"
        hun "A(z) '%-.192s' tablahoz nincs meg a CREATE INDEX altal hasznalt index. Alakitsa at a tablat"
        ita "La tabella '%-.192s' non ha nessun indice come quello specificatato dalla CREATE INDEX. Ricrea la tabella"
        jpn "表 '%-.192s' に以前CREATE INDEXで作成された索引がありません。表を作り直してください。"
        kor "테이블 '%-.192s'는 인덱스를 만들지 않았습니다. alter 테이블명령을 이용하여 테이블을 수정하세요..."
        nor "Tabellen '%-.192s' har ingen index som den som er brukt i CREATE INDEX. Gjenopprett tabellen"
        norwegian-ny "Tabellen '%-.192s' har ingen index som den som er brukt i CREATE INDEX. Oprett tabellen på nytt"
        pol "Tabela '%-.192s' nie ma indeksu takiego jak w CREATE INDEX. Stwórz tabelę"
        por "Tabela '%-.192s' não possui um índice como o usado em CREATE INDEX. Recrie a tabela"
        rum "Tabela '%-.192s' nu are un index ca acela folosit in CREATE INDEX. Re-creeaza tabela"
        rus "В таблице '%-.192s' нет такого индекса, как в CREATE INDEX. Создайте таблицу заново"
        serbian "Tabela '%-.192s' nema isti indeks kao onaj upotrebljen pri komandi 'CREATE INDEX'. Napravite tabelu ponovo"
        slo "Tabuľka '%-.192s' nemá index zodpovedajúci CREATE INDEX. Vytvorte tabulku znova"
        spa "La tabla '%-.192s' no tiene indice como el usado en CREATE INDEX. Crea de nuevo la tabla"
        swe "Tabellen '%-.192s' har inget index som motsvarar det angivna i CREATE INDEX. Skapa om tabellen"
        ukr "Таблиця '%-.192s' має індекс, що не співпадає з вказанним у CREATE INDEX. Створіть таблицю знову"
ER_WRONG_FIELD_TERMINATORS 42000 S1009
        cze "Argument separátoru položek nebyl očekáván. Přečtěte si manuál"
        dan "Felt adskiller er ikke som forventet, se dokumentationen"
        nla "De argumenten om velden te scheiden zijn anders dan verwacht. Raadpleeg de handleiding"
        eng "Field separator argument is not what is expected; check the manual"
        est "Väljade eraldaja erineb oodatust. Tutvu kasutajajuhendiga"
        fre "Séparateur de champs inconnu.  Vérifiez dans le manuel"
        ger "Feldbegrenzer-Argument ist nicht in der erwarteten Form. Bitte im Handbuch nachlesen"
        greek "Ο διαχωριστής πεδίων δεν είναι αυτός που αναμενόταν. Παρακαλώ ανατρέξτε στο manual"
        hun "A mezoelvalaszto argumentumok nem egyeznek meg a varttal. Nezze meg a kezikonyvben!"
        ita "L'argomento 'Field separator' non e` quello atteso. Controlla il manuale"
        jpn "フィールド区切り文字が予期せぬ使われ方をしています。マニュアルを確認して下さい。"
        kor "필드 구분자 인수들이 완전하지 않습니다. 메뉴얼을 찾아 보세요."
        nor "Felt skiller argumentene er ikke som forventet, se dokumentasjonen"
        norwegian-ny "Felt skiljer argumenta er ikkje som venta, sjå dokumentasjonen"
        pol "Nie oczekiwano separatora. SprawdĽ podręcznik"
        por "Argumento separador de campos não é o esperado. Cheque o manual"
        rum "Argumentul pentru separatorul de cimpuri este diferit de ce ma asteptam. Verifica manualul"
        rus "Аргумент разделителя полей - не тот, который ожидался. Обращайтесь к документации"
        serbian "Argument separatora polja nije ono što se očekivalo. Proverite uputstvo MySQL server-a"
        slo "Argument oddeľovač polí nezodpovedá požiadavkám. Skontrolujte v manuáli"
        spa "Los separadores de argumentos del campo no son los especificados. Comprueba el manual"
        swe "Fältseparatorerna är vad som förväntades. Kontrollera mot manualen"
        ukr "Хибний розділювач полів. Почитайте документацію"
ER_BLOBS_AND_NO_TERMINATED 42000 S1009
        cze "Není možné použít pevný rowlength s BLOBem. Použijte 'fields terminated by'."
        dan "Man kan ikke bruge faste feltlængder med BLOB. Brug i stedet 'fields terminated by'."
        nla "Bij het gebruik van BLOBs is het niet mogelijk om vaste rijlengte te gebruiken. Maak s.v.p. gebruik van 'fields terminated by'."
        eng "You can't use fixed rowlength with BLOBs; please use 'fields terminated by'"
        est "BLOB-tüüpi väljade olemasolul ei saa kasutada fikseeritud väljapikkust. Vajalik 'fields terminated by' määrang."
        fre "Vous ne pouvez utiliser des lignes de longueur fixe avec des BLOBs. Utiliser 'fields terminated by'."
        ger "Eine feste Zeilenlänge kann für BLOB-Felder nicht verwendet werden. Bitte 'fields terminated by' verwenden"
        greek "Δεν μπορείτε να χρησιμοποιήσετε fixed rowlength σε BLOBs. Παρακαλώ χρησιμοποιείστε 'fields terminated by'."
        hun "Fix hosszusagu BLOB-ok nem hasznalhatok. Hasznalja a 'mezoelvalaszto jelet' ."
        ita "Non possono essere usate righe a lunghezza fissa con i BLOB. Usa 'FIELDS TERMINATED BY'."
        jpn "BLOBには固定長レコードが使用できません。'FIELDS TERMINATED BY'句を使用して下さい。"
        kor "BLOB로는 고정길이의 lowlength를 사용할 수 없습니다. 'fields terminated by'를 사용하세요."
        nor "En kan ikke bruke faste feltlengder med BLOB. Vennlisgt bruk 'fields terminated by'."
        norwegian-ny "Ein kan ikkje bruke faste feltlengder med BLOB. Vennlisgt bruk 'fields terminated by'."
        pol "Nie można użyć stałej długo?ci wiersza z polami typu BLOB. Użyj 'fields terminated by'."
        por "Você não pode usar comprimento de linha fixo com BLOBs. Por favor, use campos com comprimento limitado."
        rum "Nu poti folosi lungime de cimp fix pentru BLOB-uri. Foloseste 'fields terminated by'."
        rus "Фиксированный размер записи с полями типа BLOB использовать нельзя, применяйте 'fields terminated by'"
        serbian "Ne možete koristiti fiksnu veličinu sloga kada imate BLOB polja. Molim koristite 'fields terminated by' opciju."
        slo "Nie je možné použiť fixnú dĺžku s BLOBom. Použite 'fields terminated by'."
        spa "No puedes usar longitudes de filas fijos con BLOBs. Por favor usa 'campos terminados por '."
        swe "Man kan inte använda fast radlängd med blobs. Använd 'fields terminated by'"
        ukr "Не можна використовувати сталу довжину строки з BLOB. Зкористайтеся 'fields terminated by'"
ER_TEXTFILE_NOT_READABLE
        cze "Soubor '%-.128s' musí být v adresáři databáze nebo čitelný pro všechny"
        dan "Filen '%-.128s' skal være i database-folderen og kunne læses af alle"
        nla "Het bestand '%-.128s' dient in de database directory voor the komen of leesbaar voor iedereen te zijn."
        eng "The file '%-.128s' must be in the database directory or be readable by all"
        est "Fail '%-.128s' peab asuma andmebaasi kataloogis või olema kõigile loetav"
        fre "Le fichier '%-.128s' doit être dans le répertoire de la base et lisible par tous"
        ger "Datei '%-.128s' muss im Datenbank-Verzeichnis vorhanden oder lesbar für alle sein"
        greek "Το αρχείο '%-.128s' πρέπει να υπάρχει στο database directory ή να μπορεί να διαβαστεί από όλους"
        hun "A(z) '%-.128s'-nak az adatbazis konyvtarban kell lennie, vagy mindenki szamara olvashatonak"
        ita "Il file '%-.128s' deve essere nella directory del database e deve essere leggibile da tutti"
        jpn "ファイル '%-.128s' はデータベースディレクトリにあるか、全てのユーザーから読める必要があります。"
        kor "'%-.128s' 화일는 데이타베이스 디렉토리에 존재하거나 모두에게 읽기 가능하여야 합니다."
        nor "Filen '%-.128s' må være i database-katalogen for å være lesbar for alle"
        norwegian-ny "Filen '%-.128s' må være i database-katalogen for å være lesbar for alle"
        pol "Plik '%-.128s' musi znajdować sie w katalogu bazy danych lub mieć prawa czytania przez wszystkich"
        por "Arquivo '%-.128s' tem que estar no diretório do banco de dados ou ter leitura possível para todos"
        rum "Fisierul '%-.128s' trebuie sa fie in directorul bazei de data sau trebuie sa poata sa fie citit de catre toata lumea (verifica permisiile)"
        rus "Файл '%-.128s' должен находиться в том же каталоге, что и база данных, или быть общедоступным для чтения"
        serbian "File '%-.128s' mora biti u direktorijumu gde su file-ovi baze i mora imati odgovarajuća prava pristupa"
        slo "Súbor '%-.128s' musí byť v adresári databázy, alebo čitateľný pre všetkých"
        spa "El archivo '%-.128s' debe estar en el directorio de la base de datos o ser de lectura por todos"
        swe "Textfilen '%-.128s' måste finnas i databasbiblioteket eller vara läsbar för alla"
        ukr "Файл '%-.128s' повинен бути у теці бази данних або мати встановлене право на читання для усіх"
ER_FILE_EXISTS_ERROR
        cze "Soubor '%-.200s' již existuje"
        dan "Filen '%-.200s' eksisterer allerede"
        nla "Het bestand '%-.200s' bestaat reeds"
        eng "File '%-.200s' already exists"
        est "Fail '%-.200s' juba eksisteerib"
        fre "Le fichier '%-.200s' existe déjà"
        ger "Datei '%-.200s' bereits vorhanden"
        greek "Το αρχείο '%-.200s' υπάρχει ήδη"
        hun "A '%-.200s' file mar letezik."
        ita "Il file '%-.200s' esiste gia`"
        jpn "ファイル '%-.200s' はすでに存在します。"
        kor "'%-.200s' 화일은 이미 존재합니다."
        nor "Filen '%-.200s' eksisterte allerede"
        norwegian-ny "Filen '%-.200s' eksisterte allereide"
        pol "Plik '%-.200s' już istnieje"
        por "Arquivo '%-.200s' já existe"
        rum "Fisierul '%-.200s' exista deja"
        rus "Файл '%-.200s' уже существует"
        serbian "File '%-.200s' već postoji"
        slo "Súbor '%-.200s' už existuje"
        spa "El archivo '%-.200s' ya existe"
        swe "Filen '%-.200s' existerar redan"
        ukr "Файл '%-.200s' вже існує"
ER_LOAD_INFO
        cze "Záznamů: %ld  Vymazáno: %ld  Přeskočeno: %ld  Varování: %ld"
        dan "Poster: %ld  Fjernet: %ld  Sprunget over: %ld  Advarsler: %ld"
        nla "Records: %ld  Verwijderd: %ld  Overgeslagen: %ld  Waarschuwingen: %ld"
        eng "Records: %ld  Deleted: %ld  Skipped: %ld  Warnings: %ld"
        est "Kirjeid: %ld  Kustutatud: %ld  Vahele jäetud: %ld  Hoiatusi: %ld"
        fre "Enregistrements: %ld  Effacés: %ld  Non traités: %ld  Avertissements: %ld"
        ger "Datensätze: %ld  Gelöscht: %ld  Ausgelassen: %ld  Warnungen: %ld"
        greek "Εγγραφές: %ld  Διαγραφές: %ld  Παρεκάμφθησαν: %ld  Προειδοποιήσεις: %ld"
        hun "Rekordok: %ld  Torolve: %ld  Skipped: %ld  Warnings: %ld"
        ita "Records: %ld  Cancellati: %ld  Saltati: %ld  Avvertimenti: %ld"
        jpn "レコード数: %ld  削除: %ld  スキップ: %ld  警告: %ld"
        kor "레코드: %ld개  삭제: %ld개  스킵: %ld개  경고: %ld개"
        nor "Poster: %ld  Fjernet: %ld  Hoppet over: %ld  Advarsler: %ld"
        norwegian-ny "Poster: %ld  Fjerna: %ld  Hoppa over: %ld  Åtvaringar: %ld"
        pol "Recordów: %ld  Usuniętych: %ld  Pominiętych: %ld  Ostrzeżeń: %ld"
        por "Registros: %ld - Deletados: %ld - Ignorados: %ld - Avisos: %ld"
        rum "Recorduri: %ld  Sterse: %ld  Sarite (skipped): %ld  Atentionari (warnings): %ld"
        rus "Записей: %ld  Удалено: %ld  Пропущено: %ld  Предупреждений: %ld"
        serbian "Slogova: %ld  Izbrisano: %ld  Preskočeno: %ld  Upozorenja: %ld"
        slo "Záznamov: %ld  Zmazaných: %ld  Preskočených: %ld  Varovania: %ld"
        spa "Registros: %ld  Borrados: %ld  Saltados: %ld  Peligros: %ld"
        swe "Rader: %ld  Bortagna: %ld  Dubletter: %ld  Varningar: %ld"
        ukr "Записів: %ld  Видалено: %ld  Пропущено: %ld  Застережень: %ld"
ER_ALTER_INFO
        cze "Záznamů: %ld  Zdvojených: %ld"
        dan "Poster: %ld  Ens: %ld"
        nla "Records: %ld  Dubbel: %ld"
        eng "Records: %ld  Duplicates: %ld"
        est "Kirjeid: %ld  Kattuvaid: %ld"
        fre "Enregistrements: %ld  Doublons: %ld"
        ger "Datensätze: %ld  Duplikate: %ld"
        greek "Εγγραφές: %ld  Επαναλήψεις: %ld"
        hun "Rekordok: %ld  Duplikalva: %ld"
        ita "Records: %ld  Duplicati: %ld"
        jpn "レコード数: %ld  重複: %ld"
        kor "레코드: %ld개  중복: %ld개"
        nor "Poster: %ld  Like: %ld"
        norwegian-ny "Poster: %ld  Like: %ld"
        pol "Rekordów: %ld  Duplikatów: %ld"
        por "Registros: %ld - Duplicados: %ld"
        rum "Recorduri: %ld  Duplicate: %ld"
        rus "Записей: %ld  Дубликатов: %ld"
        serbian "Slogova: %ld  Duplikata: %ld"
        slo "Záznamov: %ld  Opakovaných: %ld"
        spa "Registros: %ld  Duplicados: %ld"
        swe "Rader: %ld  Dubletter: %ld"
        ukr "Записів: %ld  Дублікатів: %ld"
ER_WRONG_SUB_KEY
        cze "Chybná podčást klíče -- není to řetězec nebo je delší než délka části klíče"
        dan "Forkert indeksdel. Den anvendte nøgledel er ikke en streng eller længden er større end nøglelængden"
        nla "Foutief sub-gedeelte van de zoeksleutel. De gebruikte zoeksleutel is geen onderdeel van een string of of de gebruikte lengte is langer dan de zoeksleutel"
        eng "Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys"
        est "Vigane võtme osa. Kasutatud võtmeosa ei ole string tüüpi, määratud pikkus on pikem kui võtmeosa või tabelihandler ei toeta seda tüüpi võtmeid"
        fre "Mauvaise sous-clef. Ce n'est pas un 'string' ou la longueur dépasse celle définie dans la clef"
        ger "Falscher Unterteilschlüssel. Der verwendete Schlüsselteil ist entweder kein String, die verwendete Länge ist länger als der Teilschlüssel oder die Speicher-Engine unterstützt keine Unterteilschlüssel"
        greek "Εσφαλμένο sub part key. Το χρησιμοποιούμενο key part δεν είναι string ή το μήκος του είναι μεγαλύτερο"
        hun "Rossz alkulcs. A hasznalt kulcsresz nem karaktersorozat vagy hosszabb, mint a kulcsresz"
        ita "Sotto-parte della chiave errata. La parte di chiave utilizzata non e` una stringa o la lunghezza e` maggiore della parte di chiave."
        jpn "キーのプレフィックスが不正です。キーが文字列ではないか、プレフィックス長がキーよりも長いか、ストレージエンジンが一意索引のプレフィックス指定をサポートしていません。"
        kor "부정확한 서버 파트 키. 사용된 키 파트가 스트링이 아니거나 키 파트의 길이가 너무 깁니다."
        nor "Feil delnøkkel. Den brukte delnøkkelen er ikke en streng eller den oppgitte lengde er lengre enn nøkkel lengden"
        norwegian-ny "Feil delnykkel. Den brukte delnykkelen er ikkje ein streng eller den oppgitte lengda er lengre enn nykkellengden"
        pol "Błędna podczę?ć klucza. Użyta czę?ć klucza nie jest łańcuchem lub użyta długo?ć  jest większa niż czę?ć klucza"
        por "Sub parte da chave incorreta. A parte da chave usada não é uma 'string' ou o comprimento usado é maior que parte da chave ou o manipulador de tabelas não suporta sub chaves únicas"
        rum "Componentul cheii este incorrect. Componentul folosit al cheii nu este un sir sau lungimea folosita este mai lunga decit lungimea cheii"
        rus "Некорректная часть ключа. Используемая часть ключа не является строкой, указанная длина больше, чем длина части ключа, или обработчик таблицы не поддерживает уникальные части ключа"
        serbian "Pogrešan pod-ključ dela ključa. Upotrebljeni deo ključa nije string, upotrebljena dužina je veća od dela ključa ili handler tabela ne podržava jedinstvene pod-ključeve"
        slo "Incorrect prefix key; the used key part isn't a string or the used length is longer than the key part"
        spa "Parte de la clave es erronea. Una parte de la clave no es una cadena o la longitud usada es tan grande como la parte de la clave"
        swe "Felaktig delnyckel. Nyckeldelen är inte en sträng eller den angivna längden är längre än kolumnlängden"
        ukr "Невірна частина ключа. Використана частина ключа не є строкою, задовга або вказівник таблиці не підтримує унікальних частин ключей"
ER_CANT_REMOVE_ALL_FIELDS 42000
        cze "Není možné vymazat všechny položky s ALTER TABLE. Použijte DROP TABLE"
        dan "Man kan ikke slette alle felter med ALTER TABLE. Brug DROP TABLE i stedet."
        nla "Het is niet mogelijk alle velden te verwijderen met ALTER TABLE. Gebruik a.u.b. DROP TABLE hiervoor!"
        eng "You can't delete all columns with ALTER TABLE; use DROP TABLE instead"
        est "ALTER TABLE kasutades ei saa kustutada kõiki tulpasid. Kustuta tabel DROP TABLE abil"
        fre "Vous ne pouvez effacer tous les champs avec ALTER TABLE. Utilisez DROP TABLE"
        ger "Mit ALTER TABLE können nicht alle Felder auf einmal gelöscht werden. Dafür DROP TABLE verwenden"
        greek "Δεν είναι δυνατή η διαγραφή όλων των πεδίων με ALTER TABLE. Παρακαλώ χρησιμοποιείστε DROP TABLE"
        hun "Az osszes mezo nem torolheto az ALTER TABLE-lel. Hasznalja a DROP TABLE-t helyette"
        ita "Non si possono cancellare tutti i campi con una ALTER TABLE. Utilizzare DROP TABLE"
        jpn "ALTER TABLE では全ての列の削除はできません。DROP TABLE を使用してください。"
        kor "ALTER TABLE 명령으로는 모든 칼럼을 지울 수 없습니다. DROP TABLE 명령을 이용하세요."
        nor "En kan ikke slette alle felt med ALTER TABLE. Bruk DROP TABLE isteden."
        norwegian-ny "Ein kan ikkje slette alle felt med ALTER TABLE. Bruk DROP TABLE istadenfor."
        pol "Nie można usun?ć wszystkich pól wykorzystuj?c ALTER TABLE. W zamian użyj DROP TABLE"
        por "Você não pode deletar todas as colunas com ALTER TABLE; use DROP TABLE em seu lugar"
        rum "Nu poti sterge toate coloanele cu ALTER TABLE. Foloseste DROP TABLE in schimb"
        rus "Нельзя удалить все столбцы с помощью ALTER TABLE. Используйте  DROP TABLE"
        serbian "Ne možete da izbrišete sve kolone pomoću komande 'ALTER TABLE'. Upotrebite komandu 'DROP TABLE' ako želite to da uradite"
        slo "One nemôžem zmazať all fields with ALTER TABLE; use DROP TABLE instead"
        spa "No puede borrar todos los campos con ALTER TABLE. Usa DROP TABLE para hacerlo"
        swe "Man kan inte radera alla fält med ALTER TABLE. Använd DROP TABLE istället"
        ukr "Не можливо видалити всі стовбці за допомогою ALTER TABLE. Для цього скористайтеся DROP TABLE"
ER_CANT_DROP_FIELD_OR_KEY 42000
        cze "Nemohu zrušit '%-.192s' (provést DROP). Zkontrolujte, zda neexistují záznamy/klíče"
        dan "Kan ikke udføre DROP '%-.192s'. Undersøg om feltet/nøglen eksisterer."
        nla "Kan '%-.192s' niet weggooien. Controleer of het veld of de zoeksleutel daadwerkelijk bestaat."
        eng "Can't DROP '%-.192s'; check that column/key exists"
        est "Ei suuda kustutada '%-.192s'. Kontrolli kas tulp/võti eksisteerib"
        fre "Ne peut effacer (DROP) '%-.192s'. Vérifiez s'il existe"
        ger "Kann '%-.192s' nicht löschen. Existiert die Spalte oder der Schlüssel?"
        greek "Αδύνατη η διαγραφή (DROP) '%-.192s'. Παρακαλώ ελέγξτε αν το πεδίο/κλειδί υπάρχει"
        hun "A DROP '%-.192s' nem lehetseges. Ellenorizze, hogy a mezo/kulcs letezik-e"
        ita "Impossibile cancellare '%-.192s'. Controllare che il campo chiave esista"
        jpn "'%-.192s' を削除できません。列／索引の存在を確認して下さい。"
        kor "'%-.192s'를 DROP할 수 없습니다. 칼럼이나 키가 존재하는지 채크하세요."
        nor "Kan ikke DROP '%-.192s'. Undersøk om felt/nøkkel eksisterer."
        norwegian-ny "Kan ikkje DROP '%-.192s'. Undersøk om felt/nøkkel eksisterar."
        pol "Nie można wykonać operacji DROP '%-.192s'. SprawdĽ, czy to pole/klucz istnieje"
        por "Não se pode fazer DROP '%-.192s'. Confira se esta coluna/chave existe"
        rum "Nu pot sa DROP '%-.192s'. Verifica daca coloana/cheia exista"
        rus "Невозможно удалить (DROP) '%-.192s'. Убедитесь что столбец/ключ действительно существует"
        serbian "Ne mogu da izvršim komandu drop 'DROP' na '%-.192s'. Proverite da li ta kolona (odnosno ključ) postoji"
        slo "Nemôžem zrušiť (DROP) '%-.192s'. Skontrolujte, či neexistujú záznamy/kľúče"
        spa "No puedo ELIMINAR '%-.192s'. compuebe que el campo/clave existe"
        swe "Kan inte ta bort '%-.192s'. Kontrollera att fältet/nyckel finns"
        ukr "Не можу DROP '%-.192s'. Перевірте, чи цей стовбець/ключ існує"
ER_INSERT_INFO
        cze "Záznamů: %ld  Zdvojených: %ld  Varování: %ld"
        dan "Poster: %ld  Ens: %ld  Advarsler: %ld"
        nla "Records: %ld  Dubbel: %ld  Waarschuwing: %ld"
        eng "Records: %ld  Duplicates: %ld  Warnings: %ld"
        est "Kirjeid: %ld  Kattuvaid: %ld  Hoiatusi: %ld"
        fre "Enregistrements: %ld  Doublons: %ld  Avertissements: %ld"
        ger "Datensätze: %ld  Duplikate: %ld  Warnungen: %ld"
        greek "Εγγραφές: %ld  Επαναλήψεις: %ld  Προειδοποιήσεις: %ld"
        hun "Rekordok: %ld  Duplikalva: %ld  Warnings: %ld"
        ita "Records: %ld  Duplicati: %ld  Avvertimenti: %ld"
        jpn "レコード数: %ld  重複数: %ld  警告: %ld"
        kor "레코드: %ld개  중복: %ld개  경고: %ld개"
        nor "Poster: %ld  Like: %ld  Advarsler: %ld"
        norwegian-ny "Postar: %ld  Like: %ld  Åtvaringar: %ld"
        pol "Rekordów: %ld  Duplikatów: %ld  Ostrzeżeń: %ld"
        por "Registros: %ld - Duplicados: %ld - Avisos: %ld"
        rum "Recorduri: %ld  Duplicate: %ld  Atentionari (warnings): %ld"
        rus "Записей: %ld  Дубликатов: %ld  Предупреждений: %ld"
        serbian "Slogova: %ld  Duplikata: %ld  Upozorenja: %ld"
        slo "Záznamov: %ld  Opakovaných: %ld  Varovania: %ld"
        spa "Registros: %ld  Duplicados: %ld  Peligros: %ld"
        swe "Rader: %ld  Dubletter: %ld  Varningar: %ld"
        ukr "Записів: %ld  Дублікатів: %ld  Застережень: %ld"
ER_UPDATE_TABLE_USED
        eng "You can't specify target table '%-.192s' for update in FROM clause"
        ger "Die Verwendung der zu aktualisierenden Zieltabelle '%-.192s' ist in der FROM-Klausel nicht zulässig."
        jpn "FROM句にある表 '%-.192s' はUPDATEの対象にできません。"
        rus "Не допускается указание таблицы '%-.192s' в списке таблиц FROM для внесения в нее изменений"
        swe "INSERT-table '%-.192s' får inte finnas i FROM tabell-listan"
        ukr "Таблиця '%-.192s' що змінюється не дозволена у переліку таблиць FROM"
ER_NO_SUCH_THREAD
        cze "Neznámá identifikace threadu: %lu"
        dan "Ukendt tråd id: %lu"
        nla "Onbekend thread id: %lu"
        eng "Unknown thread id: %lu"
        est "Tundmatu lõim: %lu"
        fre "Numéro de tâche inconnu: %lu"
        ger "Unbekannte Thread-ID: %lu"
        greek "Αγνωστο thread id: %lu"
        hun "Ervenytelen szal (thread) id: %lu"
        ita "Thread id: %lu sconosciuto"
        jpn "不明なスレッドIDです: %lu"
        kor "알수 없는 쓰레드 id: %lu"
        nor "Ukjent tråd id: %lu"
        norwegian-ny "Ukjent tråd id: %lu"
        pol "Nieznany identyfikator w?tku: %lu"
        por "'Id' de 'thread' %lu desconhecido"
        rum "Id-ul: %lu thread-ului este necunoscut"
        rus "Неизвестный номер потока: %lu"
        serbian "Nepoznat thread identifikator: %lu"
        slo "Neznáma identifikácia vlákna: %lu"
        spa "Identificador del thread: %lu  desconocido"
        swe "Finns ingen tråd med id %lu"
        ukr "Невідомий ідентифікатор гілки: %lu"
ER_KILL_DENIED_ERROR
        cze "Nejste vlastníkem threadu %lu"
        dan "Du er ikke ejer af tråden %lu"
        nla "U bent geen bezitter van thread %lu"
        eng "You are not owner of thread %lu"
        est "Ei ole lõime %lu omanik"
        fre "Vous n'êtes pas propriétaire de la tâche no: %lu"
        ger "Sie sind nicht Eigentümer von Thread %lu"
        greek "Δεν είσθε owner του thread %lu"
        hun "A %lu thread-nek mas a tulajdonosa"
        ita "Utente non proprietario del thread %lu"
        jpn "スレッド %lu のオーナーではありません。"
        kor "쓰레드(Thread) %lu의 소유자가 아닙니다."
        nor "Du er ikke eier av tråden %lu"
        norwegian-ny "Du er ikkje eigar av tråd %lu"
        pol "Nie jeste? wła?cicielem w?tku %lu"
        por "Você não é proprietário da 'thread' %lu"
        rum "Nu sinteti proprietarul threadului %lu"
        rus "Вы не являетесь владельцем потока %lu"
        serbian "Vi niste vlasnik thread-a %lu"
        slo "Nie ste vlastníkom vlákna %lu"
        spa "Tu no eres el propietario del thread%lu"
        swe "Du är inte ägare till tråd %lu"
        ukr "Ви не володар гілки %lu"
ER_NO_TABLES_USED
        cze "Nejsou použity žádné tabulky"
        dan "Ingen tabeller i brug"
        nla "Geen tabellen gebruikt."
        eng "No tables used"
        est "Ühtegi tabelit pole kasutusel"
        fre "Aucune table utilisée"
        ger "Keine Tabellen verwendet"
        greek "Δεν χρησιμοποιήθηκαν πίνακες"
        hun "Nincs hasznalt tabla"
        ita "Nessuna tabella usata"
        jpn "表が指定されていません。"
        kor "어떤 테이블도 사용되지 않았습니다."
        nor "Ingen tabeller i bruk"
        norwegian-ny "Ingen tabellar i bruk"
        pol "Nie ma żadej użytej tabeli"
        por "Nenhuma tabela usada"
        rum "Nici o tabela folosita"
        rus "Никакие таблицы не использованы"
        serbian "Nema upotrebljenih tabela"
        slo "Nie je použitá žiadna tabuľka"
        spa "No ha tablas usadas"
        swe "Inga tabeller angivna"
        ukr "Не використано таблиць"
ER_TOO_BIG_SET
        cze "Příliš mnoho řetězců pro sloupec %-.192s a SET"
        dan "For mange tekststrenge til specifikationen af SET i kolonne %-.192s"
        nla "Teveel strings voor kolom %-.192s en SET"
        eng "Too many strings for column %-.192s and SET"
        est "Liiga palju string tulbale %-.192s tüübile SET"
        fre "Trop de chaînes dans la colonne %-.192s avec SET"
        ger "Zu viele Strings für Feld %-.192s und SET angegeben"
        greek "Πάρα πολλά strings για το πεδίο %-.192s και SET"
        hun "Tul sok karakter: %-.192s es SET"
        ita "Troppe stringhe per la colonna %-.192s e la SET"
        jpn "SET型の列 '%-.192s' のメンバーの数が多すぎます。"
        kor "칼럼 %-.192s와 SET에서 스트링이 너무 많습니다."
        nor "For mange tekststrenger kolonne %-.192s og SET"
        norwegian-ny "For mange tekststrengar felt %-.192s og SET"
        pol "Zbyt wiele łańcuchów dla kolumny %-.192s i polecenia SET"
        por "'Strings' demais para coluna '%-.192s' e SET"
        rum "Prea multe siruri pentru coloana %-.192s si SET"
        rus "Слишком много значений для столбца %-.192s в SET"
        serbian "Previše string-ova za kolonu '%-.192s' i komandu 'SET'"
        slo "Príliš mnoho reťazcov pre pole %-.192s a SET"
        spa "Muchas strings para columna %-.192s y SET"
        swe "För många alternativ till kolumn %-.192s för SET"
        ukr "Забагато строк для стовбця %-.192s та SET"
ER_NO_UNIQUE_LOGFILE
        cze "Nemohu vytvořit jednoznačné jméno logovacího souboru %-.200s.(1-999)\n"
        dan "Kan ikke lave unikt log-filnavn %-.200s.(1-999)\n"
        nla "Het is niet mogelijk een unieke naam te maken voor de logfile %-.200s.(1-999)\n"
        eng "Can't generate a unique log-filename %-.200s.(1-999)\n"
        est "Ei suuda luua unikaalset logifaili nime %-.200s.(1-999)\n"
        fre "Ne peut générer un unique nom de journal %-.200s.(1-999)\n"
        ger "Kann keinen eindeutigen Dateinamen für die Logdatei %-.200s(1-999) erzeugen\n"
        greek "Αδύνατη η δημιουργία unique log-filename %-.200s.(1-999)\n"
        hun "Egyedi log-filenev nem generalhato: %-.200s.(1-999)\n"
        ita "Impossibile generare un nome del file log unico %-.200s.(1-999)\n"
        jpn "一意なログファイル名 %-.200s.(1-999) を生成できません。\n"
        kor "Unique 로그화일 '%-.200s'를 만들수 없습니다.(1-999)\n"
        nor "Kan ikke lage unikt loggfilnavn %-.200s.(1-999)\n"
        norwegian-ny "Kan ikkje lage unikt loggfilnavn %-.200s.(1-999)\n"
        pol "Nie można stworzyć unikalnej nazwy pliku z logiem %-.200s.(1-999)\n"
        por "Não pode gerar um nome de arquivo de 'log' único '%-.200s'.(1-999)\n"
        rum "Nu pot sa generez un nume de log unic %-.200s.(1-999)\n"
        rus "Невозможно создать уникальное имя файла журнала %-.200s.(1-999)\n"
        serbian "Ne mogu da generišem jedinstveno ime log-file-a: '%-.200s.(1-999)'\n"
        slo "Nemôžem vytvoriť unikátne meno log-súboru %-.200s.(1-999)\n"
        spa "No puede crear un unico archivo log %-.200s.(1-999)\n"
        swe "Kan inte generera ett unikt filnamn %-.200s.(1-999)\n"
        ukr "Не можу згенерувати унікальне ім'я log-файлу %-.200s.(1-999)\n"
ER_TABLE_NOT_LOCKED_FOR_WRITE
        cze "Tabulka '%-.192s' byla zamčena s READ a nemůže být změněna"
        dan "Tabellen '%-.192s' var låst med READ lås og kan ikke opdateres"
        nla "Tabel '%-.192s' was gelocked met een lock om te lezen. Derhalve kunnen geen wijzigingen worden opgeslagen."
        eng "Table '%-.192s' was locked with a READ lock and can't be updated"
        est "Tabel '%-.192s' on lukustatud READ lukuga ning ei ole muudetav"
        fre "Table '%-.192s' verrouillée lecture (READ): modification impossible"
        ger "Tabelle '%-.192s' ist mit Lesesperre versehen und kann nicht aktualisiert werden"
        greek "Ο πίνακας '%-.192s' έχει κλειδωθεί με READ lock και δεν επιτρέπονται αλλαγές"
        hun "A(z) '%-.192s' tabla zarolva lett (READ lock) es nem lehet frissiteni"
        ita "La tabella '%-.192s' e` soggetta a lock in lettura e non puo` essere aggiornata"
        jpn "表 '%-.192s' はREADロックされていて、更新できません。"
        kor "테이블 '%-.192s'는 READ 락이 잠겨있어서 갱신할 수 없습니다."
        nor "Tabellen '%-.192s' var låst med READ lås og kan ikke oppdateres"
        norwegian-ny "Tabellen '%-.192s' var låst med READ lås og kan ikkje oppdaterast"
        pol "Tabela '%-.192s' została zablokowana przez READ i nie może zostać zaktualizowana"
        por "Tabela '%-.192s' foi travada com trava de leitura e não pode ser atualizada"
        rum "Tabela '%-.192s' a fost locked cu un READ lock si nu poate fi actualizata"
        rus "Таблица '%-.192s' заблокирована уровнем READ lock и не может быть изменена"
        serbian "Tabela '%-.192s' je zaključana READ lock-om; iz nje se može samo čitati ali u nju se ne može pisati"
        slo "Tabuľka '%-.192s' bola zamknutá s READ a nemôže byť zmenená"
        spa "Tabla '%-.192s' fue trabada con un READ lock y no puede ser actualizada"
        swe "Tabell '%-.192s' kan inte uppdateras emedan den är låst för läsning"
        ukr "Таблицю '%-.192s' заблоковано тільки для читання, тому її не можна оновити"
ER_TABLE_NOT_LOCKED
        cze "Tabulka '%-.192s' nebyla zamčena s LOCK TABLES"
        dan "Tabellen '%-.192s' var ikke låst med LOCK TABLES"
        nla "Tabel '%-.192s' was niet gelocked met LOCK TABLES"
        eng "Table '%-.192s' was not locked with LOCK TABLES"
        est "Tabel '%-.192s' ei ole lukustatud käsuga LOCK TABLES"
        fre "Table '%-.192s' non verrouillée: utilisez LOCK TABLES"
        ger "Tabelle '%-.192s' wurde nicht mit LOCK TABLES gesperrt"
        greek "Ο πίνακας '%-.192s' δεν έχει κλειδωθεί με LOCK TABLES"
        hun "A(z) '%-.192s' tabla nincs zarolva a LOCK TABLES-szel"
        ita "Non e` stato impostato il lock per la tabella '%-.192s' con LOCK TABLES"
        jpn "表 '%-.192s' は LOCK TABLES でロックされていません。"
        kor "테이블 '%-.192s'는 LOCK TABLES 명령으로 잠기지 않았습니다."
        nor "Tabellen '%-.192s' var ikke låst med LOCK TABLES"
        norwegian-ny "Tabellen '%-.192s' var ikkje låst med LOCK TABLES"
        pol "Tabela '%-.192s' nie została zablokowana poleceniem LOCK TABLES"
        por "Tabela '%-.192s' não foi travada com LOCK TABLES"
        rum "Tabela '%-.192s' nu a fost locked cu LOCK TABLES"
        rus "Таблица '%-.192s' не была заблокирована с помощью LOCK TABLES"
        serbian "Tabela '%-.192s' nije bila zaključana komandom 'LOCK TABLES'"
        slo "Tabuľka '%-.192s' nebola zamknutá s LOCK TABLES"
        spa "Tabla '%-.192s' no fue trabada con LOCK TABLES"
        swe "Tabell '%-.192s' är inte låst med LOCK TABLES"
        ukr "Таблицю '%-.192s' не було блоковано з LOCK TABLES"
ER_BLOB_CANT_HAVE_DEFAULT 42000
        cze "Blob položka '%-.192s' nemůže mít defaultní hodnotu"
        dan "BLOB feltet '%-.192s' kan ikke have en standard værdi"
        nla "Blob veld '%-.192s' can geen standaardwaarde bevatten"
        eng "BLOB, TEXT, GEOMETRY or JSON column '%-.192s' can't have a default value"
        est "BLOB-tüüpi tulp '%-.192s' ei saa omada vaikeväärtust"
        fre "BLOB '%-.192s' ne peut avoir de valeur par défaut"
        ger "BLOB/TEXT-Feld '%-.192s' darf keinen Vorgabewert (DEFAULT) haben"
        greek "Τα Blob πεδία '%-.192s' δεν μπορούν να έχουν προκαθορισμένες τιμές (default value)"
        hun "A(z) '%-.192s' blob objektumnak nem lehet alapertelmezett erteke"
        ita "Il campo BLOB '%-.192s' non puo` avere un valore di default"
        jpn "BLOB/TEXT 列 '%-.192s' にはデフォルト値を指定できません。"
        kor "BLOB 칼럼 '%-.192s' 는 디폴트 값을 가질 수 없습니다."
        nor "Blob feltet '%-.192s' kan ikke ha en standard verdi"
        norwegian-ny "Blob feltet '%-.192s' kan ikkje ha ein standard verdi"
        pol "Pole typu blob '%-.192s' nie może mieć domy?lnej warto?ci"
        por "Coluna BLOB '%-.192s' não pode ter um valor padrão (default)"
        rum "Coloana BLOB '%-.192s' nu poate avea o valoare default"
        rus "Невозможно указывать значение по умолчанию для столбца BLOB '%-.192s'"
        serbian "BLOB kolona '%-.192s' ne može imati default vrednost"
        slo "Pole BLOB '%-.192s' nemôže mať implicitnú hodnotu"
        spa "Campo Blob '%-.192s' no puede tener valores patron"
        swe "BLOB fält '%-.192s' kan inte ha ett DEFAULT-värde"
        ukr "Стовбець BLOB '%-.192s' не може мати значення по замовчуванню"
ER_WRONG_DB_NAME 42000
        cze "Nepřípustné jméno databáze '%-.100s'"
        dan "Ugyldigt database navn '%-.100s'"
        nla "Databasenaam '%-.100s' is niet getoegestaan"
        eng "Incorrect database name '%-.100s'"
        est "Vigane andmebaasi nimi '%-.100s'"
        fre "Nom de base de donnée illégal: '%-.100s'"
        ger "Unerlaubter Datenbankname '%-.100s'"
        greek "Λάθος όνομα βάσης δεδομένων '%-.100s'"
        hun "Hibas adatbazisnev: '%-.100s'"
        ita "Nome database errato '%-.100s'"
        jpn "データベース名 '%-.100s' は不正です。"
        kor "'%-.100s' 데이타베이스의 이름이 부정확합니다."
        nor "Ugyldig database navn '%-.100s'"
        norwegian-ny "Ugyldig database namn '%-.100s'"
        pol "Niedozwolona nazwa bazy danych '%-.100s'"
        por "Nome de banco de dados '%-.100s' incorreto"
        rum "Numele bazei de date este incorect '%-.100s'"
        rus "Некорректное имя базы данных '%-.100s'"
        serbian "Pogrešno ime baze '%-.100s'"
        slo "Neprípustné meno databázy '%-.100s'"
        spa "Nombre de base de datos ilegal '%-.100s'"
        swe "Felaktigt databasnamn '%-.100s'"
        ukr "Невірне ім'я бази данних '%-.100s'"
ER_WRONG_TABLE_NAME 42000
        cze "Nepřípustné jméno tabulky '%-.100s'"
        dan "Ugyldigt tabel navn '%-.100s'"
        nla "Niet toegestane tabelnaam '%-.100s'"
        eng "Incorrect table name '%-.100s'"
        est "Vigane tabeli nimi '%-.100s'"
        fre "Nom de table illégal: '%-.100s'"
        ger "Unerlaubter Tabellenname '%-.100s'"
        greek "Λάθος όνομα πίνακα '%-.100s'"
        hun "Hibas tablanev: '%-.100s'"
        ita "Nome tabella errato '%-.100s'"
        jpn "表名 '%-.100s' は不正です。"
        kor "'%-.100s' 테이블 이름이 부정확합니다."
        nor "Ugyldig tabell navn '%-.100s'"
        norwegian-ny "Ugyldig tabell namn '%-.100s'"
        pol "Niedozwolona nazwa tabeli '%-.100s'..."
        por "Nome de tabela '%-.100s' incorreto"
        rum "Numele tabelei este incorect '%-.100s'"
        rus "Некорректное имя таблицы '%-.100s'"
        serbian "Pogrešno ime tabele '%-.100s'"
        slo "Neprípustné meno tabuľky '%-.100s'"
        spa "Nombre de tabla ilegal '%-.100s'"
        swe "Felaktigt tabellnamn '%-.100s'"
        ukr "Невірне ім'я таблиці '%-.100s'"
ER_TOO_BIG_SELECT 42000
        cze "Zadaný SELECT by procházel příliš mnoho záznamů a trval velmi dlouho. Zkontrolujte tvar WHERE a je-li SELECT v pořádku, použijte SET SQL_BIG_SELECTS=1"
        dan "SELECT ville undersøge for mange poster og ville sandsynligvis tage meget lang tid. Undersøg WHERE delen og brug SET SQL_BIG_SELECTS=1 hvis udtrykket er korrekt"
        nla "Het SELECT-statement zou te veel records analyseren en dus veel tijd in beslagnemen. Kijk het WHERE-gedeelte van de query na en kies SET SQL_BIG_SELECTS=1 als het stament in orde is."
        eng "The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay"
        est "SELECT lause peab läbi vaatama suure hulga kirjeid ja võtaks tõenäoliselt liiga kaua aega. Tasub kontrollida WHERE klauslit ja vajadusel kasutada käsku SET SQL_BIG_SELECTS=1"
        fre "SELECT va devoir examiner beaucoup d'enregistrements ce qui va prendre du temps. Vérifiez la clause WHERE et utilisez SET SQL_BIG_SELECTS=1 si SELECT se passe bien"
        ger "Die Ausführung des SELECT würde zu viele Datensätze untersuchen und wahrscheinlich sehr lange dauern. Bitte WHERE-Klausel überprüfen und gegebenenfalls SET SQL_BIG_SELECTS=1 oder SET MAX_JOIN_SIZE=# verwenden"
        greek "Το SELECT θα εξετάσει μεγάλο αριθμό εγγραφών και πιθανώς θα καθυστερήσει. Παρακαλώ εξετάστε τις παραμέτρους του WHERE και χρησιμοποιείστε SET SQL_BIG_SELECTS=1 αν το SELECT είναι σωστό"
        hun "A SELECT tul sok rekordot fog megvizsgalni es nagyon sokaig fog tartani. Ellenorizze a WHERE-t es hasznalja a SET SQL_BIG_SELECTS=1 beallitast, ha a SELECT okay"
        ita "La SELECT dovrebbe esaminare troppi record e usare troppo tempo. Controllare la WHERE e usa SET SQL_BIG_SELECTS=1 se e` tutto a posto."
        jpn "SELECTがMAX_JOIN_SIZEを超える行数を処理しました。WHERE句を確認し、SELECT文に問題がなければ、 SET SQL_BIG_SELECTS=1 または SET MAX_JOIN_SIZE=# を使用して下さい。"
        kor "SELECT 명령에서 너무 많은 레코드를 찾기 때문에 많은 시간이 소요됩니다. 따라서 WHERE 문을 점검하거나, 만약 SELECT가 ok되면  SET SQL_BIG_SELECTS=1 옵션을 사용하세요."
        nor "SELECT ville undersøke for mange poster og ville sannsynligvis ta veldig lang tid. Undersøk WHERE klausulen og bruk SET SQL_BIG_SELECTS=1 om SELECTen er korrekt"
        norwegian-ny "SELECT ville undersøkje for mange postar og ville sannsynligvis ta veldig lang tid. Undersøk WHERE klausulen og bruk SET SQL_BIG_SELECTS=1 om SELECTen er korrekt"
        pol "Operacja SELECT będzie dotyczyła zbyt wielu rekordów i prawdopodobnie zajmie bardzo dużo czasu. SprawdĽ warunek WHERE i użyj SQL_OPTION BIG_SELECTS=1 je?li operacja SELECT jest poprawna"
        por "O SELECT examinaria registros demais e provavelmente levaria muito tempo. Cheque sua cláusula WHERE e use SET SQL_BIG_SELECTS=1, se o SELECT estiver correto"
        rum "SELECT-ul ar examina prea multe cimpuri si probabil ar lua prea mult timp; verifica clauza WHERE si foloseste SET SQL_BIG_SELECTS=1 daca SELECT-ul e okay"
        rus "Для такой выборки SELECT должен будет просмотреть слишком много записей и, видимо, это займет очень много времени. Проверьте ваше указание WHERE, и, если в нем все в порядке, укажите SET SQL_BIG_SELECTS=1"
        serbian "Komanda 'SELECT' će ispitati previše slogova i potrošiti previše vremena. Proverite vaš 'WHERE' filter i upotrebite 'SET OPTION SQL_BIG_SELECTS=1' ako želite baš ovakvu komandu"
        slo "Zadaná požiadavka SELECT by prechádzala príliš mnoho záznamov a trvala by príliš dlho. Skontrolujte tvar WHERE a ak je v poriadku, použite SET SQL_BIG_SELECTS=1"
        spa "El SELECT puede examinar muchos registros y probablemente con mucho tiempo. Verifique tu WHERE y usa SET SQL_BIG_SELECTS=1 si el SELECT esta correcto"
        swe "Den angivna frågan skulle läsa mer än MAX_JOIN_SIZE rader.  Kontrollera din WHERE och använd SET SQL_BIG_SELECTS=1 eller SET MAX_JOIN_SIZE=# ifall du vill hantera stora joins"
        ukr "Запиту SELECT потрібно обробити багато записів, що, певне, займе дуже багато часу. Перевірте ваше WHERE та використовуйте SET SQL_BIG_SELECTS=1, якщо цей запит SELECT є вірним"
ER_UNKNOWN_ERROR
        cze "Neznámá chyba"
        dan "Ukendt fejl"
        nla "Onbekende Fout"
        eng "Unknown error"
        est "Tundmatu viga"
        fre "Erreur inconnue"
        ger "Unbekannter Fehler"
        greek "Προέκυψε άγνωστο λάθος"
        hun "Ismeretlen hiba"
        ita "Errore sconosciuto"
        jpn "不明なエラー"
        kor "알수 없는 에러입니다."
        nor "Ukjent feil"
        norwegian-ny "Ukjend feil"
        por "Erro desconhecido"
        rum "Eroare unknown"
        rus "Неизвестная ошибка"
        serbian "Nepoznata greška"
        slo "Neznámá chyba"
        spa "Error desconocido"
        swe "Okänt fel"
        ukr "Невідома помилка"
ER_UNKNOWN_PROCEDURE 42000
        cze "Neznámá procedura %-.192s"
        dan "Ukendt procedure %-.192s"
        nla "Onbekende procedure %-.192s"
        eng "Unknown procedure '%-.192s'"
        est "Tundmatu protseduur '%-.192s'"
        fre "Procédure %-.192s inconnue"
        ger "Unbekannte Prozedur '%-.192s'"
        greek "Αγνωστη διαδικασία '%-.192s'"
        hun "Ismeretlen eljaras: '%-.192s'"
        ita "Procedura '%-.192s' sconosciuta"
        jpn "'%-.192s' は不明なプロシージャです。"
        kor "알수 없는 수행문 : '%-.192s'"
        nor "Ukjent prosedyre %-.192s"
        norwegian-ny "Ukjend prosedyre %-.192s"
        pol "Unkown procedure %-.192s"
        por "'Procedure' '%-.192s' desconhecida"
        rum "Procedura unknown '%-.192s'"
        rus "Неизвестная процедура '%-.192s'"
        serbian "Nepoznata procedura '%-.192s'"
        slo "Neznámá procedúra '%-.192s'"
        spa "Procedimiento desconocido %-.192s"
        swe "Okänd procedur: %-.192s"
        ukr "Невідома процедура '%-.192s'"
ER_WRONG_PARAMCOUNT_TO_PROCEDURE 42000
        cze "Chybný počet parametrů procedury %-.192s"
        dan "Forkert antal  parametre til proceduren %-.192s"
        nla "Foutief aantal parameters doorgegeven aan procedure %-.192s"
        eng "Incorrect parameter count to procedure '%-.192s'"
        est "Vale parameetrite hulk protseduurile '%-.192s'"
        fre "Mauvais nombre de paramètres pour la procedure %-.192s"
        ger "Falsche Parameterzahl für Prozedur '%-.192s'"
        greek "Λάθος αριθμός παραμέτρων στη διαδικασία '%-.192s'"
        hun "Rossz parameter a(z) '%-.192s'eljaras szamitasanal"
        ita "Numero di parametri errato per la procedura '%-.192s'"
        jpn "プロシージャ '%-.192s' へのパラメータ数が不正です。"
        kor "'%-.192s' 수행문에 대한 부정확한 파라메터"
        nor "Feil parameter antall til prosedyren %-.192s"
        norwegian-ny "Feil parameter tal til prosedyra %-.192s"
        pol "Incorrect parameter count to procedure %-.192s"
        por "Número de parâmetros incorreto para a 'procedure' '%-.192s'"
        rum "Procedura '%-.192s' are un numar incorect de parametri"
        rus "Некорректное количество параметров для процедуры '%-.192s'"
        serbian "Pogrešan broj parametara za proceduru '%-.192s'"
        slo "Chybný počet parametrov procedúry '%-.192s'"
        spa "Equivocado parametro count para procedimiento %-.192s"
        swe "Felaktigt antal parametrar till procedur %-.192s"
        ukr "Хибна кількість параметрів процедури '%-.192s'"
ER_WRONG_PARAMETERS_TO_PROCEDURE
        cze "Chybné parametry procedury %-.192s"
        dan "Forkert(e) parametre til proceduren %-.192s"
        nla "Foutieve parameters voor procedure %-.192s"
        eng "Incorrect parameters to procedure '%-.192s'"
        est "Vigased parameetrid protseduurile '%-.192s'"
        fre "Paramètre erroné pour la procedure %-.192s"
        ger "Falsche Parameter für Prozedur '%-.192s'"
        greek "Λάθος παράμετροι στην διαδικασία '%-.192s'"
        hun "Rossz parameter a(z) '%-.192s' eljarasban"
        ita "Parametri errati per la procedura '%-.192s'"
        jpn "プロシージャ '%-.192s' へのパラメータが不正です。"
        kor "'%-.192s' 수행문에 대한 부정확한 파라메터"
        nor "Feil parametre til prosedyren %-.192s"
        norwegian-ny "Feil parameter til prosedyra %-.192s"
        pol "Incorrect parameters to procedure %-.192s"
        por "Parâmetros incorretos para a 'procedure' '%-.192s'"
        rum "Procedura '%-.192s' are parametrii incorecti"
        rus "Некорректные параметры для процедуры '%-.192s'"
        serbian "Pogrešni parametri prosleđeni proceduri '%-.192s'"
        slo "Chybné parametre procedúry '%-.192s'"
        spa "Equivocados parametros para procedimiento %-.192s"
        swe "Felaktiga parametrar till procedur %-.192s"
        ukr "Хибний параметер процедури '%-.192s'"
ER_UNKNOWN_TABLE 42S02
        cze "Neznámá tabulka '%-.192s' v %-.32s"
        dan "Ukendt tabel '%-.192s' i %-.32s"
        nla "Onbekende tabel '%-.192s' in %-.32s"
        eng "Unknown table '%-.192s' in %-.32s"
        est "Tundmatu tabel '%-.192s' %-.32s-s"
        fre "Table inconnue '%-.192s' dans %-.32s"
        ger "Unbekannte Tabelle '%-.192s' in '%-.32s'"
        greek "Αγνωστος πίνακας '%-.192s' σε %-.32s"
        hun "Ismeretlen tabla: '%-.192s' %-.32s-ban"
        ita "Tabella '%-.192s' sconosciuta in %-.32s"
        jpn "'%-.192s' は %-.32s では不明な表です。"
        kor "알수 없는 테이블 '%-.192s' (데이타베이스 %-.32s)"
        nor "Ukjent tabell '%-.192s' i %-.32s"
        norwegian-ny "Ukjend tabell '%-.192s' i %-.32s"
        pol "Unknown table '%-.192s' in %-.32s"
        por "Tabela '%-.192s' desconhecida em '%-.32s'"
        rum "Tabla '%-.192s' invalida in %-.32s"
        rus "Неизвестная таблица '%-.192s' в %-.32s"
        serbian "Nepoznata tabela '%-.192s' u '%-.32s'"
        slo "Neznáma tabuľka '%-.192s' v %-.32s"
        spa "Tabla desconocida '%-.192s' in %-.32s"
        swe "Okänd tabell '%-.192s' i '%-.32s'"
        ukr "Невідома таблиця '%-.192s' у %-.32s"
ER_FIELD_SPECIFIED_TWICE 42000
        cze "Položka '%-.192s' je zadána dvakrát"
        dan "Feltet '%-.192s' er anvendt to gange"
        nla "Veld '%-.192s' is dubbel gespecificeerd"
        eng "Column '%-.192s' specified twice"
        est "Tulp '%-.192s' on määratletud topelt"
        fre "Champ '%-.192s' spécifié deux fois"
        ger "Feld '%-.192s' wurde zweimal angegeben"
        greek "Το πεδίο '%-.192s' έχει ορισθεί δύο φορές"
        hun "A(z) '%-.192s' mezot ketszer definialta"
        ita "Campo '%-.192s' specificato 2 volte"
        jpn "列 '%-.192s' は2回指定されています。"
        kor "칼럼 '%-.192s'는 두번 정의되어 있읍니다."
        nor "Feltet '%-.192s' er spesifisert to ganger"
        norwegian-ny "Feltet '%-.192s' er spesifisert to gangar"
        pol "Field '%-.192s' specified twice"
        por "Coluna '%-.192s' especificada duas vezes"
        rum "Coloana '%-.192s' specificata de doua ori"
        rus "Столбец '%-.192s' указан дважды"
        serbian "Kolona '%-.192s' je navedena dva puta"
        slo "Pole '%-.192s' je zadané dvakrát"
        spa "Campo '%-.192s' especificado dos veces"
        swe "Fält '%-.192s' är redan använt"
        ukr "Стовбець '%-.192s' зазначено двічі"
ER_INVALID_GROUP_FUNC_USE
        cze "Nesprávné použití funkce group"
        dan "Forkert brug af grupperings-funktion"
        nla "Ongeldig gebruik van GROUP-functie"
        eng "Invalid use of group function"
        est "Vigane grupeerimisfunktsiooni kasutus"
        fre "Utilisation invalide de la clause GROUP"
        ger "Falsche Verwendung einer Gruppierungsfunktion"
        greek "Εσφαλμένη χρήση της group function"
        hun "A group funkcio ervenytelen hasznalata"
        ita "Uso non valido di una funzione di raggruppamento"
        jpn "集計関数の使用方法が不正です。"
        kor "잘못된 그룹 함수를 사용하였습니다."
        por "Uso inválido de função de agrupamento (GROUP)"
        rum "Folosire incorecta a functiei group"
        rus "Неправильное использование групповых функций"
        serbian "Pogrešna upotreba 'GROUP' funkcije"
        slo "Nesprávne použitie funkcie GROUP"
        spa "Invalido uso de función en grupo"
        swe "Felaktig användning av SQL grupp function"
        ukr "Хибне використання функції групування"
ER_UNSUPPORTED_EXTENSION 42000
        cze "Tabulka '%-.192s' používá rozšíření, které v této verzi MySQL není"
        dan "Tabellen '%-.192s' bruger et filtypenavn som ikke findes i denne MySQL version"
        nla "Tabel '%-.192s' gebruikt een extensie, die niet in deze MySQL-versie voorkomt."
        eng "Table '%-.192s' uses an extension that doesn't exist in this MySQL version"
        est "Tabel '%-.192s' kasutab laiendust, mis ei eksisteeri antud MySQL versioonis"
        fre "Table '%-.192s' : utilise une extension invalide pour cette version de MySQL"
        ger "Tabelle '%-.192s' verwendet eine Erweiterung, die in dieser MySQL-Version nicht verfügbar ist"
        greek "Ο πίνακς '%-.192s' χρησιμοποιεί κάποιο extension που δεν υπάρχει στην έκδοση αυτή της MySQL"
        hun "A(z) '%-.192s' tabla olyan bovitest hasznal, amely nem letezik ebben a MySQL versioban."
        ita "La tabella '%-.192s' usa un'estensione che non esiste in questa versione di MySQL"
        jpn "表 '%-.192s' は、このMySQLバージョンには無い機能を使用しています。"
        kor "테이블 '%-.192s'는 확장명령을 이용하지만 현재의 MySQL 버젼에서는 존재하지 않습니다."
        nor "Table '%-.192s' uses a extension that doesn't exist in this MySQL version"
        norwegian-ny "Table '%-.192s' uses a extension that doesn't exist in this MySQL version"
        pol "Table '%-.192s' uses a extension that doesn't exist in this MySQL version"
        por "Tabela '%-.192s' usa uma extensão que não existe nesta versão do MySQL"
        rum "Tabela '%-.192s' foloseste o extensire inexistenta in versiunea curenta de MySQL"
        rus "В таблице '%-.192s' используются возможности, не поддерживаемые в этой версии MySQL"
        serbian "Tabela '%-.192s' koristi ekstenziju koje ne postoji u ovoj verziji MySQL-a"
        slo "Tabuľka '%-.192s' používa rozšírenie, ktoré v tejto verzii MySQL nie je"
        spa "Tabla '%-.192s' usa una extensión que no existe en esta MySQL versión"
        swe "Tabell '%-.192s' har en extension som inte finns i denna version av MySQL"
        ukr "Таблиця '%-.192s' використовує розширення, що не існує у цій версії MySQL"
ER_TABLE_MUST_HAVE_COLUMNS 42000
        cze "Tabulka musí mít alespoň jeden sloupec"
        dan "En tabel skal have mindst een kolonne"
        nla "Een tabel moet minstens 1 kolom bevatten"
        eng "A table must have at least 1 column"
        est "Tabelis peab olema vähemalt üks tulp"
        fre "Une table doit comporter au moins une colonne"
        ger "Eine Tabelle muss mindestens eine Spalte besitzen"
        greek "Ενας πίνακας πρέπει να έχει τουλάχιστον ένα πεδίο"
        hun "A tablanak legalabb egy oszlopot tartalmazni kell"
        ita "Una tabella deve avere almeno 1 colonna"
        jpn "表には最低でも1個の列が必要です。"
        kor "하나의 테이블에서는 적어도 하나의 칼럼이 존재하여야 합니다."
        por "Uma tabela tem que ter pelo menos uma (1) coluna"
        rum "O tabela trebuie sa aiba cel putin o coloana"
        rus "В таблице должен быть как минимум один столбец"
        serbian "Tabela mora imati najmanje jednu kolonu"
        slo "Tabuľka musí mať aspoň 1 pole"
        spa "Una tabla debe tener al menos 1 columna"
        swe "Tabeller måste ha minst 1 kolumn"
        ukr "Таблиця повинна мати хочаб один стовбець"
ER_RECORD_FILE_FULL
        cze "Tabulka '%-.192s' je plná"
        dan "Tabellen '%-.192s' er fuld"
        nla "De tabel '%-.192s' is vol"
        eng "The table '%-.192s' is full"
        est "Tabel '%-.192s' on täis"
        fre "La table '%-.192s' est pleine"
        ger "Tabelle '%-.192s' ist voll"
        greek "Ο πίνακας '%-.192s' είναι γεμάτος"
        hun "A '%-.192s' tabla megtelt"
        ita "La tabella '%-.192s' e` piena"
        jpn "表 '%-.192s' は満杯です。"
        kor "테이블 '%-.192s'가 full났습니다. "
        por "Tabela '%-.192s' está cheia"
        rum "Tabela '%-.192s' e plina"
        rus "Таблица '%-.192s' переполнена"
        serbian "Tabela '%-.192s' je popunjena do kraja"
        slo "Tabuľka '%-.192s' je plná"
        spa "La tabla '%-.192s' está llena"
        swe "Tabellen '%-.192s' är full"
        ukr "Таблиця '%-.192s' заповнена"
ER_UNKNOWN_CHARACTER_SET 42000
        cze "Neznámá znaková sada: '%-.64s'"
        dan "Ukendt tegnsæt: '%-.64s'"
        nla "Onbekende character set: '%-.64s'"
        eng "Unknown character set: '%-.64s'"
        est "Vigane kooditabel '%-.64s'"
        fre "Jeu de caractères inconnu: '%-.64s'"
        ger "Unbekannter Zeichensatz: '%-.64s'"
        greek "Αγνωστο character set: '%-.64s'"
        hun "Ervenytelen karakterkeszlet: '%-.64s'"
        ita "Set di caratteri '%-.64s' sconosciuto"
        jpn "不明な文字コードセット: '%-.64s'"
        kor "알수없는 언어 Set: '%-.64s'"
        por "Conjunto de caracteres '%-.64s' desconhecido"
        rum "Set de caractere invalid: '%-.64s'"
        rus "Неизвестная кодировка '%-.64s'"
        serbian "Nepoznati karakter-set: '%-.64s'"
        slo "Neznáma znaková sada: '%-.64s'"
        spa "Juego de caracteres desconocido: '%-.64s'"
        swe "Okänd teckenuppsättning: '%-.64s'"
        ukr "Невідома кодова таблиця: '%-.64s'"
ER_TOO_MANY_TABLES
        cze "Příliš mnoho tabulek, MySQL jich může mít v joinu jen %d"
        dan "For mange tabeller. MySQL kan kun bruge %d tabeller i et join"
        nla "Teveel tabellen. MySQL kan slechts %d tabellen in een join bevatten"
        eng "Too many tables; MySQL can only use %d tables in a join"
        est "Liiga palju tabeleid. MySQL suudab JOINiga ühendada kuni %d tabelit"
        fre "Trop de tables. MySQL ne peut utiliser que %d tables dans un JOIN"
        ger "Zu viele Tabellen. MySQL kann in einem Join maximal %d Tabellen verwenden"
        greek "Πολύ μεγάλος αριθμός πινάκων. Η MySQL μπορεί να χρησιμοποιήσει %d πίνακες σε διαδικασία join"
        hun "Tul sok tabla. A MySQL csak %d tablat tud kezelni osszefuzeskor"
        ita "Troppe tabelle. MySQL puo` usare solo %d tabelle in una join"
        jpn "表が多すぎます。MySQLがJOINできる表は %d 個までです。"
        kor "너무 많은 테이블이 Join되었습니다. MySQL에서는 JOIN시 %d개의 테이블만 사용할 수 있습니다."
        por "Tabelas demais. O MySQL pode usar somente %d tabelas em uma junção (JOIN)"
        rum "Prea multe tabele. MySQL nu poate folosi mai mult de %d tabele intr-un join"
        rus "Слишком много таблиц. MySQL может использовать только %d таблиц в соединении"
        serbian "Previše tabela. MySQL može upotrebiti maksimum %d tabela pri 'JOIN' operaciji"
        slo "Príliš mnoho tabuliek. MySQL môže použiť len %d v JOIN-e"
        spa "Muchas tablas. MySQL solamente puede usar %d tablas en un join"
        swe "För många tabeller. MySQL can ha högst %d tabeller i en och samma join"
        ukr "Забагато таблиць. MySQL може використовувати лише %d таблиць у об'єднанні"
ER_TOO_MANY_FIELDS
        cze "Příliš mnoho položek"
        dan "For mange felter"
        nla "Te veel velden"
        eng "Too many columns"
        est "Liiga palju tulpasid"
        fre "Trop de champs"
        ger "Zu viele Felder"
        greek "Πολύ μεγάλος αριθμός πεδίων"
        hun "Tul sok mezo"
        ita "Troppi campi"
        jpn "列が多すぎます。"
        kor "칼럼이 너무 많습니다."
        por "Colunas demais"
        rum "Prea multe coloane"
        rus "Слишком много столбцов"
        serbian "Previše kolona"
        slo "Príliš mnoho polí"
        spa "Muchos campos"
        swe "För många fält"
        ukr "Забагато стовбців"
ER_TOO_BIG_ROWSIZE 42000
        cze "Řádek je příliš velký. Maximální velikost řádku, nepočítaje položky blob, je %ld. Musíte změnit některé položky na blob"
        dan "For store poster. Max post størrelse, uden BLOB's, er %ld. Du må lave nogle felter til BLOB's"
        nla "Rij-grootte is groter dan toegestaan. Maximale rij grootte, blobs niet meegeteld, is %ld. U dient sommige velden in blobs te veranderen."
        eng "Row size too large. The maximum row size for the used table type, not counting BLOBs, is %ld. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs"
        est "Liiga pikk kirje. Kirje maksimumpikkus arvestamata BLOB-tüüpi välju on %ld. Muuda mõned väljad BLOB-tüüpi väljadeks"
        fre "Ligne trop grande. Le taille maximale d'une ligne, sauf les BLOBs, est %ld. Changez le type de quelques colonnes en BLOB"
        ger "Zeilenlänge zu groß. Die maximale Zeilenlänge für den verwendeten Tabellentyp (ohne BLOB-Felder) beträgt %ld. Einige Felder müssen in BLOB oder TEXT umgewandelt werden"
        greek "Πολύ μεγάλο μέγεθος εγγραφής. Το μέγιστο μέγεθος εγγραφής, χωρίς να υπολογίζονται τα blobs, είναι %ld. Πρέπει να ορίσετε κάποια πεδία σαν blobs"
        hun "Tul nagy sormeret. A maximalis sormeret (nem szamolva a blob objektumokat) %ld. Nehany mezot meg kell valtoztatnia"
        ita "Riga troppo grande. La massima grandezza di una riga, non contando i BLOB, e` %ld. Devi cambiare alcuni campi in BLOB"
        jpn "行サイズが大きすぎます。この表の最大行サイズは BLOB を含まずに %ld です。格納時のオーバーヘッドも含まれます(マニュアルを確認してください)。列をTEXTまたはBLOBに変更する必要があります。"
        kor "너무 큰 row 사이즈입니다. BLOB를 계산하지 않고 최대 row 사이즈는 %ld입니다. 얼마간의 필드들을 BLOB로 바꾸셔야 겠군요.."
        por "Tamanho de linha grande demais. O máximo tamanho de linha, não contando BLOBs, é %ld. Você tem que mudar alguns campos para BLOBs"
        rum "Marimea liniei (row) prea mare. Marimea maxima a liniei, excluzind BLOB-urile este de %ld. Trebuie sa schimbati unele cimpuri in BLOB-uri"
        rus "Слишком большой размер записи. Максимальный размер строки, исключая поля BLOB, - %ld. Возможно, вам следует изменить тип некоторых полей на BLOB"
        serbian "Prevelik slog. Maksimalna veličina sloga, ne računajući BLOB polja, je %ld. Trebali bi da promenite tip nekih polja u BLOB"
        slo "Riadok je príliš veľký. Maximálna veľkosť riadku, okrem 'BLOB', je %ld. Musíte zmeniť niektoré položky na BLOB"
        spa "Tamaño de línea muy grande. Máximo tamaño de línea, no contando blob, es %ld. Tu tienes que cambiar algunos campos para blob"
        swe "För stor total radlängd. Den högst tillåtna radlängden, förutom BLOBs, är %ld. Ändra några av dina fält till BLOB"
        ukr "Задовга строка. Найбільшою довжиною строки, не рахуючи BLOB, є %ld. Вам потрібно привести деякі стовбці до типу BLOB"
ER_STACK_OVERRUN
        cze "Přetečení zásobníku threadu: použito %ld z %ld. Použijte 'mysqld --thread_stack=#' k zadání většího zásobníku"
        dan "Thread stack brugt:  Brugt: %ld af en %ld stak.  Brug 'mysqld --thread_stack=#' for at allokere en større stak om nødvendigt"
        nla "Thread stapel overrun:  Gebruikte: %ld van een %ld stack. Gebruik 'mysqld --thread_stack=#' om een grotere stapel te definieren (indien noodzakelijk)."
        eng "Thread stack overrun:  Used: %ld of a %ld stack.  Use 'mysqld --thread_stack=#' to specify a bigger stack if needed"
        fre "Débordement de la pile des tâches (Thread stack). Utilisées: %ld pour une pile de %ld.  Essayez 'mysqld --thread_stack=#' pour indiquer une plus grande valeur"
        ger "Thread-Stack-Überlauf. Benutzt: %ld von %ld Stack. 'mysqld --thread_stack=#' verwenden, um bei Bedarf einen größeren Stack anzulegen"
        greek "Stack overrun στο thread:  Used: %ld of a %ld stack.  Παρακαλώ χρησιμοποιείστε 'mysqld --thread_stack=#' για να ορίσετε ένα μεγαλύτερο stack αν χρειάζεται"
        hun "Thread verem tullepes:  Used: %ld of a %ld stack. Hasznalja a 'mysqld --thread_stack=#' nagyobb verem definialasahoz"
        ita "Thread stack overrun:  Usati: %ld di uno stack di %ld.  Usa 'mysqld --thread_stack=#' per specificare uno stack piu` grande."
        jpn "スレッドスタック不足です(使用: %ld ; サイズ: %ld)。必要に応じて、より大きい値で 'mysqld --thread_stack=#' の指定をしてください。"
        kor "쓰레드 스택이 넘쳤습니다.  사용: %ld개 스택: %ld개.  만약 필요시 더큰 스택을 원할때에는 'mysqld --thread_stack=#' 를 정의하세요"
        por "Estouro da pilha do 'thread'. Usados %ld de uma pilha de %ld. Use 'mysqld --thread_stack=#' para especificar uma pilha maior, se necessário"
        rum "Stack-ul thread-ului a fost depasit (prea mic):  Folositi: %ld intr-un stack de %ld.  Folositi 'mysqld --thread_stack=#' ca sa specifici un stack mai mare"
        rus "Стек потоков переполнен:  использовано: %ld из %ld стека.  Применяйте 'mysqld --thread_stack=#' для указания большего размера стека, если необходимо"
        serbian "Prepisivanje thread stack-a:  Upotrebljeno: %ld od %ld stack memorije.  Upotrebite 'mysqld --thread_stack=#' da navedete veći stack ako je potrebno"
        slo "Pretečenie zásobníku vlákna:  použité: %ld z %ld.  Použite 'mysqld --thread_stack=#' k zadaniu väčšieho zásobníka"
        spa "Sobrecarga de la pila de thread:  Usada: %ld de una %ld pila.  Use 'mysqld --thread_stack=#' para especificar una mayor pila si necesario"
        swe "Trådstacken tog slut:  Har använt %ld av %ld bytes.  Använd 'mysqld --thread_stack=#' ifall du behöver en större stack"
        ukr "Стек гілок переповнено:  Використано: %ld з %ld. Використовуйте 'mysqld --thread_stack=#' аби зазначити більший стек, якщо необхідно"
# Not used since 5.8 and probably earlier.
ER_WRONG_OUTER_JOIN_UNUSED 42000
        cze "V OUTER JOIN byl nalezen křížový odkaz. Prověřte ON podmínky"
        dan "Krydsreferencer fundet i OUTER JOIN; check dine ON conditions"
        nla "Gekruiste afhankelijkheid gevonden in OUTER JOIN. Controleer uw ON-conditions"
        eng "Cross dependency found in OUTER JOIN; examine your ON conditions"
        est "Ristsõltuvus OUTER JOIN klauslis. Kontrolli oma ON tingimusi"
        fre "Dépendance croisée dans une clause OUTER JOIN. Vérifiez la condition ON"
        ger "OUTER JOIN enthält fehlerhafte Abhängigkeiten. In ON verwendete Bedingungen überprüfen"
        greek "Cross dependency βρέθηκε σε OUTER JOIN.  Παρακαλώ εξετάστε τις συνθήκες που θέσατε στο ON"
        hun "Keresztfuggoseg van az OUTER JOIN-ban. Ellenorizze az ON felteteleket"
        ita "Trovata una dipendenza incrociata nella OUTER JOIN. Controlla le condizioni ON"
        jpn "OUTER JOINに相互依存が見つかりました。ON句の条件を確認して下さい。"
        por "Dependência cruzada encontrada em junção externa (OUTER JOIN); examine as condições utilizadas nas cláusulas 'ON'"
        rum "Dependinta incrucisata (cross dependency) gasita in OUTER JOIN.  Examinati conditiile ON"
        rus "В OUTER JOIN обнаружена перекрестная зависимость. Внимательно проанализируйте свои условия ON"
        serbian "Unakrsna zavisnost pronađena u komandi 'OUTER JOIN'. Istražite vaše 'ON' uslove"
        slo "V OUTER JOIN bol nájdený krížový odkaz.  Skontrolujte podmienky ON"
        spa "Dependencia cruzada encontrada en OUTER JOIN.  Examine su condición ON"
        swe "Felaktigt referens i OUTER JOIN.  Kontrollera ON-uttrycket"
        ukr "Перехресна залежність у OUTER JOIN. Перевірте умову ON"
ER_NULL_COLUMN_IN_INDEX 42000
        eng "Table handler doesn't support NULL in given index. Please change column '%-.192s' to be NOT NULL or use another handler"
        swe "Tabell hanteraren kan inte indexera NULL kolumner för den givna index typen. Ändra '%-.192s' till NOT NULL eller använd en annan hanterare"
ER_CANT_FIND_UDF
        cze "Nemohu načíst funkci '%-.192s'"
        dan "Kan ikke læse funktionen '%-.192s'"
        nla "Kan functie '%-.192s' niet laden"
        eng "Can't load function '%-.192s'"
        est "Ei suuda avada funktsiooni '%-.192s'"
        fre "Imposible de charger la fonction '%-.192s'"
        ger "Kann Funktion '%-.192s' nicht laden"
        greek "Δεν είναι δυνατή η διαδικασία load για τη συνάρτηση '%-.192s'"
        hun "A(z) '%-.192s' fuggveny nem toltheto be"
        ita "Impossibile caricare la funzione '%-.192s'"
        jpn "関数 '%-.192s' をロードできません。"
        kor "'%-.192s' 함수를 로드하지 못했습니다."
        por "Não pode carregar a função '%-.192s'"
        rum "Nu pot incarca functia '%-.192s'"
        rus "Невозможно загрузить функцию '%-.192s'"
        serbian "Ne mogu da učitam funkciju '%-.192s'"
        slo "Nemôžem načítať funkciu '%-.192s'"
        spa "No puedo cargar función '%-.192s'"
        swe "Kan inte ladda funktionen '%-.192s'"
        ukr "Не можу завантажити функцію '%-.192s'"
ER_CANT_INITIALIZE_UDF
        cze "Nemohu inicializovat funkci '%-.192s'; %-.192s"
        dan "Kan ikke starte funktionen '%-.192s'; %-.192s"
        nla "Kan functie '%-.192s' niet initialiseren; %-.192s"
        eng "Can't initialize function '%-.192s'; %-.192s"
        est "Ei suuda algväärtustada funktsiooni '%-.192s'; %-.192s"
        fre "Impossible d'initialiser la fonction '%-.192s'; %-.192s"
        ger "Kann Funktion '%-.192s' nicht initialisieren: %-.192s"
        greek "Δεν είναι δυνατή η έναρξη της συνάρτησης '%-.192s'; %-.192s"
        hun "A(z) '%-.192s' fuggveny nem inicializalhato; %-.192s"
        ita "Impossibile inizializzare la funzione '%-.192s'; %-.192s"
        jpn "関数 '%-.192s' を初期化できません。; %-.192s"
        kor "'%-.192s' 함수를 초기화 하지 못했습니다.; %-.192s"
        por "Não pode inicializar a função '%-.192s' - '%-.192s'"
        rum "Nu pot initializa functia '%-.192s'; %-.192s"
        rus "Невозможно инициализировать функцию '%-.192s'; %-.192s"
        serbian "Ne mogu da inicijalizujem funkciju '%-.192s'; %-.192s"
        slo "Nemôžem inicializovať funkciu '%-.192s'; %-.192s"
        spa "No puedo inicializar función '%-.192s'; %-.192s"
        swe "Kan inte initialisera funktionen '%-.192s'; '%-.192s'"
        ukr "Не можу ініціалізувати функцію '%-.192s'; %-.192s"
ER_UDF_NO_PATHS
        cze "Pro sdílenou knihovnu nejsou povoleny cesty"
        dan "Angivelse af sti ikke tilladt for delt bibliotek"
        nla "Geen pad toegestaan voor shared library"
        eng "No paths allowed for shared library"
        est "Teegi nimes ei tohi olla kataloogi"
        fre "Chemin interdit pour les bibliothèques partagées"
        ger "Keine Pfade gestattet für Shared Library"
        greek "Δεν βρέθηκαν paths για την shared library"
        hun "Nincs ut a megosztott konyvtarakhoz (shared library)"
        ita "Non sono ammessi path per le librerie condivisa"
        jpn "共有ライブラリにはパスを指定できません。"
        kor "공유 라이버러리를 위한 패스가 정의되어 있지 않습니다."
        por "Não há caminhos (paths) permitidos para biblioteca compartilhada"
        rum "Nici un paths nu e permis pentru o librarie shared"
        rus "Недопустимо указывать пути для динамических библиотек"
        serbian "Ne postoje dozvoljene putanje do share-ovane biblioteke"
        slo "Neprípustné žiadne cesty k zdieľanej knižnici"
        spa "No pasos permitidos para librarias conjugadas"
        swe "Man får inte ange sökväg för dynamiska bibliotek"
        ukr "Не дозволено використовувати путі для розділюваних бібліотек"
ER_UDF_EXISTS
        cze "Funkce '%-.192s' již existuje"
        dan "Funktionen '%-.192s' findes allerede"
        nla "Functie '%-.192s' bestaat reeds"
        eng "Function '%-.192s' already exists"
        est "Funktsioon '%-.192s' juba eksisteerib"
        fre "La fonction '%-.192s' existe déjà"
        ger "Funktion '%-.192s' existiert schon"
        greek "Η συνάρτηση '%-.192s' υπάρχει ήδη"
        hun "A '%-.192s' fuggveny mar letezik"
        ita "La funzione '%-.192s' esiste gia`"
        jpn "関数 '%-.192s' はすでに定義されています。"
        kor "'%-.192s' 함수는 이미 존재합니다."
        por "Função '%-.192s' já existe"
        rum "Functia '%-.192s' exista deja"
        rus "Функция '%-.192s' уже существует"
        serbian "Funkcija '%-.192s' već postoji"
        slo "Funkcia '%-.192s' už existuje"
        spa "Función '%-.192s' ya existe"
        swe "Funktionen '%-.192s' finns redan"
        ukr "Функція '%-.192s' вже існує"
ER_CANT_OPEN_LIBRARY
        cze "Nemohu otevřít sdílenou knihovnu '%-.192s' (errno: %d %-.128s)"
        dan "Kan ikke åbne delt bibliotek '%-.192s' (errno: %d %-.128s)"
        nla "Kan shared library '%-.192s' niet openen (Errcode: %d %-.128s)"
        eng "Can't open shared library '%-.192s' (errno: %d %-.128s)"
        est "Ei suuda avada jagatud teeki '%-.192s' (veakood: %d %-.128s)"
        fre "Impossible d'ouvrir la bibliothèque partagée '%-.192s' (errno: %d %-.128s)"
        ger "Kann Shared Library '%-.192s' nicht öffnen (Fehler: %d %-.128s)"
        greek "Δεν είναι δυνατή η ανάγνωση της shared library '%-.192s' (κωδικός λάθους: %d %-.128s)"
        hun "A(z) '%-.192s' megosztott konyvtar nem hasznalhato (hibakod: %d %-.128s)"
        ita "Impossibile aprire la libreria condivisa '%-.192s' (errno: %d %-.128s)"
        jpn "共有ライブラリ '%-.192s' を開く事ができません。(エラー番号: %d %-.128s)"
        kor "'%-.192s' 공유 라이버러리를 열수 없습니다.(에러번호: %d %-.128s)"
        nor "Can't open shared library '%-.192s' (errno: %d %-.128s)"
        norwegian-ny "Can't open shared library '%-.192s' (errno: %d %-.128s)"
        pol "Can't open shared library '%-.192s' (errno: %d %-.128s)"
        por "Não pode abrir biblioteca compartilhada '%-.192s' (erro no. %d '%-.128s')"
        rum "Nu pot deschide libraria shared '%-.192s' (Eroare: %d %-.128s)"
        rus "Невозможно открыть динамическую библиотеку '%-.192s' (ошибка: %d %-.128s)"
        serbian "Ne mogu da otvorim share-ovanu biblioteku '%-.192s' (errno: %d %-.128s)"
        slo "Nemôžem otvoriť zdieľanú knižnicu '%-.192s' (chybový kód: %d %-.128s)"
        spa "No puedo abrir libraria conjugada '%-.192s' (errno: %d %-.128s)"
        swe "Kan inte öppna det dynamiska biblioteket '%-.192s' (Felkod: %d %-.128s)"
        ukr "Не можу відкрити розділювану бібліотеку '%-.192s' (помилка: %d %-.128s)"
ER_CANT_FIND_DL_ENTRY
        cze "Nemohu najít funkci '%-.128s' v knihovně"
        dan "Kan ikke finde funktionen '%-.128s' i bibliotek"
        nla "Kan functie '%-.128s' niet in library vinden"
        eng "Can't find symbol '%-.128s' in library"
        est "Ei leia funktsiooni '%-.128s' antud teegis"
        fre "Impossible de trouver la fonction '%-.128s' dans la bibliothèque"
        ger "Kann Funktion '%-.128s' in der Library nicht finden"
        greek "Δεν είναι δυνατή η ανεύρεση της συνάρτησης '%-.128s' στην βιβλιοθήκη"
        hun "A(z) '%-.128s' fuggveny nem talalhato a konyvtarban"
        ita "Impossibile trovare la funzione '%-.128s' nella libreria"
        jpn "関数 '%-.128s' は共有ライブラリー中にありません。"
        kor "라이버러리에서 '%-.128s' 함수를 찾을 수 없습니다."
        por "Não pode encontrar a função '%-.128s' na biblioteca"
        rum "Nu pot gasi functia '%-.128s' in libraria"
        rus "Невозможно отыскать символ '%-.128s' в библиотеке"
        serbian "Ne mogu da pronadjem funkciju '%-.128s' u biblioteci"
        slo "Nemôžem nájsť funkciu '%-.128s' v knižnici"
        spa "No puedo encontrar función '%-.128s' en libraria"
        swe "Hittar inte funktionen '%-.128s' in det dynamiska biblioteket"
        ukr "Не можу знайти функцію '%-.128s' у бібліотеці"
ER_FUNCTION_NOT_DEFINED
        cze "Funkce '%-.192s' není definována"
        dan "Funktionen '%-.192s' er ikke defineret"
        nla "Functie '%-.192s' is niet gedefinieerd"
        eng "Function '%-.192s' is not defined"
        est "Funktsioon '%-.192s' ei ole defineeritud"
        fre "La fonction '%-.192s' n'est pas définie"
        ger "Funktion '%-.192s' ist nicht definiert"
        greek "Η συνάρτηση '%-.192s' δεν έχει ορισθεί"
        hun "A '%-.192s' fuggveny nem definialt"
        ita "La funzione '%-.192s' non e` definita"
        jpn "関数 '%-.192s' は定義されていません。"
        kor "'%-.192s' 함수가 정의되어 있지 않습니다."
        por "Função '%-.192s' não está definida"
        rum "Functia '%-.192s' nu e definita"
        rus "Функция '%-.192s' не определена"
        serbian "Funkcija '%-.192s' nije definisana"
        slo "Funkcia '%-.192s' nie je definovaná"
        spa "Función '%-.192s' no está definida"
        swe "Funktionen '%-.192s' är inte definierad"
        ukr "Функцію '%-.192s' не визначено"
ER_HOST_IS_BLOCKED
        cze "Stroj '%-.255s' je zablokován kvůli mnoha chybám při připojování. Odblokujete použitím 'mysqladmin flush-hosts'"
        dan "Værten '%-.255s' er blokeret på grund af mange fejlforespørgsler. Lås op med 'mysqladmin flush-hosts'"
        nla "Host '%-.255s' is geblokkeeerd vanwege te veel verbindings fouten. Deblokkeer met 'mysqladmin flush-hosts'"
        eng "Host '%-.255s' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'"
        est "Masin '%-.255s' on blokeeritud hulgaliste ühendusvigade tõttu. Blokeeringu saab tühistada 'mysqladmin flush-hosts' käsuga"
        fre "L'hôte '%-.255s' est bloqué à cause d'un trop grand nombre d'erreur de connexion. Débloquer le par 'mysqladmin flush-hosts'"
        ger "Host '%-.255s' blockiert wegen zu vieler Verbindungsfehler. Aufheben der Blockierung mit 'mysqladmin flush-hosts'"
        greek "Ο υπολογιστής '%-.255s' έχει αποκλεισθεί λόγω πολλαπλών λαθών σύνδεσης. Προσπαθήστε να διορώσετε με 'mysqladmin flush-hosts'"
        hun "A '%-.255s' host blokkolodott, tul sok kapcsolodasi hiba miatt. Hasznalja a 'mysqladmin flush-hosts' parancsot"
        ita "Sistema '%-.255s' bloccato a causa di troppi errori di connessione. Per sbloccarlo: 'mysqladmin flush-hosts'"
        jpn "接続エラーが多いため、ホスト '%-.255s' は拒否されました。'mysqladmin flush-hosts' で解除できます。"
        kor "너무 많은 연결오류로 인하여 호스트 '%-.255s'는 블락되었습니다. 'mysqladmin flush-hosts'를 이용하여 블락을 해제하세요"
        por "'Host' '%-.255s' está bloqueado devido a muitos erros de conexão. Desbloqueie com 'mysqladmin flush-hosts'"
        rum "Host-ul '%-.255s' e blocat din cauza multelor erori de conectie. Poti deploca folosind 'mysqladmin flush-hosts'"
        rus "Хост '%-.255s' заблокирован из-за слишком большого количества ошибок соединения. Разблокировать его можно с помощью 'mysqladmin flush-hosts'"
        serbian "Host '%-.255s' je blokiran zbog previše grešaka u konekciji.  Možete ga odblokirati pomoću komande 'mysqladmin flush-hosts'"
        spa "Servidor '%-.255s' está bloqueado por muchos errores de conexión.  Desbloquear con 'mysqladmin flush-hosts'"
        swe "Denna dator, '%-.255s', är blockerad pga många felaktig paket. Gör 'mysqladmin flush-hosts' för att ta bort alla blockeringarna"
        ukr "Хост '%-.255s' заблоковано з причини великої кількості помилок з'єднання. Для розблокування використовуйте 'mysqladmin flush-hosts'"
ER_HOST_NOT_PRIVILEGED
        cze "Stroj '%-.255s' nemá povoleno se k tomuto MySQL serveru připojit"
        dan "Værten '%-.255s' kan ikke tilkoble denne MySQL-server"
        nla "Het is host '%-.255s' is niet toegestaan verbinding te maken met deze MySQL server"
        eng "Host '%-.255s' is not allowed to connect to this MySQL server"
        est "Masinal '%-.255s' puudub ligipääs sellele MySQL serverile"
        fre "Le hôte '%-.255s' n'est pas authorisé à se connecter à ce serveur MySQL"
        ger "Host '%-.255s' hat keine Berechtigung, sich mit diesem MySQL-Server zu verbinden"
        greek "Ο υπολογιστής '%-.255s' δεν έχει δικαίωμα σύνδεσης με τον MySQL server"
        hun "A '%-.255s' host szamara nem engedelyezett a kapcsolodas ehhez a MySQL szerverhez"
        ita "Al sistema '%-.255s' non e` consentita la connessione a questo server MySQL"
        jpn "ホスト '%-.255s' からのこの MySQL server への接続は許可されていません。"
        kor "'%-.255s' 호스트는 이 MySQL서버에 접속할 허가를 받지 못했습니다."
        por "'Host' '%-.255s' não tem permissão para se conectar com este servidor MySQL"
        rum "Host-ul '%-.255s' nu este permis a se conecta la aceste server MySQL"
        rus "Хосту '%-.255s' не разрешается подключаться к этому серверу MySQL"
        serbian "Host-u '%-.255s' nije dozvoljeno da se konektuje na ovaj MySQL server"
        spa "Servidor '%-.255s' no está permitido para conectar con este servidor MySQL"
        swe "Denna dator, '%-.255s', har inte privileger att använda denna MySQL server"
        ukr "Хосту '%-.255s' не доволено зв'язуватись з цим сервером MySQL"
ER_PASSWORD_ANONYMOUS_USER 42000
        cze "Používáte MySQL jako anonymní uživatel a anonymní uživatelé nemají povoleno měnit hesla"
        dan "Du bruger MySQL som anonym bruger. Anonyme brugere må ikke ændre adgangskoder"
        nla "U gebruikt MySQL als anonieme gebruiker en deze mogen geen wachtwoorden wijzigen"
        eng "You are using MySQL as an anonymous user and anonymous users are not allowed to change passwords"
        est "Te kasutate MySQL-i anonüümse kasutajana, kelledel pole parooli muutmise õigust"
        fre "Vous utilisez un utilisateur anonyme et les utilisateurs anonymes ne sont pas autorisés à changer les mots de passe"
        ger "Sie benutzen MySQL als anonymer Benutzer und dürfen daher keine Passwörter ändern"
        greek "Χρησιμοποιείτε την MySQL σαν anonymous user και έτσι δεν μπορείτε να αλλάξετε τα passwords άλλων χρηστών"
        hun "Nevtelen (anonymous) felhasznalokent nem negedelyezett a jelszovaltoztatas"
        ita "Impossibile cambiare la password usando MySQL come utente anonimo"
        jpn "MySQL を匿名ユーザーで使用しているので、パスワードの変更はできません。"
        kor "당신은 MySQL서버에 익명의 사용자로 접속을 하셨습니다.익명의 사용자는 암호를 변경할 수 없습니다."
        por "Você está usando o MySQL como usuário anônimo e usuários anônimos não têm permissão para mudar senhas"
        rum "Dumneavoastra folositi MySQL ca un utilizator anonim si utilizatorii anonimi nu au voie sa schime parolele"
        rus "Вы используете MySQL от имени анонимного пользователя, а анонимным пользователям не разрешается менять пароли"
        serbian "Vi koristite MySQL kao anonimni korisnik a anonimnim korisnicima nije dozvoljeno da menjaju lozinke"
        spa "Tu estás usando MySQL como un usuario anonimo y usuarios anonimos no tienen permiso para cambiar las claves"
        swe "Du använder MySQL som en anonym användare och som sådan får du inte ändra ditt lösenord"
        ukr "Ви використовуєте MySQL як анонімний користувач, тому вам не дозволено змінювати паролі"
ER_PASSWORD_NOT_ALLOWED 42000
        cze "Na změnu hesel ostatním musíte mít právo provést update tabulek v databázi mysql"
        dan "Du skal have tilladelse til at opdatere tabeller i MySQL databasen for at ændre andres adgangskoder"
        nla "U moet tabel update priveleges hebben in de mysql database om wachtwoorden voor anderen te mogen wijzigen"
        eng "You must have privileges to update tables in the mysql database to be able to change passwords for others"
        est "Teiste paroolide muutmiseks on nõutav tabelite muutmisõigus 'mysql' andmebaasis"
        fre "Vous devez avoir le privilège update sur les tables de la base de donnée mysql pour pouvoir changer les mots de passe des autres"
        ger "Sie benötigen die Berechtigung zum Aktualisieren von Tabellen in der Datenbank 'mysql', um die Passwörter anderer Benutzer ändern zu können"
        greek "Πρέπει να έχετε δικαίωμα διόρθωσης πινάκων (update) στη βάση δεδομένων mysql για να μπορείτε να αλλάξετε τα passwords άλλων χρηστών"
        hun "Onnek tabla-update joggal kell rendelkeznie a mysql adatbazisban masok jelszavanak megvaltoztatasahoz"
        ita "E` necessario il privilegio di update sulle tabelle del database mysql per cambiare le password per gli altri utenti"
        jpn "他のユーザーのパスワードを変更するためには、mysqlデータベースの表を更新する権限が必要です。"
        kor "당신은 다른사용자들의 암호를 변경할 수 있도록 데이타베이스 변경권한을 가져야 합니다."
        por "Você deve ter privilégios para atualizar tabelas no banco de dados mysql para ser capaz de mudar a senha de outros"
        rum "Trebuie sa aveti privilegii sa actualizati tabelele in bazele de date mysql ca sa puteti sa schimati parolele altora"
        rus "Для того чтобы изменять пароли других пользователей, у вас должны быть привилегии на изменение таблиц в базе данных mysql"
        serbian "Morate imati privilegije da možete da update-ujete određene tabele ako želite da menjate lozinke za druge korisnike"
        spa "Tu debes de tener permiso para actualizar tablas en la base de datos mysql para cambiar las claves para otros"
        swe "För att ändra lösenord för andra måste du ha rättigheter att uppdatera mysql-databasen"
        ukr "Ви повині мати право на оновлення таблиць у базі данних mysql, аби мати можливість змінювати пароль іншим"
ER_PASSWORD_NO_MATCH 42000
        cze "V tabulce user není žádný odpovídající řádek"
        dan "Kan ikke finde nogen tilsvarende poster i bruger tabellen"
        nla "Kan geen enkele passende rij vinden in de gebruikers tabel"
        eng "Can't find any matching row in the user table"
        est "Ei leia vastavat kirjet kasutajate tabelis"
        fre "Impossible de trouver un enregistrement correspondant dans la table user"
        ger "Kann keinen passenden Datensatz in Tabelle 'user' finden"
        greek "Δεν είναι δυνατή η ανεύρεση της αντίστοιχης εγγραφής στον πίνακα των χρηστών"
        hun "Nincs megegyezo sor a user tablaban"
        ita "Impossibile trovare la riga corrispondente nella tabella user"
        jpn "ユーザーテーブルに該当するレコードが見つかりません。"
        kor "사용자 테이블에서 일치하는 것을 찾을 수 없읍니다."
        por "Não pode encontrar nenhuma linha que combine na tabela usuário (user table)"
        rum "Nu pot gasi nici o linie corespunzatoare in tabela utilizatorului"
        rus "Невозможно отыскать подходящую запись в таблице пользователей"
        serbian "Ne mogu da pronađem odgovarajući slog u 'user' tabeli"
        spa "No puedo encontrar una línea correponsdiente en la tabla user"
        swe "Hittade inte användaren i 'user'-tabellen"
        ukr "Не можу знайти відповідних записів у таблиці користувача"
ER_UPDATE_INFO
        cze "Nalezených řádků: %ld  Změněno: %ld  Varování: %ld"
        dan "Poster fundet: %ld  Ændret: %ld  Advarsler: %ld"
        nla "Passende rijen: %ld  Gewijzigd: %ld  Waarschuwingen: %ld"
        eng "Rows matched: %ld  Changed: %ld  Warnings: %ld"
        est "Sobinud kirjeid: %ld  Muudetud: %ld  Hoiatusi: %ld"
        fre "Enregistrements correspondants: %ld  Modifiés: %ld  Warnings: %ld"
        ger "Datensätze gefunden: %ld  Geändert: %ld  Warnungen: %ld"
        hun "Megegyezo sorok szama: %ld  Valtozott: %ld  Warnings: %ld"
        ita "Rows riconosciute: %ld  Cambiate: %ld  Warnings: %ld"
        jpn "該当した行: %ld  変更: %ld  警告: %ld"
        kor "일치하는 Rows : %ld개 변경됨: %ld개  경고: %ld개"
        por "Linhas que combinaram: %ld - Alteradas: %ld - Avisos: %ld"
        rum "Linii identificate (matched): %ld  Schimbate: %ld  Atentionari (warnings): %ld"
        rus "Совпало записей: %ld  Изменено: %ld  Предупреждений: %ld"
        serbian "Odgovarajućih slogova: %ld  Promenjeno: %ld  Upozorenja: %ld"
        spa "Líneas correspondientes: %ld  Cambiadas: %ld  Avisos: %ld"
        swe "Rader: %ld  Uppdaterade: %ld  Varningar: %ld"
        ukr "Записів відповідає: %ld  Змінено: %ld  Застережень: %ld"
ER_CANT_CREATE_THREAD
        cze "Nemohu vytvořit nový thread (errno %d). Pokud je ještě nějaká volná paměť, podívejte se do manuálu na část o chybách specifických pro jednotlivé operační systémy"
        dan "Kan ikke danne en ny tråd (fejl nr. %d). Hvis computeren ikke er løbet tør for hukommelse, kan du se i brugervejledningen for en mulig operativ-system - afhængig fejl"
        nla "Kan geen nieuwe thread aanmaken (Errcode: %d). Indien er geen tekort aan geheugen is kunt u de handleiding consulteren over een mogelijke OS afhankelijke fout"
        eng "Can't create a new thread (errno %d); if you are not out of available memory, you can consult the manual for a possible OS-dependent bug"
        est "Ei suuda luua uut lõime (veakood %d). Kui mälu ei ole otsas, on tõenäoliselt tegemist operatsioonisüsteemispetsiifilise veaga"
        fre "Impossible de créer une nouvelle tâche (errno %d). S'il reste de la mémoire libre, consultez le manual pour trouver un éventuel bug dépendant de l'OS"
        ger "Kann keinen neuen Thread erzeugen (Fehler: %d). Sollte noch Speicher verfügbar sein, bitte im Handbuch wegen möglicher Fehler im Betriebssystem nachschlagen"
        hun "Uj thread letrehozasa nem lehetseges (Hibakod: %d). Amenyiben van meg szabad memoria, olvassa el a kezikonyv operacios rendszerfuggo hibalehetosegekrol szolo reszet"
        ita "Impossibile creare un nuovo thread (errno %d). Se non ci sono problemi di memoria disponibile puoi consultare il manuale per controllare possibili problemi dipendenti dal SO"
        jpn "新規にスレッドを作成できません。(エラー番号 %d) もしも使用可能メモリーの不足でなければ、OS依存のバグである可能性があります。"
        kor "새로운 쓰레드를 만들 수 없습니다.(에러번호 %d). 만약 여유메모리가 있다면 OS-dependent버그 의 메뉴얼 부분을 찾아보시오."
        nor "Can't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bug"
        norwegian-ny "Can't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bug"
        pol "Can't create a new thread (errno %d); if you are not out of available memory you can consult the manual for any possible OS dependent bug"
        por "Não pode criar uma nova 'thread' (erro no. %d). Se você não estiver sem memória disponível, você pode consultar o manual sobre um possível 'bug' dependente do sistema operacional"
        rum "Nu pot crea un thread nou (Eroare %d). Daca mai aveti memorie disponibila in sistem, puteti consulta manualul - ar putea exista un potential bug in legatura cu sistemul de operare"
        rus "Невозможно создать новый поток (ошибка %d). Если это не ситуация, связанная с нехваткой памяти, то вам следует изучить документацию на предмет описания возможной ошибки работы в конкретной ОС"
        serbian "Ne mogu da kreiram novi thread (errno %d). Ako imate još slobodne memorije, trebali biste da pogledate u priručniku da li je ovo specifična greška vašeg operativnog sistema"
        spa "No puedo crear un nuevo thread (errno %d). Si tu está con falta de memoria disponible, tu puedes consultar el Manual para posibles problemas con SO"
        swe "Kan inte skapa en ny tråd (errno %d)"
        ukr "Не можу створити нову гілку (помилка %d). Якщо ви не використали усю пам'ять, то прочитайте документацію до вашої ОС - можливо це помилка ОС"
ER_WRONG_VALUE_COUNT_ON_ROW 21S01
        cze "Počet sloupců neodpovídá počtu hodnot na řádku %ld"
        dan "Kolonne antallet stemmer ikke overens med antallet af værdier i post %ld"
        nla "Kolom aantal komt niet overeen met waarde aantal in rij %ld"
        eng "Column count doesn't match value count at row %ld"
        est "Tulpade hulk erineb väärtuste hulgast real %ld"
        ger "Anzahl der Felder stimmt nicht mit der Anzahl der Werte in Zeile %ld überein"
        hun "Az oszlopban talalhato ertek nem egyezik meg a %ld sorban szamitott ertekkel"
        ita "Il numero delle colonne non corrisponde al conteggio alla riga %ld"
        jpn "%ld 行目で、列の数が値の数と一致しません。"
        kor "Row %ld에서 칼럼 카운트와 value 카운터와 일치하지 않습니다."
        por "Contagem de colunas não confere com a contagem de valores na linha %ld"
        rum "Numarul de coloane nu corespunde cu numarul de valori la linia %ld"
        rus "Количество столбцов не совпадает с количеством значений в записи %ld"
        serbian "Broj kolona ne odgovara broju vrednosti u slogu %ld"
        spa "El número de columnas no corresponde al número en la línea %ld"
        swe "Antalet kolumner motsvarar inte antalet värden på rad: %ld"
        ukr "Кількість стовбців не співпадає з кількістю значень у строці %ld"
ER_CANT_REOPEN_TABLE
        cze "Nemohu znovuotevřít tabulku: '%-.192s"
        dan "Kan ikke genåbne tabel '%-.192s"
        nla "Kan tabel niet opnieuw openen: '%-.192s"
        eng "Can't reopen table: '%-.192s'"
        est "Ei suuda taasavada tabelit '%-.192s'"
        fre "Impossible de réouvrir la table: '%-.192s"
        ger "Kann Tabelle'%-.192s' nicht erneut öffnen"
        hun "Nem lehet ujra-megnyitni a tablat: '%-.192s"
        ita "Impossibile riaprire la tabella: '%-.192s'"
        jpn "表を再オープンできません。: '%-.192s'"
        kor "테이블을 다시 열수 없군요: '%-.192s"
        nor "Can't reopen table: '%-.192s"
        norwegian-ny "Can't reopen table: '%-.192s"
        pol "Can't reopen table: '%-.192s"
        por "Não pode reabrir a tabela '%-.192s"
        rum "Nu pot redeschide tabela: '%-.192s'"
        rus "Невозможно заново открыть таблицу '%-.192s'"
        serbian "Ne mogu da ponovo otvorim tabelu '%-.192s'"
        slo "Can't reopen table: '%-.192s"
        spa "No puedo reabrir tabla: '%-.192s"
        swe "Kunde inte stänga och öppna tabell '%-.192s"
        ukr "Не можу перевідкрити таблицю: '%-.192s'"
ER_INVALID_USE_OF_NULL 22004
        cze "Neplatné užití hodnoty NULL"
        dan "Forkert brug af nulværdi (NULL)"
        nla "Foutief gebruik van de NULL waarde"
        eng "Invalid use of NULL value"
        est "NULL väärtuse väärkasutus"
        fre "Utilisation incorrecte de la valeur NULL"
        ger "Unerlaubte Verwendung eines NULL-Werts"
        hun "A NULL ervenytelen hasznalata"
        ita "Uso scorretto del valore NULL"
        jpn "NULL 値の使用方法が不適切です。"
        kor "NULL 값을 잘못 사용하셨군요..."
        por "Uso inválido do valor NULL"
        rum "Folosirea unei value NULL e invalida"
        rus "Неправильное использование величины NULL"
        serbian "Pogrešna upotreba vrednosti NULL"
        spa "Invalido uso de valor NULL"
        swe "Felaktig använding av NULL"
        ukr "Хибне використання значення NULL"
ER_REGEXP_ERROR 42000
        cze "Regulární výraz vrátil chybu '%-.64s'"
        dan "Fik fejl '%-.64s' fra regexp"
        nla "Fout '%-.64s' ontvangen van regexp"
        eng "Got error '%-.64s' from regexp"
        est "regexp tagastas vea '%-.64s'"
        fre "Erreur '%-.64s' provenant de regexp"
        ger "regexp lieferte Fehler '%-.64s'"
        hun "'%-.64s' hiba a regularis kifejezes hasznalata soran (regexp)"
        ita "Errore '%-.64s' da regexp"
        jpn "regexp がエラー '%-.64s' を返しました。"
        kor "regexp에서 '%-.64s'가 났습니다."
        por "Obteve erro '%-.64s' em regexp"
        rum "Eroarea '%-.64s' obtinuta din expresia regulara (regexp)"
        rus "Получена ошибка '%-.64s' от регулярного выражения"
        serbian "Funkcija regexp je vratila grešku '%-.64s'"
        spa "Obtenido error '%-.64s' de regexp"
        swe "Fick fel '%-.64s' från REGEXP"
        ukr "Отримано помилку '%-.64s' від регулярного виразу"

# When using this error code, please use ER(ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2)
# for the message string.
ER_MIX_OF_GROUP_FUNC_AND_FIELDS 42000
        cze "Pokud není žádná GROUP BY klauzule, není dovoleno současné použití GROUP položek (MIN(),MAX(),COUNT()...) s ne GROUP položkami"
        dan "Sammenblanding af GROUP kolonner (MIN(),MAX(),COUNT()...) uden GROUP kolonner er ikke tilladt, hvis der ikke er noget GROUP BY prædikat"
        nla "Het mixen van GROUP kolommen (MIN(),MAX(),COUNT()...) met no-GROUP kolommen is foutief indien er geen GROUP BY clausule is"
        eng "Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause"
        est "GROUP tulpade (MIN(),MAX(),COUNT()...) kooskasutamine tavaliste tulpadega ilma GROUP BY klauslita ei ole lubatud"
        fre "Mélanger les colonnes GROUP (MIN(),MAX(),COUNT()...) avec des colonnes normales est interdit s'il n'y a pas de clause GROUP BY"
        ger "Das Vermischen von GROUP-Feldern (MIN(),MAX(),COUNT()...) mit Nicht-GROUP-Feldern ist nicht zulässig, wenn keine GROUP-BY-Klausel vorhanden ist"
        hun "A GROUP mezok (MIN(),MAX(),COUNT()...) kevert hasznalata nem lehetseges GROUP BY hivatkozas nelkul"
        ita "Il mescolare funzioni di aggregazione (MIN(),MAX(),COUNT()...) e non e` illegale se non c'e` una clausula GROUP BY"
        jpn "GROUP BY句が無い場合、集計関数(MIN(),MAX(),COUNT(),...)と通常の列を同時に使用できません。"
        kor "Mixing of GROUP 칼럼s (MIN(),MAX(),COUNT(),...) with no GROUP 칼럼s is illegal if there is no GROUP BY clause"
        por "Mistura de colunas agrupadas (com MIN(), MAX(), COUNT(), ...) com colunas não agrupadas é ilegal, se não existir uma cláusula de agrupamento (cláusula GROUP BY)"
        rum "Amestecarea de coloane GROUP (MIN(),MAX(),COUNT()...) fara coloane GROUP este ilegala daca nu exista o clauza GROUP BY"
        rus "Одновременное использование сгруппированных (GROUP) столбцов (MIN(),MAX(),COUNT(),...) с несгруппированными столбцами является некорректным, если в выражении есть GROUP BY"
        serbian "Upotreba agregatnih funkcija (MIN(),MAX(),COUNT()...) bez 'GROUP' kolona je pogrešna ako ne postoji 'GROUP BY' iskaz"
        spa "Mezcla de columnas GROUP (MIN(),MAX(),COUNT()...) con no GROUP columnas es ilegal si no hat la clausula GROUP BY"
        swe "Man får ha både GROUP-kolumner (MIN(),MAX(),COUNT()...) och fält i en fråga om man inte har en GROUP BY-del"
        ukr "Змішування GROUP стовбців (MIN(),MAX(),COUNT()...) з не GROUP стовбцями є забороненим, якщо не має GROUP BY"
ER_NONEXISTING_GRANT 42000
        cze "Neexistuje odpovídající grant pro uživatele '%-.48s' na stroji '%-.255s'"
        dan "Denne tilladelse findes ikke for brugeren '%-.48s' på vært '%-.255s'"
        nla "Deze toegang (GRANT) is niet toegekend voor gebruiker '%-.48s' op host '%-.255s'"
        eng "There is no such grant defined for user '%-.48s' on host '%-.255s'"
        est "Sellist õigust ei ole defineeritud kasutajale '%-.48s' masinast '%-.255s'"
        fre "Un tel droit n'est pas défini pour l'utilisateur '%-.48s' sur l'hôte '%-.255s'"
        ger "Für Benutzer '%-.48s' auf Host '%-.255s' gibt es keine solche Berechtigung"
        hun "A '%-.48s' felhasznalonak nincs ilyen joga a '%-.255s' host-on"
        ita "GRANT non definita per l'utente '%-.48s' dalla macchina '%-.255s'"
        jpn "ユーザー '%-.48s' (ホスト '%-.255s' 上) は許可されていません。"
        kor "사용자 '%-.48s' (호스트 '%-.255s')를 위하여 정의된 그런 승인은 없습니다."
        por "Não existe tal permissão (grant) definida para o usuário '%-.48s' no 'host' '%-.255s'"
        rum "Nu exista un astfel de grant definit pentru utilzatorul '%-.48s' de pe host-ul '%-.255s'"
        rus "Такие права не определены для пользователя '%-.48s' на хосте '%-.255s'"
        serbian "Ne postoji odobrenje za pristup korisniku '%-.48s' na host-u '%-.255s'"
        spa "No existe permiso definido para usuario '%-.48s' en el servidor '%-.255s'"
        swe "Det finns inget privilegium definierat för användare '%-.48s' på '%-.255s'"
        ukr "Повноважень не визначено для користувача '%-.48s' з хосту '%-.255s'"
ER_TABLEACCESS_DENIED_ERROR 42000
        cze "%-.128s příkaz nepřístupný pro uživatele: '%-.48s'@'%-.64s' pro tabulku '%-.64s'"
        dan "%-.128s-kommandoen er ikke tilladt for brugeren '%-.48s'@'%-.64s' for tabellen '%-.64s'"
        nla "%-.128s commando geweigerd voor gebruiker: '%-.48s'@'%-.64s' voor tabel '%-.64s'"
        eng "%-.128s command denied to user '%-.48s'@'%-.64s' for table '%-.64s'"
        est "%-.128s käsk ei ole lubatud kasutajale '%-.48s'@'%-.64s' tabelis '%-.64s'"
        fre "La commande '%-.128s' est interdite à l'utilisateur: '%-.48s'@'@%-.64s' sur la table '%-.64s'"
        ger "%-.128s Befehl nicht erlaubt für Benutzer '%-.48s'@'%-.64s' auf Tabelle '%-.64s'"
        hun "%-.128s parancs a '%-.48s'@'%-.64s' felhasznalo szamara nem engedelyezett a '%-.64s' tablaban"
        ita "Comando %-.128s negato per l'utente: '%-.48s'@'%-.64s' sulla tabella '%-.64s'"
        jpn "コマンド %-.128s は ユーザー '%-.48s'@'%-.64s' の表 '%-.64s' の使用に関して許可されていません。"
        kor "'%-.128s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 테이블 '%-.64s'"
        por "Comando '%-.128s' negado para o usuário '%-.48s'@'%-.64s' na tabela '%-.64s'"
        rum "Comanda %-.128s interzisa utilizatorului: '%-.48s'@'%-.64s' pentru tabela '%-.64s'"
        rus "Команда %-.128s запрещена пользователю '%-.48s'@'%-.64s' для таблицы '%-.64s'"
        serbian "%-.128s komanda zabranjena za korisnika '%-.48s'@'%-.64s' za tabelu '%-.64s'"
        spa "%-.128s comando negado para usuario: '%-.48s'@'%-.64s' para tabla '%-.64s'"
        swe "%-.128s ej tillåtet för '%-.48s'@'%-.64s' för tabell '%-.64s'"
        ukr "%-.128s команда заборонена користувачу: '%-.48s'@'%-.64s' у таблиці '%-.64s'"
ER_COLUMNACCESS_DENIED_ERROR 42000
        cze "%-.16s příkaz nepřístupný pro uživatele: '%-.48s'@'%-.64s' pro sloupec '%-.192s' v tabulce '%-.192s'"
        dan "%-.16s-kommandoen er ikke tilladt for brugeren '%-.48s'@'%-.64s' for kolonne '%-.192s' in tabellen '%-.192s'"
        nla "%-.16s commando geweigerd voor gebruiker: '%-.48s'@'%-.64s' voor kolom '%-.192s' in tabel '%-.192s'"
        eng "%-.16s command denied to user '%-.48s'@'%-.64s' for column '%-.192s' in table '%-.192s'"
        est "%-.16s käsk ei ole lubatud kasutajale '%-.48s'@'%-.64s' tulbale '%-.192s' tabelis '%-.192s'"
        fre "La commande '%-.16s' est interdite à l'utilisateur: '%-.48s'@'@%-.64s' sur la colonne '%-.192s' de la table '%-.192s'"
        ger "%-.16s Befehl nicht erlaubt für Benutzer '%-.48s'@'%-.64s' und Feld '%-.192s' in Tabelle '%-.192s'"
        hun "%-.16s parancs a '%-.48s'@'%-.64s' felhasznalo szamara nem engedelyezett a '%-.192s' mezo eseten a '%-.192s' tablaban"
        ita "Comando %-.16s negato per l'utente: '%-.48s'@'%-.64s' sulla colonna '%-.192s' della tabella '%-.192s'"
        jpn "コマンド %-.16s は ユーザー '%-.48s'@'%-.64s'\n の列 '%-.192s'(表 '%-.192s') の利用に関して許可されていません。"
        kor "'%-.16s' 명령은 다음 사용자에게 거부되었습니다. : '%-.48s'@'%-.64s' for 칼럼 '%-.192s' in 테이블 '%-.192s'"
        por "Comando '%-.16s' negado para o usuário '%-.48s'@'%-.64s' na coluna '%-.192s', na tabela '%-.192s'"
        rum "Comanda %-.16s interzisa utilizatorului: '%-.48s'@'%-.64s' pentru coloana '%-.192s' in tabela '%-.192s'"
        rus "Команда %-.16s запрещена пользователю '%-.48s'@'%-.64s' для столбца '%-.192s' в таблице '%-.192s'"
        serbian "%-.16s komanda zabranjena za korisnika '%-.48s'@'%-.64s' za kolonu '%-.192s' iz tabele '%-.192s'"
        spa "%-.16s comando negado para usuario: '%-.48s'@'%-.64s' para columna '%-.192s' en la tabla '%-.192s'"
        swe "%-.16s ej tillåtet för '%-.48s'@'%-.64s' för kolumn '%-.192s' i tabell '%-.192s'"
        ukr "%-.16s команда заборонена користувачу: '%-.48s'@'%-.64s' для стовбця '%-.192s' у таблиці '%-.192s'"
ER_ILLEGAL_GRANT_FOR_TABLE 42000
        cze "Neplatný příkaz GRANT/REVOKE. Prosím, přečtěte si v manuálu, jaká privilegia je možné použít."
        dan "Forkert GRANT/REVOKE kommando. Se i brugervejledningen hvilke privilegier der kan specificeres."
        nla "Foutief GRANT/REVOKE commando. Raadpleeg de handleiding welke priveleges gebruikt kunnen worden."
        eng "Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used"
        est "Vigane GRANT/REVOKE käsk. Tutvu kasutajajuhendiga"
        fre "Commande GRANT/REVOKE incorrecte. Consultez le manuel."
        ger "Unzulässiger GRANT- oder REVOKE-Befehl. Verfügbare Berechtigungen sind im Handbuch aufgeführt"
        greek "Illegal GRANT/REVOKE command; please consult the manual to see which privileges can be used."
        hun "Ervenytelen GRANT/REVOKE parancs. Kerem, nezze meg a kezikonyvben, milyen jogok lehetsegesek"
        ita "Comando GRANT/REVOKE illegale. Prego consultare il manuale per sapere quali privilegi possono essere usati."
        jpn "不正な GRANT/REVOKE コマンドです。どの権限で利用可能かはマニュアルを参照して下さい。"
        kor "잘못된 GRANT/REVOKE 명령. 어떤 권리와 승인이 사용되어 질 수 있는지 메뉴얼을 보시오."
        nor "Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used."
        norwegian-ny "Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used."
        pol "Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used."
        por "Comando GRANT/REVOKE ilegal. Por favor consulte no manual quais privilégios podem ser usados."
        rum "Comanda GRANT/REVOKE ilegala. Consultati manualul in privinta privilegiilor ce pot fi folosite."
        rus "Неверная команда GRANT или REVOKE. Обратитесь к документации, чтобы выяснить, какие привилегии можно использовать"
        serbian "Pogrešna 'GRANT' odnosno 'REVOKE' komanda. Molim Vas pogledajte u priručniku koje vrednosti mogu biti upotrebljene."
        slo "Illegal GRANT/REVOKE command; please consult the manual to see which privleges can be used."
        spa "Ilegal comando GRANT/REVOKE. Por favor consulte el manual para cuales permisos pueden ser usados."
        swe "Felaktigt GRANT-privilegium använt"
        ukr "Хибна GRANT/REVOKE команда; прочитайте документацію стосовно того, які права можна використовувати"
ER_GRANT_WRONG_HOST_OR_USER 42000
        cze "Argument příkazu GRANT uživatel nebo stroj je příliš dlouhý"
        dan "Værts- eller brugernavn for langt til GRANT"
        nla "De host of gebruiker parameter voor GRANT is te lang"
        eng "The host or user argument to GRANT is too long"
        est "Masina või kasutaja nimi GRANT lauses on liiga pikk"
        fre "L'hôte ou l'utilisateur donné en argument à GRANT est trop long"
        ger "Das Host- oder User-Argument für GRANT ist zu lang"
        hun "A host vagy felhasznalo argumentuma tul hosszu a GRANT parancsban"
        ita "L'argomento host o utente per la GRANT e` troppo lungo"
        jpn "GRANTコマンドへの、ホスト名やユーザー名が長すぎます。"
        kor "승인(GRANT)을 위하여 사용한 사용자나 호스트의 값들이 너무 깁니다."
        por "Argumento de 'host' ou de usuário para o GRANT é longo demais"
        rum "Argumentul host-ului sau utilizatorului pentru GRANT e prea lung"
        rus "Слишком длинное имя пользователя/хоста для GRANT"
        serbian "Argument 'host' ili 'korisnik' prosleđen komandi 'GRANT' je predugačak"
        spa "El argumento para servidor o usuario para GRANT es demasiado grande"
        swe "Felaktigt maskinnamn eller användarnamn använt med GRANT"
        ukr "Аргумент host або user для GRANT задовгий"
ER_NO_SUCH_TABLE 42S02
        cze "Tabulka '%-.192s.%-.192s' neexistuje"
        dan "Tabellen '%-.192s.%-.192s' eksisterer ikke"
        nla "Tabel '%-.192s.%-.192s' bestaat niet"
        eng "Table '%-.192s.%-.192s' doesn't exist"
        est "Tabelit '%-.192s.%-.192s' ei eksisteeri"
        fre "La table '%-.192s.%-.192s' n'existe pas"
        ger "Tabelle '%-.192s.%-.192s' existiert nicht"
        hun "A '%-.192s.%-.192s' tabla nem letezik"
        ita "La tabella '%-.192s.%-.192s' non esiste"
        jpn "表 '%-.192s.%-.192s' は存在しません。"
        kor "테이블 '%-.192s.%-.192s' 는 존재하지 않습니다."
        nor "Table '%-.192s.%-.192s' doesn't exist"
        norwegian-ny "Table '%-.192s.%-.192s' doesn't exist"
        pol "Table '%-.192s.%-.192s' doesn't exist"
        por "Tabela '%-.192s.%-.192s' não existe"
        rum "Tabela '%-.192s.%-.192s' nu exista"
        rus "Таблица '%-.192s.%-.192s' не существует"
        serbian "Tabela '%-.192s.%-.192s' ne postoji"
        slo "Table '%-.192s.%-.192s' doesn't exist"
        spa "Tabla '%-.192s.%-.192s' no existe"
        swe "Det finns ingen tabell som heter '%-.192s.%-.192s'"
        ukr "Таблиця '%-.192s.%-.192s' не існує"
ER_NONEXISTING_TABLE_GRANT 42000
        cze "Neexistuje odpovídající grant pro uživatele '%-.48s' na stroji '%-.255s' pro tabulku '%-.192s'"
        dan "Denne tilladelse eksisterer ikke for brugeren '%-.48s' på vært '%-.255s' for tabellen '%-.192s'"
        nla "Deze toegang (GRANT) is niet toegekend voor gebruiker '%-.48s' op host '%-.255s' op tabel '%-.192s'"
        eng "There is no such grant defined for user '%-.48s' on host '%-.255s' on table '%-.192s'"
        est "Sellist õigust ei ole defineeritud kasutajale '%-.48s' masinast '%-.255s' tabelile '%-.192s'"
        fre "Un tel droit n'est pas défini pour l'utilisateur '%-.48s' sur l'hôte '%-.255s' sur la table '%-.192s'"
        ger "Eine solche Berechtigung ist für User '%-.48s' auf Host '%-.255s' an Tabelle '%-.192s' nicht definiert"
        hun "A '%-.48s' felhasznalo szamara a '%-.255s' host '%-.192s' tablajaban ez a parancs nem engedelyezett"
        ita "GRANT non definita per l'utente '%-.48s' dalla macchina '%-.255s' sulla tabella '%-.192s'"
        jpn "ユーザー '%-.48s' (ホスト '%-.255s' 上) の表 '%-.192s' への権限は定義されていません。"
        kor "사용자 '%-.48s'(호스트 '%-.255s')는 테이블 '%-.192s'를 사용하기 위하여 정의된 승인은 없습니다. "
        por "Não existe tal permissão (grant) definido para o usuário '%-.48s' no 'host' '%-.255s', na tabela '%-.192s'"
        rum "Nu exista un astfel de privilegiu (grant) definit pentru utilizatorul '%-.48s' de pe host-ul '%-.255s' pentru tabela '%-.192s'"
        rus "Такие права не определены для пользователя '%-.48s' на компьютере '%-.255s' для таблицы '%-.192s'"
        serbian "Ne postoji odobrenje za pristup korisniku '%-.48s' na host-u '%-.255s' tabeli '%-.192s'"
        spa "No existe tal permiso definido para usuario '%-.48s' en el servidor '%-.255s' en la tabla '%-.192s'"
        swe "Det finns inget privilegium definierat för användare '%-.48s' på '%-.255s' för tabell '%-.192s'"
        ukr "Повноважень не визначено для користувача '%-.48s' з хосту '%-.255s' для таблиці '%-.192s'"
ER_NOT_ALLOWED_COMMAND 42000
        cze "Použitý příkaz není v této verzi MySQL povolen"
        dan "Den brugte kommando er ikke tilladt med denne udgave af MySQL"
        nla "Het used commando is niet toegestaan in deze MySQL versie"
        eng "The used command is not allowed with this MySQL version"
        est "Antud käsk ei ole lubatud käesolevas MySQL versioonis"
        fre "Cette commande n'existe pas dans cette version de MySQL"
        ger "Der verwendete Befehl ist in dieser MySQL-Version nicht zulässig"
        hun "A hasznalt parancs nem engedelyezett ebben a MySQL verzioban"
        ita "Il comando utilizzato non e` supportato in questa versione di MySQL"
        jpn "このMySQLバージョンでは利用できないコマンドです。"
        kor "사용된 명령은 현재의 MySQL 버젼에서는 이용되지 않습니다."
        por "Comando usado não é permitido para esta versão do MySQL"
        rum "Comanda folosita nu este permisa pentru aceasta versiune de MySQL"
        rus "Эта команда не допускается в данной  версии MySQL"
        serbian "Upotrebljena komanda nije dozvoljena sa ovom verzijom MySQL servera"
        spa "El comando usado no es permitido con esta versión de MySQL"
        swe "Du kan inte använda detta kommando med denna MySQL version"
        ukr "Використовувана команда не дозволена у цій версії MySQL"
ER_SYNTAX_ERROR 42000
        cze "Vaše syntaxe je nějaká divná"
        dan "Der er en fejl i SQL syntaksen"
        nla "Er is iets fout in de gebruikte syntax"
        eng "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use"
        est "Viga SQL süntaksis"
        fre "Erreur de syntaxe"
        ger "Fehler in der SQL-Syntax. Bitte die korrekte Syntax im Handbuch nachschlagen"
        greek "You have an error in your SQL syntax"
        hun "Szintaktikai hiba"
        ita "Errore di sintassi nella query SQL"
        jpn "SQL構文エラーです。バージョンに対応するマニュアルを参照して正しい構文を確認してください。"
        kor "SQL 구문에 오류가 있습니다."
        nor "Something is wrong in your syntax"
        norwegian-ny "Something is wrong in your syntax"
        pol "Something is wrong in your syntax"
        por "Você tem um erro de sintaxe no seu SQL"
        rum "Aveti o eroare in sintaxa RSQL"
        rus "У вас ошибка в запросе. Изучите документацию по используемой версии MySQL на предмет корректного синтаксиса"
        serbian "Imate grešku u vašoj SQL sintaksi"
        slo "Something is wrong in your syntax"
        spa "Algo está equivocado en su sintax"
        swe "Du har något fel i din syntax"
        ukr "У вас помилка у синтаксисі SQL"
OBSOLETE_ER_UNUSED1
        eng "Delayed insert thread couldn't get requested lock for table %-.192s"
OBSOLETE_ER_UNUSED2
        eng "Too many delayed threads in use"
ER_ABORTING_CONNECTION 08S01
        cze "Zrušeno spojení %ld do databáze: '%-.192s' uživatel: '%-.48s' (%-.64s)"
        dan "Afbrudt forbindelse %ld til database: '%-.192s' bruger: '%-.48s' (%-.64s)"
        nla "Afgebroken verbinding %ld naar db: '%-.192s' gebruiker: '%-.48s' (%-.64s)"
        eng "Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)"
        est "Ühendus katkestatud %ld andmebaasile: '%-.192s' kasutajale: '%-.48s' (%-.64s)"
        fre "Connection %ld avortée vers la bd: '%-.192s' utilisateur: '%-.48s' (%-.64s)"
        ger "Abbruch der Verbindung %ld zur Datenbank '%-.192s'. Benutzer: '%-.48s' (%-.64s)"
        hun "Megszakitott kapcsolat %ld db: '%-.192s' adatbazishoz, felhasznalo: '%-.48s' (%-.64s)"
        ita "Interrotta la connessione %ld al db: '%-.192s' utente: '%-.48s' (%-.64s)"
        jpn "接続 %ld が中断されました。データベース: '%-.192s' ユーザー: '%-.48s' (%-.64s)"
        kor "데이타베이스 접속을 위한 연결 %ld가 중단됨 : '%-.192s' 사용자: '%-.48s' (%-.64s)"
        nor "Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)"
        norwegian-ny "Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)"
        pol "Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)"
        por "Conexão %ld abortou para o banco de dados '%-.192s' - usuário '%-.48s' (%-.64s)"
        rum "Conectie terminata %ld la baza de date: '%-.192s' utilizator: '%-.48s' (%-.64s)"
        rus "Прервано соединение %ld к базе данных '%-.192s' пользователя '%-.48s' (%-.64s)"
        serbian "Prekinuta konekcija broj %ld ka bazi: '%-.192s' korisnik je bio: '%-.48s' (%-.64s)"
        slo "Aborted connection %ld to db: '%-.192s' user: '%-.48s' (%-.64s)"
        spa "Conexión abortada %ld para db: '%-.192s' usuario: '%-.48s' (%-.64s)"
        swe "Avbröt länken för tråd %ld till db '%-.192s', användare '%-.48s' (%-.64s)"
        ukr "Перервано з'єднання %ld до бази данних: '%-.192s' користувача: '%-.48s' (%-.64s)"
ER_NET_PACKET_TOO_LARGE 08S01
        cze "Zjištěn příchozí packet delší než 'max_allowed_packet'"
        dan "Modtog en datapakke som var større end 'max_allowed_packet'"
        nla "Groter pakket ontvangen dan 'max_allowed_packet'"
        eng "Got a packet bigger than 'max_allowed_packet' bytes"
        est "Saabus suurem pakett kui lubatud 'max_allowed_packet' muutujaga"
        fre "Paquet plus grand que 'max_allowed_packet' reçu"
        ger "Empfangenes Paket ist größer als 'max_allowed_packet' Bytes"
        hun "A kapott csomag nagyobb, mint a maximalisan engedelyezett: 'max_allowed_packet'"
        ita "Ricevuto un pacchetto piu` grande di 'max_allowed_packet'"
        jpn "'max_allowed_packet'よりも大きなパケットを受信しました。"
        kor "'max_allowed_packet'보다 더큰 패킷을 받았습니다."
        por "Obteve um pacote maior do que a taxa máxima de pacotes definida (max_allowed_packet)"
        rum "Un packet mai mare decit 'max_allowed_packet' a fost primit"
        rus "Полученный пакет больше, чем 'max_allowed_packet'"
        serbian "Primio sam mrežni paket veći od definisane vrednosti 'max_allowed_packet'"
        spa "Obtenido un paquete mayor que 'max_allowed_packet'"
        swe "Kommunkationspaketet är större än 'max_allowed_packet'"
        ukr "Отримано пакет більший ніж max_allowed_packet"
ER_NET_READ_ERROR_FROM_PIPE 08S01
        cze "Zjištěna chyba při čtení z roury spojení"
        dan "Fik læsefejl fra forbindelse (connection pipe)"
        nla "Kreeg leesfout van de verbindings pipe"
        eng "Got a read error from the connection pipe"
        est "Viga ühendustoru lugemisel"
        fre "Erreur de lecture reçue du pipe de connexion"
        ger "Lese-Fehler bei einer Verbindungs-Pipe"
        hun "Olvasasi hiba a kapcsolat soran"
        ita "Rilevato un errore di lettura dalla pipe di connessione"
        jpn "接続パイプの読み込みエラーです。"
        kor "연결 파이프로부터 에러가 발생하였습니다."
        por "Obteve um erro de leitura no 'pipe' da conexão"
        rum "Eroare la citire din cauza lui 'connection pipe'"
        rus "Получена ошибка чтения от потока соединения (connection pipe)"
        serbian "Greška pri čitanju podataka sa pipe-a"
        spa "Obtenido un error de lectura de la conexión pipe"
        swe "Fick läsfel från klienten vid läsning från 'PIPE'"
        ukr "Отримано помилку читання з комунікаційного каналу"
ER_NET_FCNTL_ERROR 08S01
        cze "Zjištěna chyba fcntl()"
        dan "Fik fejlmeddelelse fra fcntl()"
        nla "Kreeg fout van fcntl()"
        eng "Got an error from fcntl()"
        est "fcntl() tagastas vea"
        fre "Erreur reçue de fcntl() "
        ger "fcntl() lieferte einen Fehler"
        hun "Hiba a fcntl() fuggvenyben"
        ita "Rilevato un errore da fcntl()"
        jpn "fcntl()がエラーを返しました。"
        kor "fcntl() 함수로부터 에러가 발생하였습니다."
        por "Obteve um erro em fcntl()"
        rum "Eroare obtinuta de la fcntl()"
        rus "Получена ошибка от fcntl()"
        serbian "Greška pri izvršavanju funkcije fcntl()"
        spa "Obtenido un error de fcntl()"
        swe "Fick fatalt fel från 'fcntl()'"
        ukr "Отримано помилкку від fcntl()"
ER_NET_PACKETS_OUT_OF_ORDER 08S01
        cze "Příchozí packety v chybném pořadí"
        dan "Modtog ikke datapakker i korrekt rækkefølge"
        nla "Pakketten in verkeerde volgorde ontvangen"
        eng "Got packets out of order"
        est "Paketid saabusid vales järjekorras"
        fre "Paquets reçus dans le désordre"
        ger "Pakete nicht in der richtigen Reihenfolge empfangen"
        hun "Helytelen sorrendben erkezett adatcsomagok"
        ita "Ricevuti pacchetti non in ordine"
        jpn "不正な順序のパケットを受信しました。"
        kor "순서가 맞지않는 패킷을 받았습니다."
        por "Obteve pacotes fora de ordem"
        rum "Packets care nu sint ordonati au fost gasiti"
        rus "Пакеты получены в неверном порядке"
        serbian "Primio sam mrežne pakete van reda"
        spa "Obtenido paquetes desordenados"
        swe "Kommunikationspaketen kom i fel ordning"
        ukr "Отримано пакети у неналежному порядку"
ER_NET_UNCOMPRESS_ERROR 08S01
        cze "Nemohu rozkomprimovat komunikační packet"
        dan "Kunne ikke dekomprimere kommunikations-pakke (communication packet)"
        nla "Communicatiepakket kon niet worden gedecomprimeerd"
        eng "Couldn't uncompress communication packet"
        est "Viga andmepaketi lahtipakkimisel"
        fre "Impossible de décompresser le paquet reçu"
        ger "Kommunikationspaket lässt sich nicht entpacken"
        hun "A kommunikacios adatcsomagok nem tomorithetok ki"
        ita "Impossibile scompattare i pacchetti di comunicazione"
        jpn "圧縮パケットの展開ができませんでした。"
        kor "통신 패킷의 압축해제를 할 수 없었습니다."
        por "Não conseguiu descomprimir pacote de comunicação"
        rum "Nu s-a putut decompresa pachetul de comunicatie (communication packet)"
        rus "Невозможно распаковать пакет, полученный через коммуникационный протокол"
        serbian "Ne mogu da dekompresujem mrežne pakete"
        spa "No puedo descomprimir paquetes de comunicación"
        swe "Kunde inte packa up kommunikationspaketet"
        ukr "Не можу декомпресувати комунікаційний пакет"
ER_NET_READ_ERROR 08S01
        cze "Zjištěna chyba při čtení komunikačního packetu"
        dan "Fik fejlmeddelelse ved læsning af kommunikations-pakker (communication packets)"
        nla "Fout bij het lezen van communicatiepakketten"
        eng "Got an error reading communication packets"
        est "Viga andmepaketi lugemisel"
        fre "Erreur de lecture des paquets reçus"
        ger "Fehler beim Lesen eines Kommunikationspakets"
        hun "HIba a kommunikacios adatcsomagok olvasasa soran"
        ita "Rilevato un errore ricevendo i pacchetti di comunicazione"
        jpn "パケットの受信でエラーが発生しました。"
        kor "통신 패킷을 읽는 중 오류가 발생하였습니다."
        por "Obteve um erro na leitura de pacotes de comunicação"
        rum "Eroare obtinuta citind pachetele de comunicatie (communication packets)"
        rus "Получена ошибка в процессе получения пакета через коммуникационный протокол "
        serbian "Greška pri primanju mrežnih paketa"
        spa "Obtenido un error leyendo paquetes de comunicación"
        swe "Fick ett fel vid läsning från klienten"
        ukr "Отримано помилку читання комунікаційних пакетів"
ER_NET_READ_INTERRUPTED 08S01
        cze "Zjištěn timeout při čtení komunikačního packetu"
        dan "Timeout-fejl ved læsning af kommunukations-pakker (communication packets)"
        nla "Timeout bij het lezen van communicatiepakketten"
        eng "Got timeout reading communication packets"
        est "Kontrollaja ületamine andmepakettide lugemisel"
        fre "Timeout en lecture des paquets reçus"
        ger "Zeitüberschreitung beim Lesen eines Kommunikationspakets"
        hun "Idotullepes a kommunikacios adatcsomagok olvasasa soran"
        ita "Rilevato un timeout ricevendo i pacchetti di comunicazione"
        jpn "パケットの受信でタイムアウトが発生しました。"
        kor "통신 패킷을 읽는 중 timeout이 발생하였습니다."
        por "Obteve expiração de tempo (timeout) na leitura de pacotes de comunicação"
        rum "Timeout obtinut citind pachetele de comunicatie (communication packets)"
        rus "Получен таймаут ожидания пакета через коммуникационный протокол "
        serbian "Vremenski limit za čitanje mrežnih paketa je istekao"
        spa "Obtenido timeout leyendo paquetes de comunicación"
        swe "Fick 'timeout' vid läsning från klienten"
        ukr "Отримано затримку читання комунікаційних пакетів"
ER_NET_ERROR_ON_WRITE 08S01
        cze "Zjištěna chyba při zápisu komunikačního packetu"
        dan "Fik fejlmeddelelse ved skrivning af kommunukations-pakker (communication packets)"
        nla "Fout bij het schrijven van communicatiepakketten"
        eng "Got an error writing communication packets"
        est "Viga andmepaketi kirjutamisel"
        fre "Erreur d'écriture des paquets envoyés"
        ger "Fehler beim Schreiben eines Kommunikationspakets"
        hun "Hiba a kommunikacios csomagok irasa soran"
        ita "Rilevato un errore inviando i pacchetti di comunicazione"
        jpn "パケットの送信でエラーが発生しました。"
        kor "통신 패킷을 기록하는 중 오류가 발생하였습니다."
        por "Obteve um erro na escrita de pacotes de comunicação"
        rum "Eroare in scrierea pachetelor de comunicatie (communication packets)"
        rus "Получена ошибка при передаче пакета через коммуникационный протокол "
        serbian "Greška pri slanju mrežnih paketa"
        spa "Obtenido un error de escribiendo paquetes de comunicación"
        swe "Fick ett fel vid skrivning till klienten"
        ukr "Отримано помилку запису комунікаційних пакетів"
ER_NET_WRITE_INTERRUPTED 08S01
        cze "Zjištěn timeout při zápisu komunikačního packetu"
        dan "Timeout-fejl ved skrivning af kommunukations-pakker (communication packets)"
        nla "Timeout bij het schrijven van communicatiepakketten"
        eng "Got timeout writing communication packets"
        est "Kontrollaja ületamine andmepakettide kirjutamisel"
        fre "Timeout d'écriture des paquets envoyés"
        ger "Zeitüberschreitung beim Schreiben eines Kommunikationspakets"
        hun "Idotullepes a kommunikacios csomagok irasa soran"
        ita "Rilevato un timeout inviando i pacchetti di comunicazione"
        jpn "パケットの送信でタイムアウトが発生しました。"
        kor "통신 패팃을 기록하는 중 timeout이 발생하였습니다."
        por "Obteve expiração de tempo ('timeout') na escrita de pacotes de comunicação"
        rum "Timeout obtinut scriind pachetele de comunicatie (communication packets)"
        rus "Получен таймаут в процессе передачи пакета через коммуникационный протокол "
        serbian "Vremenski limit za slanje mrežnih paketa je istekao"
        spa "Obtenido timeout escribiendo paquetes de comunicación"
        swe "Fick 'timeout' vid skrivning till klienten"
        ukr "Отримано затримку запису комунікаційних пакетів"
ER_TOO_LONG_STRING 42000
        cze "Výsledný řetězec je delší než 'max_allowed_packet'"
        dan "Strengen med resultater er større end 'max_allowed_packet'"
        nla "Resultaat string is langer dan 'max_allowed_packet'"
        eng "Result string is longer than 'max_allowed_packet' bytes"
        est "Tulemus on pikem kui lubatud 'max_allowed_packet' muutujaga"
        fre "La chaîne résultat est plus grande que 'max_allowed_packet'"
        ger "Ergebnis-String ist länger als 'max_allowed_packet' Bytes"
        hun "Ez eredmeny sztring nagyobb, mint a lehetseges maximum: 'max_allowed_packet'"
        ita "La stringa di risposta e` piu` lunga di 'max_allowed_packet'"
        jpn "結果の文字列が 'max_allowed_packet' よりも大きいです。"
        por "'String' resultante é mais longa do que 'max_allowed_packet'"
        rum "Sirul rezultat este mai lung decit 'max_allowed_packet'"
        rus "Результирующая строка больше, чем 'max_allowed_packet'"
        serbian "Rezultujuči string je duži nego što to dozvoljava parametar servera 'max_allowed_packet'"
        spa "La string resultante es mayor que max_allowed_packet"
        swe "Resultatsträngen är längre än max_allowed_packet"
        ukr "Строка результату довша ніж max_allowed_packet"
ER_TABLE_CANT_HANDLE_BLOB 42000
        cze "Typ použité tabulky nepodporuje BLOB/TEXT sloupce"
        dan "Denne tabeltype understøtter ikke brug af BLOB og TEXT kolonner"
        nla "Het gebruikte tabel type ondersteunt geen BLOB/TEXT kolommen"
        eng "The used table type doesn't support BLOB/TEXT columns"
        est "Valitud tabelitüüp ei toeta BLOB/TEXT tüüpi välju"
        fre "Ce type de table ne supporte pas les colonnes BLOB/TEXT"
        ger "Der verwendete Tabellentyp unterstützt keine BLOB- und TEXT-Felder"
        hun "A hasznalt tabla tipus nem tamogatja a BLOB/TEXT mezoket"
        ita "Il tipo di tabella usata non supporta colonne di tipo BLOB/TEXT"
        jpn "指定されたストレージエンジンでは、BLOB/TEXT型の列を使用できません。"
        por "Tipo de tabela usado não permite colunas BLOB/TEXT"
        rum "Tipul de tabela folosit nu suporta coloane de tip BLOB/TEXT"
        rus "Используемая таблица не поддерживает типы BLOB/TEXT"
        serbian "Iskorišteni tip tabele ne podržava kolone tipa 'BLOB' odnosno 'TEXT'"
        spa "El tipo de tabla usada no permite soporte para columnas BLOB/TEXT"
        swe "Den använda tabelltypen kan inte hantera BLOB/TEXT-kolumner"
        ukr "Використаний тип таблиці не підтримує BLOB/TEXT стовбці"
ER_TABLE_CANT_HANDLE_AUTO_INCREMENT 42000
        cze "Typ použité tabulky nepodporuje AUTO_INCREMENT sloupce"
        dan "Denne tabeltype understøtter ikke brug af AUTO_INCREMENT kolonner"
        nla "Het gebruikte tabel type ondersteunt geen AUTO_INCREMENT kolommen"
        eng "The used table type doesn't support AUTO_INCREMENT columns"
        est "Valitud tabelitüüp ei toeta AUTO_INCREMENT tüüpi välju"
        fre "Ce type de table ne supporte pas les colonnes AUTO_INCREMENT"
        ger "Der verwendete Tabellentyp unterstützt keine AUTO_INCREMENT-Felder"
        hun "A hasznalt tabla tipus nem tamogatja az AUTO_INCREMENT tipusu mezoket"
        jpn "指定されたストレージエンジンでは、AUTO_INCREMENT列を使用できません。"
        ita "Il tipo di tabella usata non supporta colonne di tipo AUTO_INCREMENT"
        por "Tipo de tabela usado não permite colunas AUTO_INCREMENT"
        rum "Tipul de tabela folosit nu suporta coloane de tip AUTO_INCREMENT"
        rus "Используемая таблица не поддерживает автоинкрементные столбцы"
        serbian "Iskorišteni tip tabele ne podržava kolone tipa 'AUTO_INCREMENT'"
        spa "El tipo de tabla usada no permite soporte para columnas AUTO_INCREMENT"
        swe "Den använda tabelltypen kan inte hantera AUTO_INCREMENT-kolumner"
        ukr "Використаний тип таблиці не підтримує AUTO_INCREMENT стовбці"
OBSOLETE_ER_UNUSED3
        eng "INSERT DELAYED can't be used with table '%-.192s' because it is locked with LOCK TABLES"
ER_WRONG_COLUMN_NAME 42000
        cze "Nesprávné jméno sloupce '%-.100s'"
        dan "Forkert kolonnenavn '%-.100s'"
        nla "Incorrecte kolom naam '%-.100s'"
        eng "Incorrect column name '%-.100s'"
        est "Vigane tulba nimi '%-.100s'"
        fre "Nom de colonne '%-.100s' incorrect"
        ger "Falscher Spaltenname '%-.100s'"
        hun "Ervenytelen mezonev: '%-.100s'"
        ita "Nome colonna '%-.100s' non corretto"
        jpn "列名 '%-.100s' は不正です。"
        por "Nome de coluna '%-.100s' incorreto"
        rum "Nume increct de coloana '%-.100s'"
        rus "Неверное имя столбца '%-.100s'"
        serbian "Pogrešno ime kolone '%-.100s'"
        spa "Incorrecto nombre de columna '%-.100s'"
        swe "Felaktigt kolumnnamn '%-.100s'"
        ukr "Невірне ім'я стовбця '%-.100s'"
ER_WRONG_KEY_COLUMN 42000
        cze "Handler použité tabulky neumí indexovat sloupce '%-.192s'"
        dan "Den brugte tabeltype kan ikke indeksere kolonnen '%-.192s'"
        nla "De gebruikte tabel 'handler' kan kolom '%-.192s' niet indexeren"
        eng "The used storage engine can't index column '%-.192s'"
        est "Tabelihandler ei oska indekseerida tulpa '%-.192s'"
        fre "Le handler de la table ne peut indexé la colonne '%-.192s'"
        ger "Die verwendete Speicher-Engine kann die Spalte '%-.192s' nicht indizieren"
        greek "The used table handler can't index column '%-.192s'"
        hun "A hasznalt tablakezelo nem tudja a '%-.192s' mezot indexelni"
        ita "Il gestore delle tabelle non puo` indicizzare la colonna '%-.192s'"
        jpn "使用のストレージエンジンは列 '%-.192s' の索引を作成できません。"
        kor "The used table handler can't index column '%-.192s'"
        nor "The used table handler can't index column '%-.192s'"
        norwegian-ny "The used table handler can't index column '%-.192s'"
        pol "The used table handler can't index column '%-.192s'"
        por "O manipulador de tabela usado não pode indexar a coluna '%-.192s'"
        rum "Handler-ul tabelei folosite nu poate indexa coloana '%-.192s'"
        rus "Использованный обработчик таблицы не может проиндексировать столбец '%-.192s'"
        serbian "Handler tabele ne može da indeksira kolonu '%-.192s'"
        slo "The used table handler can't index column '%-.192s'"
        spa "El manipulador de tabla usado no puede indexar columna '%-.192s'"
        swe "Den använda tabelltypen kan inte indexera kolumn '%-.192s'"
        ukr "Використаний вказівник таблиці не може індексувати стовбець '%-.192s'"
ER_WRONG_MRG_TABLE
        cze "Všechny tabulky v MERGE tabulce nejsou definovány stejně"
        dan "Tabellerne i MERGE er ikke defineret ens"
        nla "Niet alle tabellen in de MERGE tabel hebben identieke gedefinities"
        eng "Unable to open underlying table which is differently defined or of non-MyISAM type or doesn't exist"
        est "Kõik tabelid MERGE tabeli määratluses ei ole identsed"
        fre "Toutes les tables de la table de type MERGE n'ont pas la même définition"
        ger "Nicht alle Tabellen in der MERGE-Tabelle sind gleich definiert"
        hun "A MERGE tablaban talalhato tablak definicioja nem azonos"
        ita "Non tutte le tabelle nella tabella di MERGE sono definite in maniera identica"
        jpn "MERGE表の構成表がオープンできません。列定義が異なるか、MyISAM表ではないか、存在しません。"
        kor "All tables in the MERGE table are not defined identically"
        nor "All tables in the MERGE table are not defined identically"
        norwegian-ny "All tables in the MERGE table are not defined identically"
        pol "All tables in the MERGE table are not defined identically"
        por "Todas as tabelas contidas na tabela fundida (MERGE) não estão definidas identicamente"
        rum "Toate tabelele din tabela MERGE nu sint definite identic"
        rus "Не все таблицы в MERGE определены одинаково"
        serbian "Tabele iskorištene u 'MERGE' tabeli nisu definisane na isti način"
        slo "All tables in the MERGE table are not defined identically"
        spa "Todas las tablas en la MERGE tabla no estan definidas identicamente"
        swe "Tabellerna i MERGE-tabellen är inte identiskt definierade"
        ukr "Таблиці у MERGE TABLE мають різну структуру"
ER_DUP_UNIQUE 23000
        cze "Kvůli unique constraintu nemozu zapsat do tabulky '%-.192s'"
        dan "Kan ikke skrive til tabellen '%-.192s' fordi det vil bryde CONSTRAINT regler"
        nla "Kan niet opslaan naar table '%-.192s' vanwege 'unique' beperking"
        eng "Can't write, because of unique constraint, to table '%-.192s'"
        est "Ei suuda kirjutada tabelisse '%-.192s', kuna see rikub ühesuse kitsendust"
        fre "Écriture impossible à cause d'un index UNIQUE sur la table '%-.192s'"
        ger "Schreiben in Tabelle '%-.192s' nicht möglich wegen einer Eindeutigkeitsbeschränkung (unique constraint)"
        hun "A '%-.192s' nem irhato, az egyedi mezok miatt"
        jpn "一意性制約違反のため、表 '%-.192s' に書き込めません。"
        ita "Impossibile scrivere nella tabella '%-.192s' per limitazione di unicita`"
        por "Não pode gravar, devido à restrição UNIQUE, na tabela '%-.192s'"
        rum "Nu pot scrie pe hard-drive, din cauza constraintului unic (unique constraint) pentru tabela '%-.192s'"
        rus "Невозможно записать в таблицу '%-.192s' из-за ограничений уникального ключа"
        serbian "Zbog provere jedinstvenosti ne mogu da upišem podatke u tabelu '%-.192s'"
        spa "No puedo escribir, debido al único constraint, para tabla '%-.192s'"
        swe "Kan inte skriva till tabell '%-.192s'; UNIQUE-test"
        ukr "Не можу записати до таблиці '%-.192s', з причини вимог унікальності"
ER_BLOB_KEY_WITHOUT_LENGTH 42000
        cze "BLOB sloupec '%-.192s' je použit ve specifikaci klíče bez délky"
        dan "BLOB kolonnen '%-.192s' brugt i nøglespecifikation uden nøglelængde"
        nla "BLOB kolom '%-.192s' gebruikt in zoeksleutel specificatie zonder zoeksleutel lengte"
        eng "BLOB/TEXT column '%-.192s' used in key specification without a key length"
        est "BLOB-tüüpi tulp '%-.192s' on kasutusel võtmes ilma pikkust määratlemata"
        fre "La colonne '%-.192s' de type BLOB est utilisée dans une définition d'index sans longueur d'index"
        ger "BLOB- oder TEXT-Spalte '%-.192s' wird in der Schlüsseldefinition ohne Schlüssellängenangabe verwendet"
        greek "BLOB column '%-.192s' used in key specification without a key length"
        hun "BLOB mezo '%-.192s' hasznalt a mezo specifikacioban, a mezohossz megadasa nelkul"
        ita "La colonna '%-.192s' di tipo BLOB e` usata in una chiave senza specificarne la lunghezza"
        jpn "BLOB列 '%-.192s' をキーに使用するには長さ指定が必要です。"
        kor "BLOB column '%-.192s' used in key specification without a key length"
        nor "BLOB column '%-.192s' used in key specification without a key length"
        norwegian-ny "BLOB column '%-.192s' used in key specification without a key length"
        pol "BLOB column '%-.192s' used in key specification without a key length"
        por "Coluna BLOB '%-.192s' usada na especificação de chave sem o comprimento da chave"
        rum "Coloana BLOB '%-.192s' este folosita in specificarea unei chei fara ca o lungime de cheie sa fie folosita"
        rus "Столбец типа BLOB '%-.192s' был указан в определении ключа без указания длины ключа"
        serbian "BLOB kolona '%-.192s' je upotrebljena u specifikaciji ključa bez navođenja dužine ključa"
        slo "BLOB column '%-.192s' used in key specification without a key length"
        spa "Columna BLOB column '%-.192s' usada en especificación de clave sin tamaño de la clave"
        swe "Du har inte angett någon nyckellängd för BLOB '%-.192s'"
        ukr "Стовбець BLOB '%-.192s' використано у визначенні ключа без вказання довжини ключа"
ER_PRIMARY_CANT_HAVE_NULL 42000
        cze "Všechny části primárního klíče musejí být NOT NULL; pokud potřebujete NULL, použijte UNIQUE"
        dan "Alle dele af en PRIMARY KEY skal være NOT NULL;  Hvis du skal bruge NULL i nøglen, brug UNIQUE istedet"
        nla "Alle delen van een PRIMARY KEY moeten NOT NULL zijn; Indien u NULL in een zoeksleutel nodig heeft kunt u UNIQUE gebruiken"
        eng "All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead"
        est "Kõik PRIMARY KEY peavad olema määratletud NOT NULL piiranguga; vajadusel kasuta UNIQUE tüüpi võtit"
        fre "Toutes les parties d'un index PRIMARY KEY doivent être NOT NULL; Si vous avez besoin d'un NULL dans l'index, utilisez un index UNIQUE"
        ger "Alle Teile eines PRIMARY KEY müssen als NOT NULL definiert sein. Wenn NULL in einem Schlüssel benötigt wird, muss ein UNIQUE-Schlüssel verwendet werden"
        hun "Az elsodleges kulcs teljes egeszeben csak NOT NULL tipusu lehet; Ha NULL mezot szeretne a kulcskent, hasznalja inkabb a UNIQUE-ot"
        ita "Tutte le parti di una chiave primaria devono essere dichiarate NOT NULL; se necessitano valori NULL nelle chiavi utilizzare UNIQUE"
        jpn "PRIMARY KEYの列は全てNOT NULLでなければいけません。UNIQUE索引であればNULLを含むことが可能です。"
        por "Todas as partes de uma chave primária devem ser não-nulas. Se você precisou usar um valor nulo (NULL) em uma chave, use a cláusula UNIQUE em seu lugar"
        rum "Toate partile unei chei primare (PRIMARY KEY) trebuie sa fie NOT NULL; Daca aveti nevoie de NULL in vreo cheie, folositi UNIQUE in schimb"
        rus "Все части первичного ключа (PRIMARY KEY) должны быть определены как NOT NULL; Если вам нужна поддержка величин NULL в ключе, воспользуйтесь индексом UNIQUE"
        serbian "Svi delovi primarnog ključa moraju biti različiti od NULL;  Ako Vam ipak treba NULL vrednost u ključu, upotrebite 'UNIQUE'"
        spa "Todas las partes de un PRIMARY KEY deben ser NOT NULL;  Si necesitas NULL en una clave, use UNIQUE"
        swe "Alla delar av en PRIMARY KEY måste vara NOT NULL;  Om du vill ha en nyckel med NULL, använd UNIQUE istället"
        ukr "Усі частини PRIMARY KEY повинні бути NOT NULL; Якщо ви потребуєте NULL у ключі, скористайтеся UNIQUE"
ER_TOO_MANY_ROWS 42000
        cze "Výsledek obsahuje více než jeden řádek"
        dan "Resultatet bestod af mere end een række"
        nla "Resultaat bevatte meer dan een rij"
        eng "Result consisted of more than one row"
        est "Tulemis oli rohkem kui üks kirje"
        fre "Le résultat contient plus d'un enregistrement"
        ger "Ergebnis besteht aus mehr als einer Zeile"
        hun "Az eredmeny tobb, mint egy sort tartalmaz"
        ita "Il risultato consiste di piu` di una riga"
        jpn "結果が2行以上です。"
        por "O resultado consistiu em mais do que uma linha"
        rum "Resultatul constista din mai multe linii"
        rus "В результате возвращена более чем одна строка"
        serbian "Rezultat je sačinjen od više slogova"
        spa "Resultado compuesto de mas que una línea"
        swe "Resultet bestod av mera än en rad"
        ukr "Результат знаходиться у більше ніж одній строці"
ER_REQUIRES_PRIMARY_KEY 42000
        cze "Tento typ tabulky vyžaduje primární klíč"
        dan "Denne tabeltype kræver en primærnøgle"
        nla "Dit tabel type heeft een primaire zoeksleutel nodig"
        eng "This table type requires a primary key"
        est "Antud tabelitüüp nõuab primaarset võtit"
        fre "Ce type de table nécessite une clé primaire (PRIMARY KEY)"
        ger "Dieser Tabellentyp benötigt einen Primärschlüssel (PRIMARY KEY)"
        hun "Az adott tablatipushoz elsodleges kulcs hasznalata kotelezo"
        ita "Questo tipo di tabella richiede una chiave primaria"
        jpn "使用のストレージエンジンでは、PRIMARY KEYが必要です。"
        por "Este tipo de tabela requer uma chave primária"
        rum "Aceast tip de tabela are nevoie de o cheie primara"
        rus "Этот тип таблицы требует определения первичного ключа"
        serbian "Ovaj tip tabele zahteva da imate definisan primarni ključ"
        spa "Este tipo de tabla necesita de una primary key"
        swe "Denna tabelltyp kräver en PRIMARY KEY"
        ukr "Цей тип таблиці потребує первинного ключа"
OBSOLETE_ER_NO_RAID_COMPILED
        cze "Tato verze MySQL není zkompilována s podporou RAID"
        dan "Denne udgave af MySQL er ikke oversat med understøttelse af RAID"
        nla "Deze versie van MySQL is niet gecompileerd met RAID ondersteuning"
        eng "This version of MySQL is not compiled with RAID support"
        est "Antud MySQL versioon on kompileeritud ilma RAID toeta"
        fre "Cette version de MySQL n'est pas compilée avec le support RAID"
        ger "Diese MySQL-Version ist nicht mit RAID-Unterstützung kompiliert"
        hun "Ezen leforditott MySQL verzio nem tartalmaz RAID support-ot"
        ita "Questa versione di MYSQL non e` compilata con il supporto RAID"
        jpn "このバージョンのMySQLはRAIDサポートを含めてコンパイルされていません。"
        por "Esta versão do MySQL não foi compilada com suporte a RAID"
        rum "Aceasta versiune de MySQL, nu a fost compilata cu suport pentru RAID"
        rus "Эта версия MySQL скомпилирована без поддержки RAID"
        serbian "Ova verzija MySQL servera nije kompajlirana sa podrškom za RAID uređaje"
        spa "Esta versión de MySQL no es compilada con soporte RAID"
        swe "Denna version av MySQL är inte kompilerad med RAID"
        ukr "Ця версія MySQL не зкомпільована з підтримкою RAID"
ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE
        cze "Update tabulky bez WHERE s klíčem není v módu bezpečných update dovoleno. %s"
        dan "Du bruger sikker opdaterings modus ('safe update mode') og du forsøgte at opdatere en tabel uden en WHERE klausul, der gør brug af et KEY felt. %s"
        nla "U gebruikt 'safe update mode' en u probeerde een tabel te updaten zonder een WHERE met een KEY kolom. %s"
        eng "You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column. %s"
        est "Katse muuta tabelit turvalises rezhiimis ilma WHERE klauslita. %s"
        fre "Vous êtes en mode 'safe update' et vous essayez de faire un UPDATE sans clause WHERE utilisant un index. %s"
        ger "MySQL läuft im sicheren Aktualisierungsmodus (safe update mode). Sie haben versucht, eine Tabelle zu aktualisieren, ohne in der WHERE-Klausel ein KEY-Feld anzugeben. %s"
        hun "On a biztonsagos update modot hasznalja, es        WHERE that uses a KEY column. %s"
        ita "In modalita` 'safe update' si e` cercato di aggiornare una tabella senza clausola WHERE su una chiave. %s"
        jpn "'safe update mode'で、索引を利用するWHERE句の無い更新処理を実行しようとしました。. %s"
        por "Você está usando modo de atualização seguro e tentou atualizar uma tabela sem uma cláusula WHERE que use uma coluna chave. %s"
        rus "Вы работаете в режиме безопасных обновлений (safe update mode) и попробовали изменить таблицу без использования ключевого столбца в части WHERE. %s"
        serbian "Vi koristite safe update mod servera, a probali ste da promenite podatke bez 'WHERE' komande koja koristi kolonu ključa. %s"
        spa "Tu estás usando modo de actualización segura y tentado actualizar una tabla sin un WHERE que usa una KEY columna. %s"
        swe "Du använder 'säker uppdateringsmod' och försökte uppdatera en tabell utan en WHERE-sats som använder sig av en nyckel. %s"
        ukr "Ви у режимі безпечного оновлення та намагаєтесь оновити таблицю без оператора WHERE, що використовує KEY стовбець. %s"
ER_KEY_DOES_NOT_EXITS 42000 S1009
        cze "Klíč '%-.192s' v tabulce '%-.192s' neexistuje"
        dan "Nøglen '%-.192s' eksisterer ikke i tabellen '%-.192s'"
        nla "Zoeksleutel '%-.192s' bestaat niet in tabel '%-.192s'"
        eng "Key '%-.192s' doesn't exist in table '%-.192s'"
        est "Võti '%-.192s' ei eksisteeri tabelis '%-.192s'"
        fre "L'index '%-.192s' n'existe pas sur la table '%-.192s'"
        ger "Schlüssel '%-.192s' existiert in der Tabelle '%-.192s' nicht"
        hun "A '%-.192s' kulcs nem letezik a '%-.192s' tablaban"
        ita "La chiave '%-.192s' non esiste nella tabella '%-.192s'"
        jpn "索引 '%-.192s' は表 '%-.192s' には存在しません。"
        por "Chave '%-.192s' não existe na tabela '%-.192s'"
        rus "Ключ '%-.192s' не существует в таблице '%-.192s'"
        serbian "Ključ '%-.192s' ne postoji u tabeli '%-.192s'"
        spa "Clave '%-.192s' no existe en la tabla '%-.192s'"
        swe "Nyckel '%-.192s' finns inte in tabell '%-.192s'"
        ukr "Ключ '%-.192s' не існує в таблиці '%-.192s'"
ER_CHECK_NO_SUCH_TABLE 42000
        cze "Nemohu otevřít tabulku"
        dan "Kan ikke åbne tabellen"
        nla "Kan tabel niet openen"
        eng "Can't open table"
        est "Ei suuda avada tabelit"
        fre "Impossible d'ouvrir la table"
        ger "Kann Tabelle nicht öffnen"
        hun "Nem tudom megnyitni a tablat"
        ita "Impossibile aprire la tabella"
        jpn "表をオープンできません。"
        por "Não pode abrir a tabela"
        rus "Невозможно открыть таблицу"
        serbian "Ne mogu da otvorim tabelu"
        spa "No puedo abrir tabla"
        swe "Kan inte öppna tabellen"
        ukr "Не можу відкрити таблицю"
ER_CHECK_NOT_IMPLEMENTED 42000
        cze "Handler tabulky nepodporuje %s"
        dan "Denne tabeltype understøtter ikke %s"
        nla "De 'handler' voor de tabel ondersteund geen %s"
        eng "The storage engine for the table doesn't support %s"
        est "Antud tabelitüüp ei toeta %s käske"
        fre "Ce type de table ne supporte pas les %s"
        ger "Die Speicher-Engine für diese Tabelle unterstützt kein %s"
        greek "The handler for the table doesn't support %s"
        hun "A tabla kezeloje (handler) nem tamogatja az %s"
        ita "Il gestore per la tabella non supporta il %s"
        jpn "この表のストレージエンジンは '%s' を利用できません。"
        kor "The handler for the table doesn't support %s"
        nor "The handler for the table doesn't support %s"
        norwegian-ny "The handler for the table doesn't support %s"
        pol "The handler for the table doesn't support %s"
        por "O manipulador de tabela não suporta %s"
        rum "The handler for the table doesn't support %s"
        rus "Обработчик таблицы не поддерживает этого: %s"
        serbian "Handler za ovu tabelu ne dozvoljava %s komande"
        slo "The handler for the table doesn't support %s"
        spa "El manipulador de la tabla no permite soporte para %s"
        swe "Tabellhanteraren för denna tabell kan inte göra %s"
        ukr "Вказівник таблиці не підтримуе %s"
ER_CANT_DO_THIS_DURING_AN_TRANSACTION 25000
        cze "Provedení tohoto příkazu není v transakci dovoleno"
        dan "Du må ikke bruge denne kommando i en transaktion"
        nla "Het is u niet toegestaan dit commando uit te voeren binnen een transactie"
        eng "You are not allowed to execute this command in a transaction"
        est "Seda käsku ei saa kasutada transaktsiooni sees"
        fre "Vous n'êtes pas autorisé à exécute cette commande dans une transaction"
        ger "Sie dürfen diesen Befehl nicht in einer Transaktion ausführen"
        hun "Az On szamara nem engedelyezett a parancs vegrehajtasa a tranzakcioban"
        ita "Non puoi eseguire questo comando in una transazione"
        jpn "このコマンドはトランザクション内で実行できません。"
        por "Não lhe é permitido executar este comando em uma transação"
        rus "Вам не разрешено выполнять эту команду в транзакции"
        serbian "Nije Vam dozvoljeno da izvršite ovu komandu u transakciji"
        spa "No tienes el permiso para ejecutar este comando en una transición"
        swe "Du får inte utföra detta kommando i en transaktion"
        ukr "Вам не дозволено виконувати цю команду в транзакції"
ER_ERROR_DURING_COMMIT
        cze "Chyba %d - '%-.192s' při COMMIT"
        dan "Modtog fejl %d - '%-.192s' mens kommandoen COMMIT blev udført"
        nla "Kreeg fout %d - '%-.192s' tijdens COMMIT"
        eng "Got error %d - '%-.192s' during COMMIT"
        est "Viga %d - '%-.192s' käsu COMMIT täitmisel"
        fre "Erreur %d - '%-.192s' lors du COMMIT"
        ger "Fehler %d - '%-.192s' beim COMMIT"
        hun "%d - '%-.192s' hiba a COMMIT vegrehajtasa soran"
        ita "Rilevato l'errore %d - '%-.192s' durante il COMMIT"
        jpn "COMMIT中にエラー %d - '%-.192s' が発生しました。"
        por "Obteve erro %d - '%-.192s' durante COMMIT"
        rus "Получена ошибка %d - '%-.192s' в процессе COMMIT"
        serbian "Greška %d - '%-.192s' za vreme izvršavanja komande 'COMMIT'"
        spa "Obtenido error %d - '%-.192s' durante COMMIT"
        swe "Fick fel %d - '%-.192s' vid COMMIT"
        ukr "Отримано помилку %d - '%-.192s' під час COMMIT"
ER_ERROR_DURING_ROLLBACK
        cze "Chyba %d - '%-.192s' při ROLLBACK"
        dan "Modtog fejl %d - '%-.192s' mens kommandoen ROLLBACK blev udført"
        nla "Kreeg fout %d - '%-.192s' tijdens ROLLBACK"
        eng "Got error %d - '%-.192s' during ROLLBACK"
        est "Viga %d - '%-.192s' käsu ROLLBACK täitmisel"
        fre "Erreur %d - '%-.192s' lors du ROLLBACK"
        ger "Fehler %d - '%-.192s' beim ROLLBACK"
        hun "%d - '%-.192s' hiba a ROLLBACK vegrehajtasa soran"
        ita "Rilevato l'errore %d - '%-.192s' durante il ROLLBACK"
        jpn "ROLLBACK中にエラー %d - '%-.192s' が発生しました。"
        por "Obteve erro %d - '%-.192s' durante ROLLBACK"
        rus "Получена ошибка %d - '%-.192s' в процессе ROLLBACK"
        serbian "Greška %d - '%-.192s' za vreme izvršavanja komande 'ROLLBACK'"
        spa "Obtenido error %d - '%-.192s' durante ROLLBACK"
        swe "Fick fel %d - '%-.192s' vid ROLLBACK"
        ukr "Отримано помилку %d - '%-.192s' під час ROLLBACK"
ER_ERROR_DURING_FLUSH_LOGS
        cze "Chyba %d při FLUSH_LOGS"
        dan "Modtog fejl %d mens kommandoen FLUSH_LOGS blev udført"
        nla "Kreeg fout %d tijdens FLUSH_LOGS"
        eng "Got error %d during FLUSH_LOGS"
        est "Viga %d käsu FLUSH_LOGS täitmisel"
        fre "Erreur %d lors du FLUSH_LOGS"
        ger "Fehler %d bei FLUSH_LOGS"
        hun "%d hiba a FLUSH_LOGS vegrehajtasa soran"
        ita "Rilevato l'errore %d durante il FLUSH_LOGS"
        jpn "FLUSH_LOGS中にエラー %d が発生しました。"
        por "Obteve erro %d durante FLUSH_LOGS"
        rus "Получена ошибка %d в процессе FLUSH_LOGS"
        serbian "Greška %d za vreme izvršavanja komande 'FLUSH_LOGS'"
        spa "Obtenido error %d durante FLUSH_LOGS"
        swe "Fick fel %d vid FLUSH_LOGS"
        ukr "Отримано помилку %d під час FLUSH_LOGS"
OBSOLETE_ER_ERROR_DURING_CHECKPOINT
        cze "Chyba %d při CHECKPOINT"
        dan "Modtog fejl %d mens kommandoen CHECKPOINT blev udført"
        nla "Kreeg fout %d tijdens CHECKPOINT"
        eng "Got error %d during CHECKPOINT"
        est "Viga %d käsu CHECKPOINT täitmisel"
        fre "Erreur %d lors du CHECKPOINT"
        ger "Fehler %d bei CHECKPOINT"
        hun "%d hiba a CHECKPOINT vegrehajtasa soran"
        ita "Rilevato l'errore %d durante il CHECKPOINT"
        jpn "CHECKPOINT中にエラー %d が発生しました。"
        por "Obteve erro %d durante CHECKPOINT"
        rus "Получена ошибка %d в процессе CHECKPOINT"
        serbian "Greška %d za vreme izvršavanja komande 'CHECKPOINT'"
        spa "Obtenido error %d durante CHECKPOINT"
        swe "Fick fel %d vid CHECKPOINT"
        ukr "Отримано помилку %d під час CHECKPOINT"
ER_NEW_ABORTING_CONNECTION 08S01
        cze "Spojení %u do databáze: '%-.192s' uživatel: '%-.48s' stroj: '%-.255s' (%-.64s) bylo přerušeno"
        dan "Afbrød forbindelsen %u til databasen '%-.192s' bruger: '%-.48s' vært: '%-.255s' (%-.64s)"
        nla "Afgebroken verbinding %u naar db: '%-.192s' gebruiker: '%-.48s' host: '%-.255s' (%-.64s)"
        eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)"
        est "Ühendus katkestatud %u andmebaas: '%-.192s' kasutaja: '%-.48s' masin: '%-.255s' (%-.64s)"
        fre "Connection %u avortée vers la bd: '%-.192s' utilisateur: '%-.48s' hôte: '%-.255s' (%-.64s)"
        ger "Abbruch der Verbindung %u zur Datenbank '%-.192s'. Benutzer: '%-.48s', Host: '%-.255s' (%-.64s)"
        ita "Interrotta la connessione %u al db: ''%-.192s' utente: '%-.48s' host: '%-.255s' (%-.64s)"
        jpn "接続 %u が中断されました。データベース: '%-.192s' ユーザー: '%-.48s' ホスト: '%-.255s' (%-.64s)"
        por "Conexão %u abortada para banco de dados '%-.192s' - usuário '%-.48s' - 'host' '%-.255s' ('%-.64s')"
        rus "Прервано соединение %u к базе данных '%-.192s' пользователя '%-.48s' с хоста '%-.255s' (%-.64s)"
        serbian "Prekinuta konekcija broj %u ka bazi: '%-.192s' korisnik je bio: '%-.48s' a host: '%-.255s' (%-.64s)"
        spa "Abortada conexión %u para db: '%-.192s' usuario: '%-.48s' servidor: '%-.255s' (%-.64s)"
        swe "Avbröt länken för tråd %u till db '%-.192s', användare '%-.48s', host '%-.255s' (%-.64s)"
        ukr "Перервано з'єднання %u до бази данних: '%-.192s' користувач: '%-.48s' хост: '%-.255s' (%-.64s)"
OBSOLETE_ER_DUMP_NOT_IMPLEMENTED
        cze "Handler tabulky nepodporuje binární dump"
        dan "Denne tabeltype unserstøtter ikke binært tabeldump"
        nla "De 'handler' voor de tabel ondersteund geen binaire tabel dump"
        eng "The storage engine for the table does not support binary table dump"
        fre "Ce type de table ne supporte pas les copies binaires"
        ger "Die Speicher-Engine für die Tabelle unterstützt keinen binären Tabellen-Dump"
        ita "Il gestore per la tabella non supporta il dump binario"
        jpn "この表のストレージエンジンはバイナリ形式の表ダンプを利用できません。"
        por "O manipulador de tabela não suporta 'dump' binário de tabela"
        rum "The handler for the table does not support binary table dump"
        rus "Обработчик этой таблицы не поддерживает двоичного сохранения образа таблицы (dump)"
        serbian "Handler tabele ne podržava binarni dump tabele"
        spa "El manipulador de tabla no soporta dump para tabla binaria"
        swe "Tabellhanteraren klarar inte en binär kopiering av tabellen"
        ukr "Цей тип таблиці не підтримує бінарну передачу таблиці"
OBSOLETE_ER_FLUSH_MASTER_BINLOG_CLOSED
        eng "Binlog closed, cannot RESET SOURCE"
        ger "Binlog geschlossen. Kann RESET MASTER nicht ausführen"
        jpn "バイナリログがクローズされています。RESET MASTER を実行できません。"
        por "Binlog fechado. Não pode fazer RESET MASTER"
        rus "Двоичный журнал обновления закрыт, невозможно выполнить RESET MASTER"
        serbian "Binarni log file zatvoren, ne mogu da izvršim komandu 'RESET MASTER'"
        ukr "Реплікаційний лог закрито, не можу виконати RESET MASTER"
OBSOLETE_ER_INDEX_REBUILD
        cze "Přebudování indexu dumpnuté tabulky '%-.192s' nebylo úspěšné"
        dan "Kunne ikke genopbygge indekset for den dumpede tabel '%-.192s'"
        nla "Gefaald tijdens heropbouw index van gedumpte tabel '%-.192s'"
        eng "Failed rebuilding the index of  dumped table '%-.192s'"
        fre "La reconstruction de l'index de la table copiée '%-.192s' a échoué"
        ger "Neuerstellung des Index der Dump-Tabelle '%-.192s' fehlgeschlagen"
        greek "Failed rebuilding the index of dumped table '%-.192s'"
        hun "Failed rebuilding the index of dumped table '%-.192s'"
        ita "Fallita la ricostruzione dell'indice della tabella copiata '%-.192s'"
        jpn "ダンプ表 '%-.192s' の索引再構築に失敗しました。"
        por "Falhou na reconstrução do índice da tabela 'dumped' '%-.192s'"
        rus "Ошибка перестройки индекса сохраненной таблицы '%-.192s'"
        serbian "Izgradnja indeksa dump-ovane tabele '%-.192s' nije uspela"
        spa "Falla reconstruyendo el indice de la tabla dumped '%-.192s'"
        ukr "Невдале відновлення індекса переданої таблиці '%-.192s'"
ER_SOURCE
        cze "Chyba masteru: '%-.64s'"
        dan "Fejl fra master: '%-.64s'"
        nla "Fout van master: '%-.64s'"
        eng "Error from source: '%-.64s'"
        fre "Erreur reçue du maître: '%-.64s'"
        ger "Fehler vom Master: '%-.64s'"
        ita "Errore dal master: '%-.64s"
        jpn "マスターでエラーが発生: '%-.64s'"
        por "Erro no 'master' '%-.64s'"
        rus "Ошибка от головного сервера: '%-.64s'"
        serbian "Greška iz glavnog servera '%-.64s' u klasteru"
        spa "Error del master: '%-.64s'"
        swe "Fel från master: '%-.64s'"
        ukr "Помилка від головного: '%-.64s'"
ER_SOURCE_NET_READ 08S01
        cze "Síťová chyba při čtení z masteru"
        dan "Netværksfejl ved læsning fra master"
        nla "Net fout tijdens lezen van master"
        eng "Net error reading from source"
        fre "Erreur de lecture réseau reçue du maître"
        ger "Netzfehler beim Lesen vom Master"
        ita "Errore di rete durante la ricezione dal master"
        jpn "マスターからのデータ受信中のネットワークエラー"
        por "Erro de rede lendo do 'master'"
        rus "Возникла ошибка чтения в процессе коммуникации с головным сервером"
        serbian "Greška u primanju mrežnih paketa sa glavnog servera u klasteru"
        spa "Error de red leyendo del master"
        swe "Fick nätverksfel vid läsning från master"
        ukr "Мережева помилка читання від головного"
ER_SOURCE_NET_WRITE 08S01
        cze "Síťová chyba při zápisu na master"
        dan "Netværksfejl ved skrivning til master"
        nla "Net fout tijdens schrijven naar master"
        eng "Net error writing to source"
        fre "Erreur d'écriture réseau reçue du maître"
        ger "Netzfehler beim Schreiben zum Master"
        ita "Errore di rete durante l'invio al master"
        jpn "マスターへのデータ送信中のネットワークエラー"
        por "Erro de rede gravando no 'master'"
        rus "Возникла ошибка записи в процессе коммуникации с головным сервером"
        serbian "Greška u slanju mrežnih paketa na glavni server u klasteru"
        spa "Error de red escribiendo para el master"
        swe "Fick nätverksfel vid skrivning till master"
        ukr "Мережева помилка запису до головного"
ER_FT_MATCHING_KEY_NOT_FOUND
        cze "Žádný sloupec nemá vytvořen fulltextový index"
        dan "Kan ikke finde en FULLTEXT nøgle som svarer til kolonne listen"
        nla "Kan geen FULLTEXT index vinden passend bij de kolom lijst"
        eng "Can't find FULLTEXT index matching the column list"
        est "Ei suutnud leida FULLTEXT indeksit, mis kattuks kasutatud tulpadega"
        fre "Impossible de trouver un index FULLTEXT correspondant à cette liste de colonnes"
        ger "Kann keinen FULLTEXT-Index finden, der der Feldliste entspricht"
        ita "Impossibile trovare un indice FULLTEXT che corrisponda all'elenco delle colonne"
        jpn "列リストに対応する全文索引(FULLTEXT)が見つかりません。"
        por "Não pode encontrar um índice para o texto todo que combine com a lista de colunas"
        rus "Невозможно отыскать полнотекстовый (FULLTEXT) индекс, соответствующий списку столбцов"
        serbian "Ne mogu da pronađem 'FULLTEXT' indeks koli odgovara listi kolona"
        spa "No puedo encontrar índice FULLTEXT correspondiendo a la lista de columnas"
        swe "Hittar inte ett FULLTEXT-index i kolumnlistan"
        ukr "Не можу знайти FULLTEXT індекс, що відповідає переліку стовбців"
ER_LOCK_OR_ACTIVE_TRANSACTION
        cze "Nemohu provést zadaný příkaz, protože existují aktivní zamčené tabulky nebo aktivní transakce"
        dan "Kan ikke udføre den givne kommando fordi der findes aktive, låste tabeller eller fordi der udføres en transaktion"
        nla "Kan het gegeven commando niet uitvoeren, want u heeft actieve gelockte tabellen of een actieve transactie"
        eng "Can't execute the given command because you have active locked tables or an active transaction"
        est "Ei suuda täita antud käsku kuna on aktiivseid lukke või käimasolev transaktsioon"
        fre "Impossible d'exécuter la commande car vous avez des tables verrouillées ou une transaction active"
        ger "Kann den angegebenen Befehl wegen einer aktiven Tabellensperre oder einer aktiven Transaktion nicht ausführen"
        ita "Impossibile eseguire il comando richiesto: tabelle sotto lock o transazione in atto"
        jpn "すでにアクティブな表ロックやトランザクションがあるため、コマンドを実行できません。"
        por "Não pode executar o comando dado porque você tem tabelas ativas travadas ou uma transação ativa"
        rus "Невозможно выполнить указанную команду, поскольку у вас присутствуют активно заблокированные таблица или открытая транзакция"
        serbian "Ne mogu da izvršim datu komandu zbog toga što su tabele zaključane ili je transakcija u toku"
        spa "No puedo ejecutar el comando dado porque tienes tablas bloqueadas o una transición activa"
        swe "Kan inte utföra kommandot emedan du har en låst tabell eller an aktiv transaktion"
        ukr "Не можу виконати подану команду тому, що таблиця заблокована або виконується транзакція"
ER_UNKNOWN_SYSTEM_VARIABLE
        cze "Neznámá systémová proměnná '%-.64s'"
        dan "Ukendt systemvariabel '%-.64s'"
        nla "Onbekende systeem variabele '%-.64s'"
        eng "Unknown system variable '%-.64s'"
        est "Tundmatu süsteemne muutuja '%-.64s'"
        fre "Variable système '%-.64s' inconnue"
        ger "Unbekannte Systemvariable '%-.64s'"
        ita "Variabile di sistema '%-.64s' sconosciuta"
        jpn "'%-.64s' は不明なシステム変数です。"
        por "Variável de sistema '%-.64s' desconhecida"
        rus "Неизвестная системная переменная '%-.64s'"
        serbian "Nepoznata sistemska promenljiva '%-.64s'"
        spa "Desconocida variable de sistema '%-.64s'"
        swe "Okänd systemvariabel: '%-.64s'"
        ukr "Невідома системна змінна '%-.64s'"
ER_CRASHED_ON_USAGE
        cze "Tabulka '%-.192s' je označena jako porušená a měla by být opravena"
        dan "Tabellen '%-.192s' er markeret med fejl og bør repareres"
        nla "Tabel '%-.192s' staat als gecrashed gemarkeerd en dient te worden gerepareerd"
        eng "Table '%-.192s' is marked as crashed and should be repaired"
        est "Tabel '%-.192s' on märgitud vigaseks ja tuleb parandada"
        fre "La table '%-.192s' est marquée 'crashed' et devrait être réparée"
        ger "Tabelle '%-.192s' ist als defekt markiert und sollte repariert werden"
        ita "La tabella '%-.192s' e` segnalata come corrotta e deve essere riparata"
        jpn "表 '%-.192s' は壊れています。修復が必要です。"
        por "Tabela '%-.192s' está marcada como danificada e deve ser reparada"
        rus "Таблица '%-.192s' помечена как испорченная и должна пройти проверку и ремонт"
        serbian "Tabela '%-.192s' je markirana kao oštećena i trebala bi biti popravljena"
        spa "Tabla '%-.192s' está marcada como crashed y debe ser reparada"
        swe "Tabell '%-.192s' är trasig och bör repareras med REPAIR TABLE"
        ukr "Таблицю '%-.192s' марковано як зіпсовану та її потрібно відновити"
ER_CRASHED_ON_REPAIR
        cze "Tabulka '%-.192s' je označena jako porušená a poslední (automatická?) oprava se nezdařila"
        dan "Tabellen '%-.192s' er markeret med fejl og sidste (automatiske?) REPAIR fejlede"
        nla "Tabel '%-.192s' staat als gecrashed gemarkeerd en de laatste (automatische?) reparatie poging mislukte"
        eng "Table '%-.192s' is marked as crashed and last (automatic?) repair failed"
        est "Tabel '%-.192s' on märgitud vigaseks ja viimane (automaatne?) parandus ebaõnnestus"
        fre "La table '%-.192s' est marquée 'crashed' et le dernier 'repair' a échoué"
        ger "Tabelle '%-.192s' ist als defekt markiert und der letzte (automatische?) Reparaturversuch schlug fehl"
        ita "La tabella '%-.192s' e` segnalata come corrotta e l'ultima ricostruzione (automatica?) e` fallita"
        jpn "表 '%-.192s' は壊れています。修復(自動？)にも失敗しています。"
        por "Tabela '%-.192s' está marcada como danificada e a última reparação (automática?) falhou"
        rus "Таблица '%-.192s' помечена как испорченная и последний (автоматический?) ремонт не был успешным"
        serbian "Tabela '%-.192s' je markirana kao oštećena, a zadnja (automatska?) popravka je bila neuspela"
        spa "Tabla '%-.192s' está marcada como crashed y la última reparación (automactica?) falló"
        swe "Tabell '%-.192s' är trasig och senast (automatiska?) reparation misslyckades"
        ukr "Таблицю '%-.192s' марковано як зіпсовану та останнє (автоматичне?) відновлення не вдалося"
ER_WARNING_NOT_COMPLETE_ROLLBACK
        dan "Advarsel: Visse data i tabeller der ikke understøtter transaktioner kunne ikke tilbagestilles"
        nla "Waarschuwing: Roll back mislukt voor sommige buiten transacties gewijzigde tabellen"
        eng "Some non-transactional changed tables couldn't be rolled back"
        est "Hoiatus: mõnesid transaktsioone mittetoetavaid tabeleid ei suudetud tagasi kerida"
        fre "Attention: certaines tables ne supportant pas les transactions ont été changées et elles ne pourront pas être restituées"
        ger "Änderungen an einigen nicht transaktionalen Tabellen konnten nicht zurückgerollt werden"
        ita "Attenzione: Alcune delle modifiche alle tabelle non transazionali non possono essere ripristinate (roll back impossibile)"
        jpn "トランザクション対応ではない表への変更はロールバックされません。"
        por "Aviso: Algumas tabelas não-transacionais alteradas não puderam ser reconstituídas (rolled back)"
        rus "Внимание: по некоторым измененным нетранзакционным таблицам невозможно будет произвести откат транзакции"
        serbian "Upozorenje: Neke izmenjene tabele ne podržavaju komandu 'ROLLBACK'"
        spa "Aviso:  Algunas tablas no transancionales no pueden tener rolled back"
        swe "Warning:  Några icke transaktionella tabeller kunde inte återställas vid ROLLBACK"
        ukr "Застереження: Деякі нетранзакційні зміни таблиць не можна буде повернути"
ER_TRANS_CACHE_FULL
        dan "Fler-udtryks transaktion krævede mere plads en 'max_binlog_cache_size' bytes. Forhøj værdien af denne variabel og prøv igen"
        nla "Multi-statement transactie vereist meer dan 'max_binlog_cache_size' bytes opslag. Verhoog deze mysqld variabele en probeer opnieuw"
        eng "Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage; increase this mysqld variable and try again"
        est "Mitme lausendiga transaktsioon nõudis rohkem ruumi kui lubatud 'max_binlog_cache_size' muutujaga. Suurenda muutuja väärtust ja proovi uuesti"
        fre "Cette transaction à commandes multiples nécessite plus de 'max_binlog_cache_size' octets de stockage, augmentez cette variable de mysqld et réessayez"
        ger "Transaktionen, die aus mehreren Befehlen bestehen, benötigten mehr als 'max_binlog_cache_size' Bytes an Speicher. Btte vergrössern Sie diese Server-Variable versuchen Sie es noch einmal"
        ita "La transazione a comandi multipli (multi-statement) ha richiesto piu` di 'max_binlog_cache_size' bytes di disco: aumentare questa variabile di mysqld e riprovare"
        jpn "複数ステートメントから成るトランザクションが 'max_binlog_cache_size' 以上の容量を必要としました。このシステム変数を増加して、再試行してください。"
        por "Transações multi-declaradas (multi-statement transactions) requeriram mais do que o valor limite (max_binlog_cache_size) de bytes para armazenagem. Aumente o valor desta variável do mysqld e tente novamente"
        rus "Транзакции, включающей большое количество команд, потребовалось более чем 'max_binlog_cache_size' байт. Увеличьте эту переменную сервера mysqld и попробуйте еще раз"
        spa "Multipla transición necesita mas que 'max_binlog_cache_size' bytes de almacenamiento. Aumente esta variable mysqld y tente de nuevo"
        swe "Transaktionen krävde mera än 'max_binlog_cache_size' minne. Öka denna mysqld-variabel och försök på nytt"
        ukr "Транзакція з багатьма виразами вимагає більше ніж 'max_binlog_cache_size' байтів для зберігання. Збільште цю змінну mysqld та спробуйте знову"
OBSOLETE_ER_SLAVE_MUST_STOP
        dan "Denne handling kunne ikke udføres med kørende slave, brug først kommandoen STOP SLAVE"
        nla "Deze operatie kan niet worden uitgevoerd met een actieve slave, doe eerst STOP SLAVE"
        eng "This operation cannot be performed with a running replica; run STOP REPLICA first"
        fre "Cette opération ne peut être réalisée avec un esclave actif, faites STOP SLAVE d'abord"
        ger "Diese Operation kann bei einem aktiven Slave nicht durchgeführt werden. Bitte zuerst STOP SLAVE ausführen"
        ita "Questa operazione non puo' essere eseguita con un database 'slave' che gira, lanciare prima STOP SLAVE"
        jpn "この処理は、稼働中のスレーブでは実行できません。あらかじめSTOP SLAVEコマンドを実行してください。"
        por "Esta operação não pode ser realizada com um 'slave' em execução. Execute STOP SLAVE primeiro"
        rus "Эту операцию невозможно выполнить при работающем потоке подчиненного сервера. Сначала выполните STOP SLAVE"
        serbian "Ova operacija ne može biti izvršena dok je aktivan podređeni server. Zadajte prvo komandu 'STOP SLAVE' da zaustavite podređeni server."
        spa "Esta operación no puede ser hecha con el esclavo funcionando, primero use STOP SLAVE"
        swe "Denna operation kan inte göras under replikering; Gör STOP SLAVE först"
        ukr "Операція не може бути виконана з запущеним підлеглим, спочатку виконайте STOP SLAVE"
ER_REPLICA_NOT_RUNNING
        dan "Denne handling kræver en kørende slave. Konfigurer en slave og brug kommandoen START SLAVE"
        nla "Deze operatie vereist een actieve slave, configureer slave en doe dan START SLAVE"
        eng "This operation requires a running replica; configure replica and do START REPLICA"
        fre "Cette opération nécessite un esclave actif, configurez les esclaves et faites START SLAVE"
        ger "Diese Operation benötigt einen aktiven Slave. Bitte Slave konfigurieren und mittels START SLAVE aktivieren"
        ita "Questa operaione richiede un database 'slave', configurarlo ed eseguire START SLAVE"
        jpn "この処理は、稼働中のスレーブでなければ実行できません。スレーブの設定をしてSTART SLAVEコマンドを実行してください。"
        por "Esta operação requer um 'slave' em execução. Configure  o 'slave' e execute START SLAVE"
        rus "Для этой операции требуется работающий подчиненный сервер. Сначала выполните START SLAVE"
        serbian "Ova operacija zahteva da je aktivan podređeni server. Konfigurišite prvo podređeni server i onda izvršite komandu 'START SLAVE'"
        spa "Esta operación necesita el esclavo funcionando, configure esclavo y haga el START SLAVE"
        swe "Denna operation kan endast göras under replikering; Konfigurera slaven och gör START SLAVE"
        ukr "Операція вимагає запущеного підлеглого, зконфігуруйте підлеглого та виконайте START SLAVE"
ER_BAD_REPLICA
        dan "Denne server er ikke konfigureret som slave. Ret in config-filen eller brug kommandoen CHANGE MASTER TO"
        nla "De server is niet geconfigureerd als slave, fix in configuratie bestand of met CHANGE MASTER TO"
        eng "The server is not configured as replica; fix in config file or with CHANGE REPLICATION SOURCE TO"
        fre "Le server n'est pas configuré comme un esclave, changez le fichier de configuration ou utilisez CHANGE MASTER TO"
        ger "Der Server ist nicht als Slave konfiguriert. Bitte in der Konfigurationsdatei oder mittels CHANGE MASTER TO beheben"
        ita "Il server non e' configurato come 'slave', correggere il file di configurazione cambiando CHANGE MASTER TO"
        jpn "このサーバーはスレーブとして設定されていません。コンフィグファイルかCHANGE MASTER TOコマンドで設定して下さい。"
        por "O servidor não está configurado como 'slave'. Acerte o arquivo de configuração ou use CHANGE MASTER TO"
        rus "Этот сервер не настроен как подчиненный. Внесите исправления в конфигурационном файле или с помощью CHANGE MASTER TO"
        serbian "Server nije konfigurisan kao podređeni server, ispravite konfiguracioni file ili na njemu izvršite komandu 'CHANGE MASTER TO'"
        spa "El servidor no está configurado como esclavo, edite el archivo config file o con CHANGE MASTER TO"
        swe "Servern är inte konfigurerade som en replikationsslav. Ändra konfigurationsfilen eller gör CHANGE MASTER TO"
        ukr "Сервер не зконфігуровано як підлеглий, виправте це у файлі конфігурації або з CHANGE MASTER TO"
ER_CONNECTION_METADATA
        eng "Could not initialize connection metadata structure; more error messages can be found in the MySQL error log"
        fre "Impossible d'initialiser les structures d'information de maître, vous trouverez des messages d'erreur supplémentaires dans le journal des erreurs de MySQL"
        ger "Konnte Master-Info-Struktur nicht initialisieren. Weitere Fehlermeldungen können im MySQL-Error-Log eingesehen werden"
        jpn "'master info'構造体の初期化ができませんでした。MySQLエラーログでエラーメッセージを確認してください。"
        serbian "Nisam mogao da inicijalizujem informacionu strukturu glavnog servera, proverite da li imam privilegije potrebne za pristup file-u 'master.info'"
        swe "Kunde inte initialisera replikationsstrukturerna. See MySQL fel fil för mera information"
ER_REPLICA_THREAD
        dan "Kunne ikke danne en slave-tråd; check systemressourcerne"
        nla "Kon slave thread niet aanmaken, controleer systeem resources"
        eng "Could not create replica thread; check system resources"
        fre "Impossible de créer une tâche esclave, vérifiez les ressources système"
        ger "Konnte Slave-Thread nicht starten. Bitte System-Ressourcen überprüfen"
        ita "Impossibile creare il thread 'slave', controllare le risorse di sistema"
        jpn "スレーブスレッドを作成できません。システムリソースを確認してください。"
        por "Não conseguiu criar 'thread' de 'slave'. Verifique os recursos do sistema"
        rus "Невозможно создать поток подчиненного сервера. Проверьте системные ресурсы"
        serbian "Nisam mogao da startujem thread za podređeni server, proverite sistemske resurse"
        spa "No puedo crear el thread esclavo, verifique recursos del sistema"
        swe "Kunde inte starta en tråd för replikering"
        ukr "Не можу створити підлеглу гілку, перевірте системні ресурси"
ER_TOO_MANY_USER_CONNECTIONS 42000
        dan "Brugeren %-.64s har allerede mere end 'max_user_connections' aktive forbindelser"
        nla "Gebruiker %-.64s heeft reeds meer dan 'max_user_connections' actieve verbindingen"
        eng "User %-.64s already has more than 'max_user_connections' active connections"
        est "Kasutajal %-.64s on juba rohkem ühendusi kui lubatud 'max_user_connections' muutujaga"
        fre "L'utilisateur %-.64s possède déjà plus de 'max_user_connections' connexions actives"
        ger "Benutzer '%-.64s' hat mehr als 'max_user_connections' aktive Verbindungen"
        ita "L'utente %-.64s ha gia' piu' di 'max_user_connections' connessioni attive"
        jpn "ユーザー '%-.64s' はすでに 'max_user_connections' 以上のアクティブな接続を行っています。"
        por "Usuário '%-.64s' já possui mais que o valor máximo de conexões (max_user_connections) ativas"
        rus "У пользователя %-.64s уже больше чем 'max_user_connections' активных соединений"
        serbian "Korisnik %-.64s već ima više aktivnih konekcija nego što je to određeno 'max_user_connections' promenljivom"
        spa "Usario %-.64s ya tiene mas que 'max_user_connections' conexiones activas"
        swe "Användare '%-.64s' har redan 'max_user_connections' aktiva inloggningar"
        ukr "Користувач %-.64s вже має більше ніж 'max_user_connections' активних з'єднань"
ER_SET_CONSTANTS_ONLY
        dan "Du må kun bruge konstantudtryk med SET"
        nla "U mag alleen constante expressies gebruiken bij SET"
        eng "You may only use constant expressions with SET"
        est "Ainult konstantsed suurused on lubatud SET klauslis"
        fre "Seules les expressions constantes sont autorisées avec SET"
        ger "Bei SET dürfen nur konstante Ausdrücke verwendet werden"
        ita "Si possono usare solo espressioni costanti con SET"
        jpn "SET処理が失敗しました。"
        por "Você pode usar apenas expressões constantes com SET"
        rus "Вы можете использовать в SET только константные выражения"
        serbian "Možete upotrebiti samo konstantan iskaz sa komandom 'SET'"
        spa "Tu solo debes usar expresiones constantes con SET"
        swe "Man kan endast använda konstantuttryck med SET"
        ukr "Можна використовувати лише вирази зі сталими у SET"
ER_LOCK_WAIT_TIMEOUT
        dan "Lock wait timeout overskredet"
        nla "Lock wacht tijd overschreden"
        eng "Lock wait timeout exceeded; try restarting transaction"
        est "Kontrollaeg ületatud luku järel ootamisel; Proovi transaktsiooni otsast alata"
        fre "Timeout sur l'obtention du verrou"
        ger "Beim Warten auf eine Sperre wurde die zulässige Wartezeit überschritten. Bitte versuchen Sie, die Transaktion neu zu starten"
        ita "E' scaduto il timeout per l'attesa del lock"
        jpn "ロック待ちがタイムアウトしました。トランザクションを再試行してください。"
        por "Tempo de espera (timeout) de travamento excedido. Tente reiniciar a transação."
        rus "Таймаут ожидания блокировки истек; попробуйте перезапустить транзакцию"
        serbian "Vremenski limit za zaključavanje tabele je istekao; Probajte da ponovo startujete transakciju"
        spa "Tiempo de bloqueo de espera excedido"
        swe "Fick inte ett lås i tid ; Försök att starta om transaktionen"
        ukr "Затримку очікування блокування вичерпано"
ER_LOCK_TABLE_FULL
        dan "Det totale antal låse overstiger størrelsen på låse-tabellen"
        nla "Het totale aantal locks overschrijdt de lock tabel grootte"
        eng "The total number of locks exceeds the lock table size"
        est "Lukkude koguarv ületab lukutabeli suuruse"
        fre "Le nombre total de verrou dépasse la taille de la table des verrous"
        ger "Die Gesamtzahl der Sperren überschreitet die Größe der Sperrtabelle"
        ita "Il numero totale di lock e' maggiore della grandezza della tabella di lock"
        jpn "ロックの数が多すぎます。"
        por "O número total de travamentos excede o tamanho da tabela de travamentos"
        rus "Общее количество блокировок превысило размеры таблицы блокировок"
        serbian "Broj totalnih zaključavanja tabele premašuje veličinu tabele zaključavanja"
        spa "El número total de bloqueos excede el tamaño de bloqueo de la tabla"
        swe "Antal lås överskrider antalet reserverade lås"
        ukr "Загальна кількість блокувань перевищила розмір блокувань для таблиці"
ER_READ_ONLY_TRANSACTION 25000
        dan "Update lås kan ikke opnås under en READ UNCOMMITTED transaktion"
        nla "Update locks kunnen niet worden verkregen tijdens een READ UNCOMMITTED transactie"
        eng "Update locks cannot be acquired during a READ UNCOMMITTED transaction"
        est "Uuenduslukke ei saa kasutada READ UNCOMMITTED transaktsiooni käigus"
        fre "Un verrou en update ne peut être acquit pendant une transaction READ UNCOMMITTED"
        ger "Während einer READ-UNCOMMITTED-Transaktion können keine UPDATE-Sperren angefordert werden"
        ita "I lock di aggiornamento non possono essere acquisiti durante una transazione 'READ UNCOMMITTED'"
        jpn "読み込み専用トランザクションです。"
        por "Travamentos de atualização não podem ser obtidos durante uma transação de tipo READ UNCOMMITTED"
        rus "Блокировки обновлений нельзя получить в процессе чтения не принятой (в режиме READ UNCOMMITTED) транзакции"
        serbian "Zaključavanja izmena ne mogu biti realizovana sve dok traje 'READ UNCOMMITTED' transakcija"
        spa "Bloqueos de actualización no pueden ser adqueridos durante una transición READ UNCOMMITTED"
        swe "Updateringslås kan inte göras när man använder READ UNCOMMITTED"
        ukr "Оновити блокування не можливо на протязі транзакції READ UNCOMMITTED"
OBSOLETE_ER_DROP_DB_WITH_READ_LOCK
        dan "DROP DATABASE er ikke tilladt mens en tråd holder på globalt read lock"
        nla "DROP DATABASE niet toegestaan terwijl thread een globale 'read lock' bezit"
        eng "DROP DATABASE not allowed while thread is holding global read lock"
        est "DROP DATABASE ei ole lubatud kui lõim omab globaalset READ lukku"
        fre "DROP DATABASE n'est pas autorisée pendant qu'une tâche possède un verrou global en lecture"
        ger "DROP DATABASE ist nicht erlaubt, solange der Thread eine globale Lesesperre hält"
        ita "DROP DATABASE non e' permesso mentre il thread ha un lock globale di lettura"
        jpn "グローバルリードロックを保持している間は、DROP DATABASE を実行できません。"
        por "DROP DATABASE não permitido enquanto uma 'thread' está mantendo um travamento global de leitura"
        rus "Не допускается DROP DATABASE, пока поток держит глобальную блокировку чтения"
        serbian "Komanda 'DROP DATABASE' nije dozvoljena dok thread globalno zaključava čitanje podataka"
        spa "DROP DATABASE no permitido mientras un thread está ejerciendo un bloqueo de lectura global"
        swe "DROP DATABASE är inte tillåtet när man har ett globalt läslås"
        ukr "DROP DATABASE не дозволено доки гілка перебуває під загальним блокуванням читання"
OBSOLETE_ER_CREATE_DB_WITH_READ_LOCK
        dan "CREATE DATABASE er ikke tilladt mens en tråd holder på globalt read lock"
        nla "CREATE DATABASE niet toegestaan terwijl thread een globale 'read lock' bezit"
        eng "CREATE DATABASE not allowed while thread is holding global read lock"
        est "CREATE DATABASE ei ole lubatud kui lõim omab globaalset READ lukku"
        fre "CREATE DATABASE n'est pas autorisée pendant qu'une tâche possède un verrou global en lecture"
        ger "CREATE DATABASE ist nicht erlaubt, solange der Thread eine globale Lesesperre hält"
        ita "CREATE DATABASE non e' permesso mentre il thread ha un lock globale di lettura"
        jpn "グローバルリードロックを保持している間は、CREATE DATABASE を実行できません。"
        por "CREATE DATABASE não permitido enquanto uma 'thread' está mantendo um travamento global de leitura"
        rus "Не допускается CREATE DATABASE, пока поток держит глобальную блокировку чтения"
        serbian "Komanda 'CREATE DATABASE' nije dozvoljena dok thread globalno zaključava čitanje podataka"
        spa "CREATE DATABASE no permitido mientras un thread está ejerciendo un bloqueo de lectura global"
        swe "CREATE DATABASE är inte tillåtet när man har ett globalt läslås"
        ukr "CREATE DATABASE не дозволено доки гілка перебуває під загальним блокуванням читання"
ER_WRONG_ARGUMENTS
        nla "Foutieve parameters voor %s"
        eng "Incorrect arguments to %s"
        est "Vigased parameetrid %s-le"
        fre "Mauvais arguments à %s"
        ger "Falsche Argumente für %s"
        ita "Argomenti errati a %s"
        jpn "%s の引数が不正です"
        por "Argumentos errados para %s"
        rus "Неверные параметры для %s"
        serbian "Pogrešni argumenti prosleđeni na %s"
        spa "Argumentos errados para %s"
        swe "Felaktiga argument till %s"
        ukr "Хибний аргумент для %s"
ER_NO_PERMISSION_TO_CREATE_USER 42000
        nla "'%-.48s'@'%-.64s' mag geen nieuwe gebruikers creeren"
        eng "'%-.48s'@'%-.64s' is not allowed to create new users"
        est "Kasutajal '%-.48s'@'%-.64s' ei ole lubatud luua uusi kasutajaid"
        fre "'%-.48s'@'%-.64s' n'est pas autorisé à créer de nouveaux utilisateurs"
        ger "'%-.48s'@'%-.64s' ist nicht berechtigt, neue Benutzer hinzuzufügen"
        ita "A '%-.48s'@'%-.64s' non e' permesso creare nuovi utenti"
        jpn "'%-.48s'@'%-.64s' は新しいユーザーを作成できません。"
        por "Não é permitido a '%-.48s'@'%-.64s' criar novos usuários"
        rus "'%-.48s'@'%-.64s' не разрешается создавать новых пользователей"
        serbian "Korisniku '%-.48s'@'%-.64s' nije dozvoljeno da kreira nove korisnike"
        spa "'%-.48s`@`%-.64s` no es permitido para crear nuevos usuarios"
        swe "'%-.48s'@'%-.64s' har inte rättighet att skapa nya användare"
        ukr "Користувачу '%-.48s'@'%-.64s' не дозволено створювати нових користувачів"
OBSOLETE_ER_UNION_TABLES_IN_DIFFERENT_DIR
        nla "Incorrecte tabel definitie; alle MERGE tabellen moeten tot dezelfde database behoren"
        eng "Incorrect table definition; all MERGE tables must be in the same database"
        est "Vigane tabelimääratlus; kõik MERGE tabeli liikmed peavad asuma samas andmebaasis"
        fre "Définition de table incorrecte; toutes les tables MERGE doivent être dans la même base de donnée"
        ger "Falsche Tabellendefinition. Alle MERGE-Tabellen müssen sich in derselben Datenbank befinden"
        ita "Definizione della tabella errata; tutte le tabelle di tipo MERGE devono essere nello stesso database"
        jpn "不正な表定義です。MERGE表の構成表はすべて同じデータベース内になければなりません。"
        por "Definição incorreta da tabela. Todas as tabelas contidas na junção devem estar no mesmo banco de dados."
        rus "Неверное определение таблицы; Все таблицы в MERGE должны принадлежать одной и той же базе данных"
        serbian "Pogrešna definicija tabele; sve 'MERGE' tabele moraju biti u istoj bazi podataka"
        spa "Incorrecta definición de la tabla; Todas las tablas MERGE deben estar en el mismo banco de datos"
        swe "Felaktig tabelldefinition; alla tabeller i en MERGE-tabell måste vara i samma databas"
ER_LOCK_DEADLOCK 40001
        nla "Deadlock gevonden tijdens lock-aanvraag poging; Probeer herstart van de transactie"
        eng "Deadlock found when trying to get lock; try restarting transaction"
        est "Lukustamisel tekkis tupik (deadlock); alusta transaktsiooni otsast"
        fre "Deadlock découvert en essayant d'obtenir les verrous : essayez de redémarrer la transaction"
        ger "Beim Versuch, eine Sperre anzufordern, ist ein Deadlock aufgetreten. Versuchen Sie, die Transaktion neu zu starten"
        ita "Trovato deadlock durante il lock; Provare a far ripartire la transazione"
        jpn "ロック取得中にデッドロックが検出されました。トランザクションを再試行してください。"
        por "Encontrado um travamento fatal (deadlock) quando tentava obter uma trava. Tente reiniciar a transação."
        rus "Возникла тупиковая ситуация в процессе получения блокировки; Попробуйте перезапустить транзакцию"
        serbian "Unakrsno zaključavanje pronađeno kada sam pokušao da dobijem pravo na zaključavanje; Probajte da restartujete transakciju"
        spa "Encontrado deadlock cuando tentando obtener el bloqueo; Tente recomenzar la transición"
        swe "Fick 'DEADLOCK' vid låsförsök av block/rad. Försök att starta om transaktionen"
ER_TABLE_CANT_HANDLE_FT
        nla "Het gebruikte tabel type ondersteund geen FULLTEXT indexen"
        eng "The used table type doesn't support FULLTEXT indexes"
        est "Antud tabelitüüp ei toeta FULLTEXT indekseid"
        fre "Le type de table utilisé ne supporte pas les index FULLTEXT"
        ger "Der verwendete Tabellentyp unterstützt keine FULLTEXT-Indizes"
        ita "La tabella usata non supporta gli indici FULLTEXT"
        jpn "使用の表は全文索引を利用できません。"
        por "O tipo de tabela utilizado não suporta índices de texto completo (fulltext indexes)"
        rus "Используемый тип таблиц не поддерживает полнотекстовых индексов"
        serbian "Upotrebljeni tip tabele ne podržava 'FULLTEXT' indekse"
        spa "El tipo de tabla usada no soporta índices FULLTEXT"
        swe "Tabelltypen har inte hantering av FULLTEXT-index"
        ukr "Використаний тип таблиці не підтримує FULLTEXT індексів"
ER_CANNOT_ADD_FOREIGN
        nla "Kan foreign key beperking niet toevoegen"
        eng "Cannot add foreign key constraint"
        fre "Impossible d'ajouter des contraintes d'index externe"
        ger "Fremdschlüssel-Beschränkung kann nicht hinzugefügt werden"
        ita "Impossibile aggiungere il vincolo di integrita' referenziale (foreign key constraint)"
        jpn "外部キー制約を追加できません。"
        por "Não pode acrescentar uma restrição de chave estrangeira"
        rus "Невозможно добавить ограничения внешнего ключа"
        serbian "Ne mogu da dodam proveru spoljnog ključa"
        spa "No puede adicionar clave extranjera constraint"
        swe "Kan inte lägga till 'FOREIGN KEY constraint'"
ER_NO_REFERENCED_ROW 23000
        nla "Kan onderliggende rij niet toevoegen: foreign key beperking gefaald"
        eng "Cannot add or update a child row: a foreign key constraint fails"
        fre "Impossible d'ajouter un enregistrement fils : une constrainte externe l'empèche"
        ger "Hinzufügen oder Aktualisieren eines Kind-Datensatzes schlug aufgrund einer Fremdschlüssel-Beschränkung fehl"
        greek "Cannot add a child row: a foreign key constraint fails"
        hun "Cannot add a child row: a foreign key constraint fails"
        ita "Impossibile aggiungere la riga: un vincolo d'integrita' referenziale non e' soddisfatto"
        jpn "親キーがありません。外部キー制約違反です。"
        norwegian-ny "Cannot add a child row: a foreign key constraint fails"
        por "Não pode acrescentar uma linha filha: uma restrição de chave estrangeira falhou"
        rus "Невозможно добавить или обновить дочернюю строку: проверка ограничений внешнего ключа не выполняется"
        spa "No puede adicionar una línea hijo: falla de clave extranjera constraint"
        swe "FOREIGN KEY-konflikt:  Kan inte skriva barn"
ER_ROW_IS_REFERENCED 23000
        eng "Cannot delete or update a parent row: a foreign key constraint fails"
        fre "Impossible de supprimer un enregistrement père : une constrainte externe l'empèche"
        ger "Löschen oder Aktualisieren eines Eltern-Datensatzes schlug aufgrund einer Fremdschlüssel-Beschränkung fehl"
        greek "Cannot delete a parent row: a foreign key constraint fails"
        hun "Cannot delete a parent row: a foreign key constraint fails"
        ita "Impossibile cancellare la riga: un vincolo d'integrita' referenziale non e' soddisfatto"
        jpn "子レコードがあります。外部キー制約違反です。"
        por "Não pode apagar uma linha pai: uma restrição de chave estrangeira falhou"
        rus "Невозможно удалить или обновить родительскую строку: проверка ограничений внешнего ключа не выполняется"
        serbian "Ne mogu da izbrišem roditeljski slog: provera spoljnog ključa je neuspela"
        spa "No puede deletar una línea padre: falla de clave extranjera constraint"
        swe "FOREIGN KEY-konflikt:  Kan inte radera fader"
ER_CONNECT_TO_SOURCE 08S01
        nla "Fout bij opbouwen verbinding naar master: %-.128s"
        eng "Error connecting to source: %-.128s"
        ger "Fehler bei der Verbindung zum Master: %-.128s"
        ita "Errore durante la connessione al master: %-.128s"
        jpn "マスターへの接続エラー: %-.128s"
        por "Erro conectando com o master: %-.128s"
        rus "Ошибка соединения с головным сервером: %-.128s"
        spa "Error de coneccion a master: %-.128s"
        swe "Fick fel vid anslutning till master: %-.128s"
OBSOLETE_ER_QUERY_ON_MASTER
        nla "Fout bij uitvoeren query op master: %-.128s"
        eng "Error running query on source: %-.128s"
        ger "Beim Ausführen einer Abfrage auf dem Master trat ein Fehler auf: %-.128s"
        ita "Errore eseguendo una query sul master: %-.128s"
        jpn "マスターでのクエリ実行エラー: %-.128s"
        por "Erro rodando consulta no master: %-.128s"
        rus "Ошибка выполнения запроса на головном сервере: %-.128s"
        spa "Error executando el query en master: %-.128s"
        swe "Fick fel vid utförande av command på mastern: %-.128s"
ER_ERROR_WHEN_EXECUTING_COMMAND
        nla "Fout tijdens uitvoeren van commando %s: %-.128s"
        eng "Error when executing command %s: %-.128s"
        est "Viga käsu %s täitmisel: %-.128s"
        ger "Fehler beim Ausführen des Befehls %s: %-.128s"
        ita "Errore durante l'esecuzione del comando %s: %-.128s"
        jpn "%s コマンドの実行エラー: %-.128s"
        por "Erro quando executando comando %s: %-.128s"
        rus "Ошибка при выполнении команды %s: %-.128s"
        serbian "Greška pri izvršavanju komande %s: %-.128s"
        spa "Error de %s: %-.128s"
        swe "Fick fel vid utförande av %s: %-.128s"
ER_WRONG_USAGE
        nla "Foutief gebruik van %s en %s"
        eng "Incorrect usage of %s and %s"
        est "Vigane %s ja %s kasutus"
        ger "Falsche Verwendung von %s und %s"
        ita "Uso errato di %s e %s"
        jpn "%s の %s に関する不正な使用法です。"
        por "Uso errado de %s e %s"
        rus "Неверное использование %s и %s"
        serbian "Pogrešna upotreba %s i %s"
        spa "Equivocado uso de %s y  %s"
        swe "Felaktig använding av %s and %s"
        ukr "Wrong usage of %s and %s"
ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT 21000
        nla "De gebruikte SELECT commando's hebben een verschillend aantal kolommen"
        eng "The used SELECT statements have a different number of columns"
        est "Tulpade arv kasutatud SELECT lausetes ei kattu"
        ger "Die verwendeten SELECT-Befehle liefern unterschiedliche Anzahlen von Feldern zurück"
        ita "La SELECT utilizzata ha un numero di colonne differente"
        jpn "使用のSELECT文が返す列数が違います。"
        por "Os comandos SELECT usados têm diferente número de colunas"
        rus "Использованные операторы выборки (SELECT) дают разное количество столбцов"
        serbian "Upotrebljene 'SELECT' komande adresiraju različit broj kolona"
        spa "El comando SELECT usado tiene diferente número de columnas"
        swe "SELECT-kommandona har olika antal kolumner"
ER_CANT_UPDATE_WITH_READLOCK
        nla "Kan de query niet uitvoeren vanwege een conflicterende read lock"
        eng "Can't execute the query because you have a conflicting read lock"
        est "Ei suuda täita päringut konfliktse luku tõttu"
        ger "Augrund eines READ-LOCK-Konflikts kann die Abfrage nicht ausgeführt werden"
        ita "Impossibile eseguire la query perche' c'e' un conflitto con in lock di lettura"
        jpn "競合するリードロックを保持しているので、クエリを実行できません。"
        por "Não posso executar a consulta porque você tem um conflito de travamento de leitura"
        rus "Невозможно исполнить запрос, поскольку у вас установлены конфликтующие блокировки чтения"
        serbian "Ne mogu da izvršim upit zbog toga što imate zaključavanja čitanja podataka u konfliktu"
        spa "No puedo ejecutar el query  porque usted tiene conflicto de traba de lectura"
        swe "Kan inte utföra kommandot emedan du har ett READ-lås"
ER_MIXING_NOT_ALLOWED
        nla "Het combineren van transactionele en niet-transactionele tabellen is uitgeschakeld."
        eng "Mixing of transactional and non-transactional tables is disabled"
        est "Transaktsioone toetavate ning mittetoetavate tabelite kooskasutamine ei ole lubatud"
        ger "Die gleichzeitige Verwendung von Tabellen mit und ohne Transaktionsunterstützung ist deaktiviert"
        ita "E' disabilitata la possibilita' di mischiare tabelle transazionali e non-transazionali"
        jpn "トランザクション対応の表と非対応の表の同時使用は無効化されています。"
        por "Mistura de tabelas transacional e não-transacional está desabilitada"
        rus "Использование транзакционных таблиц наряду с нетранзакционными запрещено"
        serbian "Mešanje tabela koje podržavaju transakcije i onih koje ne podržavaju transakcije je isključeno"
        spa "Mezla de transancional y no-transancional tablas está deshabilitada"
        swe "Blandning av transaktionella och icke-transaktionella tabeller är inaktiverat"
ER_DUP_ARGUMENT
        nla "Optie '%s' tweemaal gebruikt in opdracht"
        eng "Option '%s' used twice in statement"
        est "Määrangut '%s' on lauses kasutatud topelt"
        ger "Option '%s' wird im Befehl zweimal verwendet"
        ita "L'opzione '%s' e' stata usata due volte nel comando"
        jpn "オプション '%s' が2度使用されています。"
        por "Opção '%s' usada duas vezes no comando"
        rus "Опция '%s' дважды использована в выражении"
        spa "Opción '%s' usada dos veces en el comando"
        swe "Option '%s' användes två gånger"
ER_USER_LIMIT_REACHED 42000
        nla "Gebruiker '%-.64s' heeft het maximale gebruik van de '%s' faciliteit overschreden (huidige waarde: %ld)"
        eng "User '%-.64s' has exceeded the '%s' resource (current value: %ld)"
        ger "Benutzer '%-.64s' hat die Ressourcenbeschränkung '%s' überschritten (aktueller Wert: %ld)"
        ita "L'utente '%-.64s' ha ecceduto la risorsa '%s' (valore corrente: %ld)"
        jpn "ユーザー '%-.64s' はリソースの上限 '%s' に達しました。(現在値: %ld)"
        por "Usuário '%-.64s' tem excedido o '%s' recurso (atual valor: %ld)"
        rus "Пользователь '%-.64s' превысил использование ресурса '%s' (текущее значение: %ld)"
        spa "Usuario '%-.64s' ha excedido el recurso '%s' (actual valor: %ld)"
        swe "Användare '%-.64s' har överskridit '%s' (nuvarande värde: %ld)"
ER_SPECIFIC_ACCESS_DENIED_ERROR 42000
        nla "Toegang geweigerd. U moet het %-.128s privilege hebben voor deze operatie"
        eng "Access denied; you need (at least one of) the %-.128s privilege(s) for this operation"
        ger "Kein Zugriff. Hierfür wird die Berechtigung %-.128s benötigt"
        ita "Accesso non consentito. Serve il privilegio %-.128s per questa operazione"
        jpn "アクセスは拒否されました。この操作には %-.128s 権限が(複数の場合はどれか1つ)必要です。"
        por "Acesso negado. Você precisa o privilégio %-.128s para essa operação"
        rus "В доступе отказано. Вам нужны привилегии %-.128s для этой операции"
        spa "Acceso negado. Usted necesita el privilegio %-.128s para esta operación"
        swe "Du har inte privlegiet '%-.128s' som behövs för denna operation"
        ukr "Access denied. You need the %-.128s privilege for this operation"
ER_LOCAL_VARIABLE
        nla "Variabele '%-.64s' is SESSION en kan niet worden gebruikt met SET GLOBAL"
        eng "Variable '%-.64s' is a SESSION variable and can't be used with SET GLOBAL"
        ger "Variable '%-.64s' ist eine lokale Variable und kann nicht mit SET GLOBAL verändert werden"
        ita "La variabile '%-.64s' e' una variabile locale ( SESSION ) e non puo' essere cambiata usando SET GLOBAL"
        jpn "変数 '%-.64s' はセッション変数です。SET GLOBALでは使用できません。"
        por "Variável '%-.64s' é uma SESSION variável e não pode ser usada com SET GLOBAL"
        rus "Переменная '%-.64s' является потоковой (SESSION) переменной и не может быть изменена с помощью SET GLOBAL"
        spa "Variable '%-.64s' es una SESSION variable y no puede ser usada con SET GLOBAL"
        swe "Variabel '%-.64s' är en SESSION variabel och kan inte ändrad med SET GLOBAL"
ER_GLOBAL_VARIABLE
        nla "Variabele '%-.64s' is GLOBAL en dient te worden gewijzigd met SET GLOBAL"
        eng "Variable '%-.64s' is a GLOBAL variable and should be set with SET GLOBAL"
        ger "Variable '%-.64s' ist eine globale Variable und muss mit SET GLOBAL verändert werden"
        ita "La variabile '%-.64s' e' una variabile globale ( GLOBAL ) e deve essere cambiata usando SET GLOBAL"
        jpn "変数 '%-.64s' はグローバル変数です。SET GLOBALを使用してください。"
        por "Variável '%-.64s' é uma GLOBAL variável e deve ser configurada com SET GLOBAL"
        rus "Переменная '%-.64s' является глобальной (GLOBAL) переменной, и ее следует изменять с помощью SET GLOBAL"
        spa "Variable '%-.64s' es una GLOBAL variable y no puede ser configurada con SET GLOBAL"
        swe "Variabel '%-.64s' är en GLOBAL variabel och bör sättas med SET GLOBAL"
ER_NO_DEFAULT 42000
        nla "Variabele '%-.64s' heeft geen standaard waarde"
        eng "Variable '%-.64s' doesn't have a default value"
        ger "Variable '%-.64s' hat keinen Vorgabewert"
        ita "La variabile '%-.64s' non ha un valore di default"
        jpn "変数 '%-.64s' にはデフォルト値がありません。"
        por "Variável '%-.64s' não tem um valor padrão"
        rus "Переменная '%-.64s' не имеет значения по умолчанию"
        spa "Variable '%-.64s' no tiene un valor patrón"
        swe "Variabel '%-.64s' har inte ett DEFAULT-värde"
ER_WRONG_VALUE_FOR_VAR 42000
        nla "Variabele '%-.64s' kan niet worden gewijzigd naar de waarde '%-.200s'"
        eng "Variable '%-.64s' can't be set to the value of '%-.200s'"
        ger "Variable '%-.64s' kann nicht auf '%-.200s' gesetzt werden"
        ita "Alla variabile '%-.64s' non puo' essere assegato il valore '%-.200s'"
        jpn "変数 '%-.64s' に値 '%-.200s' を設定できません。"
        por "Variável '%-.64s' não pode ser configurada para o valor de '%-.200s'"
        rus "Переменная '%-.64s' не может быть установлена в значение '%-.200s'"
        spa "Variable '%-.64s' no puede ser configurada para el valor de '%-.200s'"
        swe "Variabel '%-.64s' kan inte sättas till '%-.200s'"
ER_WRONG_TYPE_FOR_VAR 42000
        nla "Foutief argumenttype voor variabele '%-.64s'"
        eng "Incorrect argument type to variable '%-.64s'"
        ger "Falscher Argumenttyp für Variable '%-.64s'"
        ita "Tipo di valore errato per la variabile '%-.64s'"
        jpn "変数 '%-.64s' への値の型が不正です。"
        por "Tipo errado de argumento para variável '%-.64s'"
        rus "Неверный тип аргумента для переменной '%-.64s'"
        spa "Tipo de argumento equivocado para variable '%-.64s'"
        swe "Fel typ av argument till variabel '%-.64s'"
ER_VAR_CANT_BE_READ
        nla "Variabele '%-.64s' kan alleen worden gewijzigd, niet gelezen"
        eng "Variable '%-.64s' can only be set, not read"
        ger "Variable '%-.64s' kann nur verändert, nicht gelesen werden"
        ita "Alla variabile '%-.64s' e' di sola scrittura quindi puo' essere solo assegnato un valore, non letto"
        jpn "変数 '%-.64s' は書き込み専用です。読み込みはできません。"
        por "Variável '%-.64s' somente pode ser configurada, não lida"
        rus "Переменная '%-.64s' может быть только установлена, но не считана"
        spa "Variable '%-.64s' solamente puede ser configurada, no leída"
        swe "Variabeln '%-.64s' kan endast sättas, inte läsas"
ER_CANT_USE_OPTION_HERE 42000
        nla "Foutieve toepassing/plaatsing van '%s'"
        eng "Incorrect usage/placement of '%s'"
        ger "Falsche Verwendung oder Platzierung von '%s'"
        ita "Uso/posizione di '%s' sbagliato"
        jpn "'%s' の使用法または場所が不正です。"
        por "Errado uso/colocação de '%s'"
        rus "Неверное использование или в неверном месте указан '%s'"
        spa "Equivocado uso/colocación de '%s'"
        swe "Fel använding/placering av '%s'"
ER_NOT_SUPPORTED_YET 42000
        nla "Deze versie van MySQL ondersteunt nog geen '%s'"
        eng "This version of MySQL doesn't yet support '%s'"
        ger "Diese MySQL-Version unterstützt '%s' nicht"
        ita "Questa versione di MySQL non supporta ancora '%s'"
        jpn "このバージョンのMySQLでは、まだ '%s' を利用できません。"
        por "Esta versão de MySQL não suporta ainda '%s'"
        rus "Эта версия MySQL пока еще не поддерживает '%s'"
        spa "Esta versión de MySQL no soporta todavia '%s'"
        swe "Denna version av MySQL kan ännu inte utföra '%s'"
ER_SOURCE_FATAL_ERROR_READING_BINLOG
        nla "Kreeg fatale fout %d: '%-.512s' van master tijdens lezen van data uit binaire log"
        eng "Got fatal error %d from source when reading data from binary log: '%-.512s'"
        ger "Schwerer Fehler %d: '%-.512s vom Master beim Lesen des binären Logs"
        ita "Errore fatale %d: '%-.512s' dal master leggendo i dati dal log binario"
        jpn "致命的なエラー %d: '%-.512s' がマスターでバイナリログ読み込み中に発生しました。"
        por "Obteve fatal erro %d: '%-.512s' do master quando lendo dados do binary log"
        rus "Получена неисправимая ошибка %d: '%-.512s' от головного сервера в процессе выборки данных из двоичного журнала"
        spa "Recibió fatal error %d: '%-.512s' del master cuando leyendo datos del binary log"
        swe "Fick fatalt fel %d: '%-.512s' från master vid läsning av binärloggen"

ER_REPLICA_IGNORED_TABLE
        eng "Replica SQL thread ignored the query because of replicate-*-table rules"
        ger "Slave-SQL-Thread hat die Abfrage aufgrund von replicate-*-table-Regeln ignoriert"
        jpn "replicate-*-table ルールに従って、スレーブSQLスレッドはクエリを無視しました。"
        nla "Slave SQL thread negeerde de query vanwege replicate-*-table opties"
        por "Slave SQL thread ignorado a consulta devido às normas de replicação-*-tabela"
        spa "Slave SQL thread ignorado el query debido a las reglas de replicación-*-tabla"
        swe "Slav SQL tråden ignorerade frågan pga en replicate-*-table regel"
ER_INCORRECT_GLOBAL_LOCAL_VAR
        eng "Variable '%-.192s' is a %s variable"
        serbian "Promenljiva '%-.192s' je %s promenljiva"
        ger "Variable '%-.192s' ist eine %s-Variable"
        jpn "変数 '%-.192s' は %s 変数です。"
        nla "Variabele '%-.192s' is geen %s variabele"
        spa "Variable '%-.192s' es una %s variable"
        swe "Variabel '%-.192s' är av typ %s"
ER_WRONG_FK_DEF 42000
        eng "Incorrect foreign key definition for '%-.192s': %s"
        ger "Falsche Fremdschlüssel-Definition für '%-.192s': %s"
        jpn "外部キー '%-.192s' の定義の不正: %s"
        nla "Incorrecte foreign key definitie voor '%-.192s': %s"
        por "Definição errada da chave estrangeira para '%-.192s': %s"
        spa "Equivocada definición de llave extranjera para '%-.192s': %s"
        swe "Felaktig FOREIGN KEY-definition för '%-.192s': %s"
ER_KEY_REF_DO_NOT_MATCH_TABLE_REF
        eng "Key reference and table reference don't match"
        ger "Schlüssel- und Tabellenverweis passen nicht zusammen"
        jpn "外部キーの参照表と定義が一致しません。"
        nla "Sleutel- en tabelreferentie komen niet overeen"
        por "Referência da chave e referência da tabela não coincidem"
        spa "Referencia de llave y referencia de tabla no coinciden"
        swe "Nyckelreferensen och tabellreferensen stämmer inte överens"
ER_OPERAND_COLUMNS 21000
        eng "Operand should contain %d column(s)"
        ger "Operand sollte %d Spalte(n) enthalten"
        jpn "オペランドに %d 個の列が必要です。"
        nla "Operand behoort %d kolommen te bevatten"
        rus "Операнд должен содержать %d колонок"
        spa "Operando debe tener %d columna(s)"
        ukr "Операнд має складатися з %d стовбців"
ER_SUBQUERY_NO_1_ROW 21000
        eng "Subquery returns more than 1 row"
        ger "Unterabfrage lieferte mehr als einen Datensatz zurück"
        jpn "サブクエリが2行以上の結果を返します。"
        nla "Subquery retourneert meer dan 1 rij"
        por "Subconsulta retorna mais que 1 registro"
        rus "Подзапрос возвращает более одной записи"
        spa "Subconsulta retorna mas que 1 línea"
        swe "Subquery returnerade mer än 1 rad"
        ukr "Підзапит повертає більш нiж 1 запис"
ER_UNKNOWN_STMT_HANDLER
        dan "Unknown prepared statement handler (%.*s) given to %s"
        eng "Unknown prepared statement handler (%.*s) given to %s"
        ger "Unbekannter Prepared-Statement-Handler (%.*s) für %s angegeben"
        jpn "'%.*s' はプリペアードステートメントの不明なハンドルです。(%s で指定されました)"
        nla "Onebekende prepared statement handler (%.*s) voor %s aangegeven"
        por "Desconhecido manipulador de declaração preparado (%.*s) determinado para %s"
        spa "Desconocido preparado comando handler (%.*s) dado para %s"
        swe "Okänd PREPARED STATEMENT id (%.*s) var given till %s"
        ukr "Unknown prepared statement handler (%.*s) given to %s"
ER_CORRUPT_HELP_DB
        eng "Help database is corrupt or does not exist"
        ger "Die Hilfe-Datenbank ist beschädigt oder existiert nicht"
        jpn "ヘルプデータベースは壊れているか存在しません。"
        nla "Help database is beschadigd of bestaat niet"
        por "Banco de dado de ajuda corrupto ou não existente"
        spa "Base de datos Help está corrupto o no existe"
        swe "Hjälpdatabasen finns inte eller är skadad"
OBSOLETE_ER_CYCLIC_REFERENCE
        eng "Cyclic reference on subqueries"
        ger "Zyklischer Verweis in Unterabfragen"
        jpn "サブクエリの参照がループしています。"
        nla "Cyclische verwijzing in subqueries"
        por "Referência cíclica em subconsultas"
        rus "Циклическая ссылка на подзапрос"
        spa "Cíclica referencia en subconsultas"
        swe "Cyklisk referens i subqueries"
        ukr "Циклічне посилання на підзапит"
ER_AUTO_CONVERT
        eng "Converting column '%s' from %s to %s"
        ger "Feld '%s' wird von %s nach %s umgewandelt"
        jpn "列 '%s' を %s から %s へ変換します。"
        nla "Veld '%s' wordt van %s naar %s geconverteerd"
        por "Convertendo coluna '%s' de %s para %s"
        rus "Преобразование поля '%s' из %s в %s"
        spa "Convirtiendo columna '%s' de %s para %s"
        swe "Konvertar kolumn '%s' från %s till %s"
        ukr "Перетворення стовбца '%s' з %s у %s"
ER_ILLEGAL_REFERENCE 42S22
        eng "Reference '%-.64s' not supported (%s)"
        ger "Verweis '%-.64s' wird nicht unterstützt (%s)"
        jpn "'%-.64s' の参照はできません。(%s)"
        nla "Verwijzing '%-.64s' niet ondersteund (%s)"
        por "Referência '%-.64s' não suportada (%s)"
        rus "Ссылка '%-.64s' не поддерживается (%s)"
        spa "Referencia '%-.64s' no soportada (%s)"
        swe "Referens '%-.64s' stöds inte (%s)"
        ukr "Посилання '%-.64s' не пiдтримуется (%s)"
ER_DERIVED_MUST_HAVE_ALIAS 42000
        eng "Every derived table must have its own alias"
        ger "Für jede abgeleitete Tabelle muss ein eigener Alias angegeben werden"
        jpn "導出表には別名が必須です。"
        nla "Voor elke afgeleide tabel moet een unieke alias worden gebruikt"
        por "Cada tabela derivada deve ter seu próprio alias"
        spa "Cada tabla derivada debe tener su propio alias"
        swe "Varje 'derived table' måste ha sitt eget alias"
ER_SELECT_REDUCED 01000
        eng "Select %u was reduced during optimization"
        ger "Select %u wurde während der Optimierung reduziert"
        jpn "Select %u は最適化によって減らされました。"
        nla "Select %u werd geredureerd tijdens optimtalisatie"
        por "Select %u foi reduzido durante otimização"
        rus "Select %u был упразднен в процессе оптимизации"
        spa "Select %u fué reducido durante optimización"
        swe "Select %u reducerades vid optimiering"
        ukr "Select %u was скасовано при оптимiзацii"
ER_TABLENAME_NOT_ALLOWED_HERE 42000
        eng "Table '%-.192s' from one of the SELECTs cannot be used in %-.32s"
        ger "Tabelle '%-.192s', die in einem der SELECT-Befehle verwendet wurde, kann nicht in %-.32s verwendet werden"
        jpn "特定のSELECTのみで使用の表 '%-.192s' は %-.32s では使用できません。"
        nla "Tabel '%-.192s' uit een van de SELECTS kan niet in %-.32s gebruikt worden"
        por "Tabela '%-.192s' de um dos SELECTs não pode ser usada em %-.32s"
        spa "Tabla '%-.192s' de uno de los SELECT no puede ser usada en %-.32s"
        swe "Tabell '%-.192s' från en SELECT kan inte användas i %-.32s"
ER_NOT_SUPPORTED_AUTH_MODE 08004
        eng "Client does not support authentication protocol requested by server; consider upgrading MySQL client"
        ger "Client unterstützt das vom Server erwartete Authentifizierungsprotokoll nicht. Bitte aktualisieren Sie Ihren MySQL-Client"
        jpn "クライアントはサーバーが要求する認証プロトコルに対応できません。MySQLクライアントのアップグレードを検討してください。"
        nla "Client ondersteunt het door de server verwachtte authenticatieprotocol niet. Overweeg een nieuwere MySQL client te gebruiken"
        por "Cliente não suporta o protocolo de autenticação exigido pelo servidor; considere a atualização do cliente MySQL"
        spa "Cliente no soporta protocolo de autenticación solicitado por el servidor; considere actualizar el cliente MySQL"
        swe "Klienten stöder inte autentiseringsprotokollet som begärts av servern; överväg uppgradering av klientprogrammet."
ER_SPATIAL_CANT_HAVE_NULL 42000
        eng "All parts of a SPATIAL index must be NOT NULL"
        ger "Alle Teile eines SPATIAL-Index müssen als NOT NULL deklariert sein"
        jpn "空間索引のキー列は NOT NULL でなければいけません。"
        nla "Alle delete van een  SPATIAL index dienen als NOT NULL gedeclareerd te worden"
        por "Todas as partes de uma SPATIAL index devem ser NOT NULL"
        spa "Todas las partes de una SPATIAL index deben ser NOT NULL"
        swe "Alla delar av en SPATIAL index måste vara NOT NULL"
ER_COLLATION_CHARSET_MISMATCH 42000
        eng "COLLATION '%s' is not valid for CHARACTER SET '%s'"
        ger "COLLATION '%s' ist für CHARACTER SET '%s' ungültig"
        jpn "COLLATION '%s' は CHARACTER SET '%s' に適用できません。"
        nla "COLLATION '%s' is niet geldig voor CHARACTER SET '%s'"
        por "COLLATION '%s' não é válida para CHARACTER SET '%s'"
        spa "COLLATION '%s' no es válido para CHARACTER SET '%s'"
        swe "COLLATION '%s' är inte tillåtet för CHARACTER SET '%s'"
OBSOLETE_ER_SLAVE_WAS_RUNNING
        eng "Replica is already running"
        ger "Slave läuft bereits"
        jpn "スレーブはすでに稼働中です。"
        nla "Slave is reeds actief"
        por "O slave já está rodando"
        spa "Slave ya está funcionando"
        swe "Slaven har redan startat"
OBSOLETE_ER_SLAVE_WAS_NOT_RUNNING
        eng "Replica already has been stopped"
        ger "Slave wurde bereits angehalten"
        jpn "スレーブはすでに停止しています。"
        nla "Slave is reeds gestopt"
        por "O slave já está parado"
        spa "Slave ya fué parado"
        swe "Slaven har redan stoppat"
ER_TOO_BIG_FOR_UNCOMPRESS
        eng "Uncompressed data size too large; the maximum size is %d (probably, length of uncompressed data was corrupted)"
        ger "Unkomprimierte Daten sind zu groß. Die maximale Größe beträgt %d (wahrscheinlich wurde die Länge der unkomprimierten Daten beschädigt)"
        jpn "展開後のデータが大きすぎます。最大サイズは %d です。(展開後データの長さ情報が壊れている可能性もあります。)"
        nla "Ongecomprimeerder data is te groot; de maximum lengte is %d (waarschijnlijk, de lengte van de gecomprimeerde data was beschadigd)"
        por "Tamanho muito grande dos dados des comprimidos. O máximo tamanho é %d. (provavelmente, o comprimento dos dados descomprimidos está corrupto)"
        spa "Tamaño demasiado grande para datos descomprimidos. El máximo tamaño es %d. (probablemente, extensión de datos descomprimidos fué corrompida)"
ER_ZLIB_Z_MEM_ERROR
        eng "ZLIB: Not enough memory"
        ger "ZLIB: Nicht genug Speicher"
        jpn "ZLIB: メモリ不足です。"
        nla "ZLIB: Onvoldoende geheugen"
        por "ZLIB: Não suficiente memória disponível"
        spa "Z_MEM_ERROR: No suficiente memoria para zlib"
ER_ZLIB_Z_BUF_ERROR
        eng "ZLIB: Not enough room in the output buffer (probably, length of uncompressed data was corrupted)"
        ger "ZLIB: Im Ausgabepuffer ist nicht genug Platz vorhanden (wahrscheinlich wurde die Länge der unkomprimierten Daten beschädigt)"
        jpn "ZLIB: 出力バッファに十分な空きがありません。(展開後データの長さ情報が壊れている可能性もあります。)"
        nla "ZLIB: Onvoldoende ruimte in uitgaande buffer (waarschijnlijk, de lengte van de ongecomprimeerde data was beschadigd)"
        por "ZLIB: Não suficiente espaço no buffer emissor (provavelmente, o comprimento dos dados descomprimidos está corrupto)"
        spa "Z_BUF_ERROR: No suficiente espacio en el búfer de salida para zlib (probablemente, extensión de datos descomprimidos fué corrompida)"
ER_ZLIB_Z_DATA_ERROR
        eng "ZLIB: Input data corrupted"
        ger "ZLIB: Eingabedaten beschädigt"
        jpn "ZLIB: 入力データが壊れています。"
        nla "ZLIB: Invoer data beschadigd"
        por "ZLIB: Dados de entrada está corrupto"
        spa "ZLIB: Dato de entrada fué corrompido para zlib"
ER_CUT_VALUE_GROUP_CONCAT
        eng "Row %u was cut by GROUP_CONCAT()"
ER_WARN_TOO_FEW_RECORDS 01000
        eng "Row %ld doesn't contain data for all columns"
        ger "Zeile %ld enthält nicht für alle Felder Daten"
        jpn "行 %ld はすべての列へのデータを含んでいません。"
        nla "Rij %ld bevat niet de data voor alle kolommen"
        por "Conta de registro é menor que a conta de coluna na linha %ld"
        spa "Línea %ld no contiene datos para todas las columnas"
ER_WARN_TOO_MANY_RECORDS 01000
        eng "Row %ld was truncated; it contained more data than there were input columns"
        ger "Zeile %ld gekürzt, die Zeile enthielt mehr Daten, als es Eingabefelder gibt"
        jpn "行 %ld はデータを切り捨てられました。列よりも多いデータを含んでいました。"
        nla "Regel %ld ingekort, bevatte meer data dan invoer kolommen"
        por "Conta de registro é maior que a conta de coluna na linha %ld"
        spa "Línea %ld fué truncada; La misma contine mas datos que las que existen en las columnas de entrada"
ER_WARN_NULL_TO_NOTNULL 22004
        eng "Column set to default value; NULL supplied to NOT NULL column '%s' at row %ld"
        ger "Feld auf Vorgabewert gesetzt, da NULL für NOT-NULL-Feld '%s' in Zeile %ld angegeben"
        jpn "列にデフォルト値が設定されました。NOT NULLの列 '%s' に 行 %ld で NULL が与えられました。"
        por "Dado truncado, NULL fornecido para NOT NULL coluna '%s' na linha %ld"
        spa "Datos truncado, NULL suministrado para NOT NULL columna '%s' en la línea %ld"
ER_WARN_DATA_OUT_OF_RANGE 22003
        eng "Out of range value for column '%s' at row %ld"
WARN_DATA_TRUNCATED 01000
        eng "Data truncated for column '%s' at row %ld"
        ger "Daten abgeschnitten für Feld '%s' in Zeile %ld"
        jpn "列 '%s' の 行 %ld でデータが切り捨てられました。"
        por "Dado truncado para coluna '%s' na linha %ld"
        spa "Datos truncados para columna '%s' en la línea %ld"
ER_WARN_USING_OTHER_HANDLER
        eng "Using storage engine %s for table '%s'"
        ger "Für Tabelle '%s' wird Speicher-Engine %s benutzt"
        jpn "ストレージエンジン %s が表 '%s' に利用されています。"
        por "Usando engine de armazenamento %s para tabela '%s'"
        spa "Usando motor de almacenamiento %s para tabla '%s'"
        swe "Använder handler %s för tabell '%s'"
ER_CANT_AGGREGATE_2COLLATIONS
        eng "Illegal mix of collations (%s,%s) and (%s,%s) for operation '%s'"
        ger "Unerlaubte Mischung von Sortierreihenfolgen (%s, %s) und (%s, %s) für Operation '%s'"
        jpn "照合順序 (%s,%s) と (%s,%s) の混在は操作 '%s' では不正です。"
        por "Combinação ilegal de collations (%s,%s) e (%s,%s) para operação '%s'"
        spa "Ilegal mezcla de collations (%s,%s) y (%s,%s) para operación '%s'"
OBSOLETE_ER_DROP_USER
        eng "Cannot drop one or more of the requested users"
        ger "Kann einen oder mehrere der angegebenen Benutzer nicht löschen"
ER_REVOKE_GRANTS
        eng "Can't revoke all privileges for one or more of the requested users"
        ger "Kann nicht alle Berechtigungen widerrufen, die für einen oder mehrere Benutzer gewährt wurden"
        jpn "指定されたユーザーから指定された全ての権限を剥奪することができませんでした。"
        por "Não pode revocar todos os privilégios, grant para um ou mais dos usuários pedidos"
        spa "No puede revocar todos los privilegios, derecho para uno o mas de los usuarios solicitados"
ER_CANT_AGGREGATE_3COLLATIONS
        eng "Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for operation '%s'"
        ger "Unerlaubte Mischung von Sortierreihenfolgen (%s, %s), (%s, %s), (%s, %s) für Operation '%s'"
        jpn "照合順序 (%s,%s), (%s,%s), (%s,%s) の混在は操作 '%s' では不正です。"
        por "Ilegal combinação de collations (%s,%s), (%s,%s), (%s,%s) para operação '%s'"
        spa "Ilegal mezcla de collations (%s,%s), (%s,%s), (%s,%s) para operación '%s'"
ER_CANT_AGGREGATE_NCOLLATIONS
        eng "Illegal mix of collations for operation '%s'"
        ger "Unerlaubte Mischung von Sortierreihenfolgen für Operation '%s'"
        jpn "操作 '%s' では不正な照合順序の混在です。"
        por "Ilegal combinação de collations para operação '%s'"
        spa "Ilegal mezcla de collations para operación '%s'"
ER_VARIABLE_IS_NOT_STRUCT
        eng "Variable '%-.64s' is not a variable component (can't be used as XXXX.variable_name)"
        ger "Variable '%-.64s' ist keine Variablen-Komponente (kann nicht als XXXX.variablen_name verwendet werden)"
        jpn "変数 '%-.64s' は構造変数の構成要素ではありません。(XXXX.変数名 という指定はできません。)"
        por "Variável '%-.64s' não é uma variável componente (Não pode ser usada como XXXX.variável_nome)"
        spa "Variable '%-.64s' no es una variable componente (No puede ser usada como XXXX.variable_name)"
ER_UNKNOWN_COLLATION
        eng "Unknown collation: '%-.64s'"
        ger "Unbekannte Sortierreihenfolge: '%-.64s'"
        jpn "不明な照合順序: '%-.64s'"
        por "Collation desconhecida: '%-.64s'"
        spa "Collation desconocida: '%-.64s'"
ER_REPLICA_IGNORED_SSL_PARAMS
        eng "SSL parameters in CHANGE REPLICATION SOURCE are ignored because this MySQL replica was compiled without SSL support; they can be used later if MySQL replica with SSL is started"
        ger "SSL-Parameter in CHANGE MASTER werden ignoriert, weil dieser MySQL-Slave ohne SSL-Unterstützung kompiliert wurde. Sie können aber später verwendet werden, wenn ein MySQL-Slave mit SSL gestartet wird"
        jpn "このMySQLスレーブはSSLサポートを含めてコンパイルされていないので、CHANGE MASTER のSSLパラメータは無視されました。今後SSLサポートを持つMySQLスレーブを起動する際に利用されます。"
        por "SSL parâmetros em CHANGE MASTER são ignorados porque este escravo MySQL foi compilado sem o SSL suporte. Os mesmos podem ser usados mais tarde quando o escravo MySQL com SSL seja iniciado."
        spa "Parametros SSL en CHANGE MASTER son ignorados porque este slave MySQL fue compilado sin soporte SSL; pueden ser usados despues cuando el slave MySQL con SSL sea inicializado"
OBSOLETE_ER_SERVER_IS_IN_SECURE_AUTH_MODE
        eng "Server is running in --secure-auth mode, but '%s'@'%s' has a password in the old format; please change the password to the new format"
        ger "Server läuft im Modus --secure-auth, aber '%s'@'%s' hat ein Passwort im alten Format. Bitte Passwort ins neue Format ändern"
        jpn "サーバーは --secure-auth モードで稼働しています。しかし '%s'@'%s' は古い形式のパスワードを使用しています。新しい形式のパスワードに変更してください。"
        por "Servidor está rodando em --secure-auth modo, porêm '%s'@'%s' tem senha no formato antigo; por favor troque a senha para o novo formato"
        rus "Сервер запущен в режиме --secure-auth (безопасной авторизации), но для пользователя '%s'@'%s' пароль сохранён в старом формате; необходимо обновить формат пароля"
        spa "Servidor está rodando en modo --secure-auth, pero '%s'@'%s' tiene clave en el antiguo formato; por favor cambie la clave para el nuevo formato"
ER_WARN_FIELD_RESOLVED
        eng "Field or reference '%-.192s%s%-.192s%s%-.192s' of SELECT #%d was resolved in SELECT #%d"
        ger "Feld oder Verweis '%-.192s%s%-.192s%s%-.192s' im SELECT-Befehl Nr. %d wurde im SELECT-Befehl Nr. %d aufgelöst"
        jpn "フィールドまたは参照 '%-.192s%s%-.192s%s%-.192s' は SELECT #%d ではなく、SELECT #%d で解決されました。"
        por "Campo ou referência '%-.192s%s%-.192s%s%-.192s' de SELECT #%d foi resolvido em SELECT #%d"
        rus "Поле или ссылка '%-.192s%s%-.192s%s%-.192s' из SELECTа #%d была найдена в SELECTе #%d"
        spa "Campo o referencia '%-.192s%s%-.192s%s%-.192s' de SELECT #%d fue resolvido en SELECT #%d"
        ukr "Стовбець або посилання '%-.192s%s%-.192s%s%-.192s' із SELECTу #%d було знайдене у SELECTі #%d"
ER_BAD_REPLICA_UNTIL_COND
        eng "Incorrect parameter or combination of parameters for START REPLICA UNTIL"
        ger "Falscher Parameter oder falsche Kombination von Parametern für START SLAVE UNTIL"
        jpn "START SLAVE UNTIL へのパラメータまたはその組み合わせが不正です。"
        por "Parâmetro ou combinação de parâmetros errado para START SLAVE UNTIL"
        spa "Parametro equivocado o combinación de parametros para START SLAVE UNTIL"
ER_MISSING_SKIP_REPLICA
        eng "It is recommended to use --skip-replica-start when doing step-by-step replication with START REPLICA UNTIL; otherwise, you will get problems if you get an unexpected replica's mysqld restart"
        ger "Es wird empfohlen, mit --skip-replica-start zu starten, wenn mit START SLAVE UNTIL eine Schritt-für-Schritt-Replikation ausgeführt wird. Ansonsten gibt es Probleme, wenn ein Slave-Server unerwartet neu startet"
        jpn "START SLAVE UNTIL で段階的にレプリケーションを行う際には、--skip-replica-start オプションを使うことを推奨します。使わない場合、スレーブのmysqldが不慮の再起動をすると問題が発生します。"
        por "É recomendado para rodar com --skip-replica-start quando fazendo replicação passo-por-passo com START SLAVE UNTIL, de outra forma você não está seguro em caso de inesperada reinicialição do mysqld escravo"
        spa "Es recomendado rodar con --skip-replica-start cuando haciendo replicación step-by-step con START SLAVE UNTIL, a menos que usted no esté seguro en caso de inesperada reinicialización del mysqld slave"
ER_UNTIL_COND_IGNORED
        eng "SQL thread is not to be started so UNTIL options are ignored"
        ger "SQL-Thread soll nicht gestartet werden. Daher werden UNTIL-Optionen ignoriert"
        jpn "スレーブSQLスレッドが開始されないため、UNTILオプションは無視されました。"
        por "Thread SQL não pode ser inicializado tal que opções UNTIL são ignoradas"
        spa "SQL thread no es inicializado tal que opciones UNTIL son ignoradas"
ER_WRONG_NAME_FOR_INDEX 42000
        eng "Incorrect index name '%-.100s'"
        ger "Falscher Indexname '%-.100s'"
        jpn "索引名 '%-.100s' は不正です。"
        por "Incorreto nome de índice '%-.100s'"
        spa "Nombre de índice incorrecto '%-.100s'"
        swe "Felaktigt index namn '%-.100s'"
ER_WRONG_NAME_FOR_CATALOG 42000
        eng "Incorrect catalog name '%-.100s'"
        ger "Falscher Katalogname '%-.100s'"
        jpn "カタログ名 '%-.100s' は不正です。"
        por "Incorreto nome de catálogo '%-.100s'"
        spa "Nombre de catalog incorrecto '%-.100s'"
        swe "Felaktigt katalog namn '%-.100s'"
OBSOLETE_ER_WARN_QC_RESIZE
        eng "Query cache failed to set size %lu; new query cache size is %lu"
        ger "Änderung der Query-Cache-Größe auf %lu fehlgeschlagen; neue Query-Cache-Größe ist %lu"
        jpn "クエリキャッシュのサイズを %lu にできませんでした。サイズは %lu になりました。"
        por "Falha em Query cache para configurar tamanho %lu, novo tamanho de query cache é %lu"
        rus "Кеш запросов не может установить размер %lu, новый размер кеша зпросов - %lu"
        spa "Query cache fallada para configurar tamaño %lu, nuevo tamaño de query cache es %lu"
        swe "Storleken av 'Query cache' kunde inte sättas till %lu, ny storlek är %lu"
        ukr "Кеш запитів неспроможен встановити розмір %lu, новий розмір кеша запитів - %lu"
ER_BAD_FT_COLUMN
        eng "Column '%-.192s' cannot be part of FULLTEXT index"
        ger "Feld '%-.192s' kann nicht Teil eines FULLTEXT-Index sein"
        jpn "列 '%-.192s' は全文索引のキーにはできません。"
        por "Coluna '%-.192s' não pode ser parte de índice FULLTEXT"
        spa "Columna '%-.192s' no puede ser parte de FULLTEXT index"
        swe "Kolumn '%-.192s' kan inte vara del av ett FULLTEXT index"
ER_UNKNOWN_KEY_CACHE
        eng "Unknown key cache '%-.100s'"
        ger "Unbekannter Schlüssel-Cache '%-.100s'"
        jpn "'%-.100s' は不明なキーキャッシュです。"
        por "Key cache desconhecida '%-.100s'"
        spa "Desconocida key cache '%-.100s'"
        swe "Okänd nyckel cache '%-.100s'"
ER_WARN_HOSTNAME_WONT_WORK
        eng "MySQL is started in --skip-name-resolve mode; you must restart it without this switch for this grant to work"
        ger "MySQL wurde mit --skip-name-resolve gestartet. Diese Option darf nicht verwendet werden, damit diese Rechtevergabe möglich ist"
        jpn "MySQLは --skip-name-resolve モードで起動しています。このオプションを外して再起動しなければ、この権限操作は機能しません。"
        por "MySQL foi inicializado em modo --skip-name-resolve. Você necesita reincializá-lo sem esta opção para este grant funcionar"
        spa "MySQL esta inicializado en modo --skip-name-resolve. Usted necesita reinicializarlo sin esta opción para este derecho funcionar"
ER_UNKNOWN_STORAGE_ENGINE 42000
        eng "Unknown storage engine '%s'"
        ger "Unbekannte Speicher-Engine '%s'"
        jpn "'%s' は不明なストレージエンジンです。"
        por "Motor de tabela desconhecido '%s'"
        spa "Desconocido motor de tabla '%s'"
ER_WARN_DEPRECATED_SYNTAX
        eng "'%s' is deprecated and will be removed in a future release. Please use %s instead"
        ger "'%s' ist veraltet. Bitte benutzen Sie '%s'"
        jpn "'%s' は将来のリリースで廃止予定です。代わりに %s を使用してください。"
        por "'%s' é desatualizado. Use '%s' em seu lugar"
        spa "'%s' está desaprobado, use '%s' en su lugar"
ER_NON_UPDATABLE_TABLE
        eng "The target table %-.100s of the %s is not updatable"
        ger "Die Zieltabelle %-.100s von %s ist nicht aktualisierbar"
        jpn "対象表 %-.100s は更新可能ではないので、%s を行えません。"
        por "A tabela destino %-.100s do %s não é atualizável"
        rus "Таблица %-.100s в %s не может изменятся"
        spa "La tabla destino %-.100s del %s no es actualizable"
        swe "Tabell %-.100s använd med '%s' är inte uppdateringsbar"
        ukr "Таблиця %-.100s у %s не може оновлюватись"
ER_FEATURE_DISABLED
        eng "The '%s' feature is disabled; you need MySQL built with '%s' to have it working"
        ger "Das Feature '%s' ist ausgeschaltet, Sie müssen MySQL mit '%s' übersetzen, damit es verfügbar ist"
        jpn "機能 '%s' は無効です。利用するためには '%s' を含めてビルドしたMySQLが必要です。"
        por "O recurso '%s' foi desativado; você necessita MySQL construído com '%s' para ter isto funcionando"
        spa "El recurso '%s' fue deshabilitado; usted necesita construir MySQL con '%s' para tener eso funcionando"
        swe "'%s' är inte aktiverad; För att aktivera detta måste du bygga om MySQL med '%s' definierad"
ER_OPTION_PREVENTS_STATEMENT
        eng "The MySQL server is running with the %s option so it cannot execute this statement"
        ger "Der MySQL-Server läuft mit der Option %s und kann diese Anweisung deswegen nicht ausführen"
        jpn "MySQLサーバーが %s オプションで実行されているので、このステートメントは実行できません。"
        por "O servidor MySQL está rodando com a opção %s razão pela qual não pode executar esse commando"
        spa "El servidor MySQL está rodando con la opción %s tal que no puede ejecutar este comando"
        swe "MySQL är startad med %s. Pga av detta kan du inte använda detta kommando"
ER_DUPLICATED_VALUE_IN_TYPE
        eng "Column '%-.100s' has duplicated value '%-.64s' in %s"
        ger "Feld '%-.100s' hat doppelten Wert '%-.64s' in %s"
        jpn "列 '%-.100s' で、重複する値 '%-.64s' が %s に指定されています。"
        por "Coluna '%-.100s' tem valor duplicado '%-.64s' em %s"
        spa "Columna '%-.100s' tiene valor doblado '%-.64s' en %s"
ER_TRUNCATED_WRONG_VALUE 22007
        eng "Truncated incorrect %-.64s value: '%-.128s'"
        ger "Falscher %-.64s-Wert gekürzt: '%-.128s'"
        jpn "不正な %-.64s の値が切り捨てられました。: '%-.128s'"
        por "Truncado errado %-.64s valor: '%-.128s'"
        spa "Equivocado truncado %-.64s valor: '%-.128s'"
OBSOLETE_ER_TOO_MUCH_AUTO_TIMESTAMP_COLS
        eng "Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause"
        ger "Fehlerhafte Tabellendefinition. Es kann nur eine einzige TIMESTAMP-Spalte mit CURRENT_TIMESTAMP als DEFAULT oder in einer ON-UPDATE-Klausel geben"
        jpn "不正な表定義です。DEFAULT句またはON UPDATE句に CURRENT_TIMESTAMP をともなうTIMESTAMP型の列は1つまでです。"
        por "Incorreta definição de tabela; Pode ter somente uma coluna TIMESTAMP com CURRENT_TIMESTAMP em DEFAULT ou ON UPDATE cláusula"
        spa "Incorrecta definición de tabla; Solamente debe haber una columna TIMESTAMP con CURRENT_TIMESTAMP en DEFAULT o ON UPDATE cláusula"
ER_INVALID_ON_UPDATE
        eng "Invalid ON UPDATE clause for '%-.192s' column"
        ger "Ungültige ON-UPDATE-Klausel für Spalte '%-.192s'"
        jpn "列 '%-.192s' に ON UPDATE句は無効です。"
        por "Inválida cláusula ON UPDATE para campo '%-.192s'"
        spa "Inválido ON UPDATE cláusula para campo '%-.192s'"
ER_UNSUPPORTED_PS
        eng "This command is not supported in the prepared statement protocol yet"
        ger "Dieser Befehl wird im Protokoll für vorbereitete Anweisungen noch nicht unterstützt"
ER_GET_ERRMSG
        dan "Modtog fejl %d '%-.100s' fra %s"
        eng "Got error %d '%-.100s' from %s"
        ger "Fehler %d '%-.100s' von %s"
        jpn "エラー %d '%-.100s' が %s から返されました。"
        nor "Mottok feil %d '%-.100s' fa %s"
        norwegian-ny "Mottok feil %d '%-.100s' fra %s"
ER_GET_TEMPORARY_ERRMSG
        dan "Modtog temporary fejl %d '%-.100s' fra %s"
        eng "Got temporary error %d '%-.100s' from %s"
        jpn "一時エラー %d '%-.100s' が %s から返されました。"
        ger "Temporärer Fehler %d '%-.100s' von %s"
        nor "Mottok temporary feil %d '%-.100s' fra %s"
        norwegian-ny "Mottok temporary feil %d '%-.100s' fra %s"
ER_UNKNOWN_TIME_ZONE
        eng "Unknown or incorrect time zone: '%-.64s'"
        ger "Unbekannte oder falsche Zeitzone: '%-.64s'"
ER_WARN_INVALID_TIMESTAMP
        eng "Invalid TIMESTAMP value in column '%s' at row %ld"
        ger "Ungültiger TIMESTAMP-Wert in Feld '%s', Zeile %ld"
ER_INVALID_CHARACTER_STRING
        eng "Invalid %s character string: '%.64s'"
        ger "Ungültiger %s-Zeichen-String: '%.64s'"
ER_WARN_ALLOWED_PACKET_OVERFLOWED
        eng "Result of %s() was larger than max_allowed_packet (%ld) - truncated"
        ger "Ergebnis von %s() war größer als max_allowed_packet (%ld) Bytes und wurde deshalb gekürzt"
ER_CONFLICTING_DECLARATIONS
        eng "Conflicting declarations: '%s%s' and '%s%s'"
        ger "Widersprüchliche Deklarationen: '%s%s' und '%s%s'"
ER_SP_NO_RECURSIVE_CREATE 2F003
        eng "Can't create a %s from within another stored routine"
        ger "Kann kein %s innerhalb einer anderen gespeicherten Routine erzeugen"
ER_SP_ALREADY_EXISTS 42000
        eng "%s %s already exists"
        ger "%s %s existiert bereits"
ER_SP_DOES_NOT_EXIST 42000
        eng "%s %s does not exist"
        ger "%s %s existiert nicht"
ER_SP_DROP_FAILED
        eng "Failed to DROP %s %s"
        ger "DROP %s %s ist fehlgeschlagen"
ER_SP_STORE_FAILED
        eng "Failed to CREATE %s %s"
        ger "CREATE %s %s ist fehlgeschlagen"
ER_SP_LILABEL_MISMATCH 42000
        eng "%s with no matching label: %s"
        ger "%s ohne passende Marke: %s"
ER_SP_LABEL_REDEFINE 42000
        eng "Redefining label %s"
        ger "Neudefinition der Marke %s"
ER_SP_LABEL_MISMATCH 42000
        eng "End-label %s without match"
        ger "Ende-Marke %s ohne zugehörigen Anfang"
ER_SP_UNINIT_VAR 01000
        eng "Referring to uninitialized variable %s"
        ger "Zugriff auf nichtinitialisierte Variable %s"
ER_SP_BADSELECT 0A000
        eng "PROCEDURE %s can't return a result set in the given context"
        ger "PROCEDURE %s kann im gegebenen Kontext keine Ergebnismenge zurückgeben"
ER_SP_BADRETURN 42000
        eng "RETURN is only allowed in a FUNCTION"
        ger "RETURN ist nur innerhalb einer FUNCTION erlaubt"
ER_SP_BADSTATEMENT 0A000
        eng "%s is not allowed in stored procedures"
        ger "%s ist in gespeicherten Prozeduren nicht erlaubt"
ER_UPDATE_LOG_DEPRECATED_IGNORED 42000
        eng "The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been ignored."
        ger "Das Update-Log ist veraltet und wurde durch das Binär-Log ersetzt. SET SQL_LOG_UPDATE wird ignoriert."
ER_UPDATE_LOG_DEPRECATED_TRANSLATED 42000
        eng "The update log is deprecated and replaced by the binary log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN."
        ger "Das Update-Log ist veraltet und wurde durch das Binär-Log ersetzt. SET SQL_LOG_UPDATE wurde in SET SQL_LOG_BIN übersetzt."
ER_QUERY_INTERRUPTED 70100
        eng "Query execution was interrupted"
        ger "Ausführung der Abfrage wurde unterbrochen"
ER_SP_WRONG_NO_OF_ARGS 42000
        eng "Incorrect number of arguments for %s %s; expected %u, got %u"
        ger "Falsche Anzahl von Argumenten für %s %s; erwarte %u, erhalte %u"
ER_SP_COND_MISMATCH 42000
        eng "Undefined CONDITION: %s"
        ger "Undefinierte CONDITION: %s"
ER_SP_NORETURN 42000
        eng "No RETURN found in FUNCTION %s"
        ger "Kein RETURN in FUNCTION %s gefunden"
ER_SP_NORETURNEND 2F005
        eng "FUNCTION %s ended without RETURN"
        ger "FUNCTION %s endete ohne RETURN"
ER_SP_BAD_CURSOR_QUERY 42000
        eng "Cursor statement must be a SELECT"
        ger "Cursor-Anweisung muss ein SELECT sein"
ER_SP_BAD_CURSOR_SELECT 42000
        eng "Cursor SELECT must not have INTO"
        ger "Cursor-SELECT darf kein INTO haben"
ER_SP_CURSOR_MISMATCH 42000
        eng "Undefined CURSOR: %s"
        ger "Undefinierter CURSOR: %s"
ER_SP_CURSOR_ALREADY_OPEN 24000
        eng "Cursor is already open"
        ger "Cursor ist schon geöffnet"
ER_SP_CURSOR_NOT_OPEN 24000
        eng "Cursor is not open"
        ger "Cursor ist nicht geöffnet"
ER_SP_UNDECLARED_VAR 42000
        eng "Undeclared variable: %s"
        ger "Nicht deklarierte Variable: %s"
ER_SP_WRONG_NO_OF_FETCH_ARGS
        eng "Incorrect number of FETCH variables"
        ger "Falsche Anzahl von FETCH-Variablen"
ER_SP_FETCH_NO_DATA 02000
        eng "No data - zero rows fetched, selected, or processed"
        ger "Keine Daten - null Zeilen geholt (fetch), ausgewählt oder verarbeitet"
ER_SP_DUP_PARAM 42000
        eng "Duplicate parameter: %s"
        ger "Doppelter Parameter: %s"
ER_SP_DUP_VAR 42000
        eng "Duplicate variable: %s"
        ger "Doppelte Variable: %s"
ER_SP_DUP_COND 42000
        eng "Duplicate condition: %s"
        ger "Doppelte Bedingung: %s"
ER_SP_DUP_CURS 42000
        eng "Duplicate cursor: %s"
        ger "Doppelter Cursor: %s"
ER_SP_CANT_ALTER
        eng "Failed to ALTER %s %s"
        ger "ALTER %s %s fehlgeschlagen"
ER_SP_SUBSELECT_NYI 0A000
        eng "Subquery value not supported"
        ger "Subquery-Wert wird nicht unterstützt"
ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG 0A000
        eng "%s is not allowed in stored function or trigger"
        ger "%s ist in gespeicherten Funktionen und in Triggern nicht erlaubt"
ER_SP_VARCOND_AFTER_CURSHNDLR 42000
        eng "Variable or condition declaration after cursor or handler declaration"
        ger "Deklaration einer Variablen oder einer Bedingung nach der Deklaration eines Cursors oder eines Handlers"
ER_SP_CURSOR_AFTER_HANDLER 42000
        eng "Cursor declaration after handler declaration"
        ger "Deklaration eines Cursors nach der Deklaration eines Handlers"
ER_SP_CASE_NOT_FOUND 20000
        eng "Case not found for CASE statement"
        ger "Fall für CASE-Anweisung nicht gefunden"
ER_FPARSER_TOO_BIG_FILE
        eng "Configuration file '%-.192s' is too big"
        ger "Konfigurationsdatei '%-.192s' ist zu groß"
        rus "Слишком большой конфигурационный файл '%-.192s'"
        ukr "Занадто великий конфігураційний файл '%-.192s'"
ER_FPARSER_BAD_HEADER
        eng "Malformed file type header in file '%-.192s'"
        ger "Nicht wohlgeformter Dateityp-Header in Datei '%-.192s'"
        rus "Неверный заголовок типа файла '%-.192s'"
        ukr "Невірний заголовок типу у файлі '%-.192s'"
ER_FPARSER_EOF_IN_COMMENT
        eng "Unexpected end of file while parsing comment '%-.200s'"
        ger "Unerwartetes Dateiende beim Parsen des Kommentars '%-.200s'"
        rus "Неожиданный конец файла в коментарии '%-.200s'"
        ukr "Несподіванний кінець файлу у коментарі '%-.200s'"
ER_FPARSER_ERROR_IN_PARAMETER
        eng "Error while parsing parameter '%-.192s' (line: '%-.192s')"
        ger "Fehler beim Parsen des Parameters '%-.192s' (Zeile: '%-.192s')"
        rus "Ошибка при распознавании параметра '%-.192s' (строка: '%-.192s')"
        ukr "Помилка в роспізнаванні параметру '%-.192s' (рядок: '%-.192s')"
ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER
        eng "Unexpected end of file while skipping unknown parameter '%-.192s'"
        ger "Unerwartetes Dateiende beim Überspringen des unbekannten Parameters '%-.192s'"
        rus "Неожиданный конец файла при пропуске неизвестного параметра '%-.192s'"
        ukr "Несподіванний кінець файлу у спробі проминути невідомий параметр '%-.192s'"
ER_VIEW_NO_EXPLAIN
        eng "EXPLAIN/SHOW can not be issued; lacking privileges for underlying table"
        ger "EXPLAIN/SHOW kann nicht verlangt werden. Rechte für zugrunde liegende Tabelle fehlen"
        rus "EXPLAIN/SHOW не может быть выполненно; недостаточно прав на такблицы запроса"
        ukr "EXPLAIN/SHOW не може бути віконано; немає прав на тиблиці запиту"
OBSOLETE_ER_FRM_UNKNOWN_TYPE
        eng "File '%-.192s' has unknown type '%-.64s' in its header"
        ger "Datei '%-.192s' hat unbekannten Typ '%-.64s' im Header"
        rus "Файл '%-.192s' содержит неизвестный тип '%-.64s' в заголовке"
        ukr "Файл '%-.192s' має невідомий тип '%-.64s' у заголовку"
ER_WRONG_OBJECT
        eng "'%-.192s.%-.192s' is not %s"
        ger "'%-.192s.%-.192s' ist nicht %s"
        rus "'%-.192s.%-.192s' - не %s"
        ukr "'%-.192s.%-.192s' не є %s"
ER_NONUPDATEABLE_COLUMN
        eng "Column '%-.192s' is not updatable"
        ger "Feld '%-.192s' ist nicht aktualisierbar"
        rus "Столбец '%-.192s' не обновляемый"
        ukr "Стовбець '%-.192s' не може бути зминений"
# Unused since MySQL 8.0.0
OBSOLETE_ER_VIEW_SELECT_DERIVED_UNUSED
        eng "View's SELECT contains a subquery in the FROM clause"
        ger "SELECT der View enthält eine Subquery in der FROM-Klausel"
        rus "View SELECT содержит подзапрос в конструкции FROM"
        ukr "View SELECT має підзапит у конструкції FROM"
ER_VIEW_SELECT_CLAUSE
        eng "View's SELECT contains a '%s' clause"
        ger "SELECT der View enthält eine '%s'-Klausel"
        rus "View SELECT содержит конструкцию '%s'"
        ukr "View SELECT має конструкцію '%s'"
ER_VIEW_SELECT_VARIABLE
        eng "View's SELECT contains a variable or parameter"
        ger "SELECT der View enthält eine Variable oder einen Parameter"
        rus "View SELECT содержит переменную или параметр"
        ukr "View SELECT має зминну або параметер"
ER_VIEW_SELECT_TMPTABLE
        eng "View's SELECT refers to a temporary table '%-.192s'"
        ger "SELECT der View verweist auf eine temporäre Tabelle '%-.192s'"
        rus "View SELECT содержит ссылку на временную таблицу '%-.192s'"
        ukr "View SELECT використовує тимчасову таблицю '%-.192s'"
ER_VIEW_WRONG_LIST
        eng "In definition of view, derived table or common table expression, SELECT list and column names list have different column counts"
        ger "SELECT- und Feldliste der Views haben unterschiedliche Anzahlen von Spalten"
        rus "View SELECT и список полей view имеют разное количество столбцов"
        ukr "View SELECT і перелік стовбців view мають різну кількість сковбців"
ER_WARN_VIEW_MERGE
        eng "View merge algorithm can't be used here for now (assumed undefined algorithm)"
        ger "View-Merge-Algorithmus kann hier momentan nicht verwendet werden (undefinierter Algorithmus wird angenommen)"
        rus "Алгоритм слияния view не может быть использован сейчас (алгоритм будет неопеределенным)"
        ukr "Алгоритм зливання view не може бути використаний зараз (алгоритм буде невизначений)"
ER_WARN_VIEW_WITHOUT_KEY
        eng "View being updated does not have complete key of underlying table in it"
        ger "Die aktualisierte View enthält nicht den vollständigen Schlüssel der zugrunde liegenden Tabelle"
        rus "Обновляемый view не содержит ключа использованных(ой) в нем таблиц(ы)"
        ukr "View, що оновлюеться, не містить повного ключа таблиці(ь), що викорістана в ньюому"
ER_VIEW_INVALID
        eng "View '%-.192s.%-.192s' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them"
ER_SP_NO_DROP_SP
        eng "Can't drop or alter a %s from within another stored routine"
        ger "Kann eine %s nicht von innerhalb einer anderen gespeicherten Routine löschen oder ändern"
OBSOLETE_ER_SP_GOTO_IN_HNDLR
        eng "GOTO is not allowed in a stored procedure handler"
        ger "GOTO ist im Handler einer gespeicherten Prozedur nicht erlaubt"
ER_TRG_ALREADY_EXISTS
        eng "Trigger already exists"
        ger "Trigger existiert bereits"
ER_TRG_DOES_NOT_EXIST
        eng "Trigger does not exist"
        ger "Trigger existiert nicht"
ER_TRG_ON_VIEW_OR_TEMP_TABLE
        eng "Trigger's '%-.192s' is view or temporary table"
        ger "'%-.192s' des Triggers ist View oder temporäre Tabelle"
ER_TRG_CANT_CHANGE_ROW
        eng "Updating of %s row is not allowed in %strigger"
        ger "Aktualisieren einer %s-Zeile ist in einem %s-Trigger nicht erlaubt"
ER_TRG_NO_SUCH_ROW_IN_TRG
        eng "There is no %s row in %s trigger"
        ger "Es gibt keine %s-Zeile im %s-Trigger"
ER_NO_DEFAULT_FOR_FIELD
        eng "Field '%-.192s' doesn't have a default value"
        ger "Feld '%-.192s' hat keinen Vorgabewert"
ER_DIVISION_BY_ZERO 22012
        eng "Division by 0"
        ger "Division durch 0"
ER_TRUNCATED_WRONG_VALUE_FOR_FIELD
        eng "Incorrect %-.32s value: '%-.128s' for column '%.192s' at row %ld"
        ger "Falscher %-.32s-Wert: '%-.128s' für Feld '%.192s' in Zeile %ld"
ER_ILLEGAL_VALUE_FOR_TYPE 22007
        eng "Illegal %s '%-.192s' value found during parsing"
        ger "Nicht zulässiger %s-Wert '%-.192s' beim Parsen gefunden"
ER_VIEW_NONUPD_CHECK
        eng "CHECK OPTION on non-updatable view '%-.192s.%-.192s'"
        ger "CHECK OPTION auf nicht-aktualisierbarem View '%-.192s.%-.192s'"
        rus "CHECK OPTION для необновляемого VIEW '%-.192s.%-.192s'"
        ukr "CHECK OPTION для VIEW '%-.192s.%-.192s' що не може бути оновленним"
ER_VIEW_CHECK_FAILED
        eng "CHECK OPTION failed '%-.192s.%-.192s'"
        ger "CHECK OPTION fehlgeschlagen: '%-.192s.%-.192s'"
        rus "проверка CHECK OPTION для VIEW '%-.192s.%-.192s' провалилась"
        ukr "Перевірка CHECK OPTION для VIEW '%-.192s.%-.192s' не пройшла"
ER_PROCACCESS_DENIED_ERROR 42000
        eng "%-.16s command denied to user '%-.48s'@'%-.64s' for routine '%-.192s'"
        ger "Befehl %-.16s nicht zulässig für Benutzer '%-.48s'@'%-.64s' in Routine '%-.192s'"
ER_RELAY_LOG_FAIL
        eng "Failed purging old relay logs: %s"
        ger "Bereinigen alter Relais-Logs fehlgeschlagen: %s"
OBSOLETE_ER_PASSWD_LENGTH
        eng "Password hash should be a %d-digit hexadecimal number"
        ger "Passwort-Hash sollte eine Hexdaezimalzahl mit %d Stellen sein"
ER_UNKNOWN_TARGET_BINLOG
        eng "Target log not found in binlog index"
        ger "Ziel-Log im Binlog-Index nicht gefunden"
ER_IO_ERR_LOG_INDEX_READ
        eng "I/O error reading log index file"
        ger "Fehler beim Lesen der Log-Index-Datei"
ER_BINLOG_PURGE_PROHIBITED
        eng "Server configuration does not permit binlog purge"
        ger "Server-Konfiguration erlaubt keine Binlog-Bereinigung"
ER_FSEEK_FAIL
        eng "Failed on fseek()"
        ger "fseek() fehlgeschlagen"
ER_BINLOG_PURGE_FATAL_ERR
        eng "Fatal error during log purge"
        ger "Schwerwiegender Fehler bei der Log-Bereinigung"
ER_LOG_IN_USE
        eng "A purgeable log is in use, will not purge"
        ger "Ein zu bereinigendes Log wird gerade benutzt, daher keine Bereinigung"
ER_LOG_PURGE_UNKNOWN_ERR
        eng "Unknown error during log purge"
        ger "Unbekannter Fehler bei Log-Bereinigung"
ER_RELAY_LOG_INIT
        eng "Failed initializing relay log position: %s"
        ger "Initialisierung der Relais-Log-Position fehlgeschlagen: %s"
ER_NO_BINARY_LOGGING
        eng "You are not using binary logging"
        ger "Sie verwenden keine Binärlogs"
ER_RESERVED_SYNTAX
        eng "The '%-.64s' syntax is reserved for purposes internal to the MySQL server"
        ger "Die Schreibweise '%-.64s' ist für interne Zwecke des MySQL-Servers reserviert"
OBSOLETE_ER_WSAS_FAILED
        eng "WSAStartup Failed"
        ger "WSAStartup fehlgeschlagen"
OBSOLETE_ER_DIFF_GROUPS_PROC
        eng "Can't handle procedures with different groups yet"
        ger "Kann Prozeduren mit unterschiedlichen Gruppen noch nicht verarbeiten"
OBSOLETE_ER_NO_GROUP_FOR_PROC
        eng "Select must have a group with this procedure"
        ger "SELECT muss bei dieser Prozedur ein GROUP BY haben"
OBSOLETE_ER_ORDER_WITH_PROC
        eng "Can't use ORDER clause with this procedure"
        ger "Kann bei dieser Prozedur keine ORDER-BY-Klausel verwenden"
OBSOLETE_ER_LOGGING_PROHIBIT_CHANGING_OF
        eng "Binary logging and replication forbid changing the global server %s"
        ger "Binärlogs und Replikation verhindern Wechsel des globalen Servers %s"
OBSOLETE_ER_NO_FILE_MAPPING
        eng "Can't map file: %-.200s, errno: %d"
        ger "Kann Datei nicht abbilden: %-.200s, Fehler: %d"
OBSOLETE_ER_WRONG_MAGIC
        eng "Wrong magic in %-.64s"
        ger "Falsche magische Zahlen in %-.64s"
ER_PS_MANY_PARAM
        eng "Prepared statement contains too many placeholders"
        ger "Vorbereitete Anweisung enthält zu viele Platzhalter"
ER_KEY_PART_0
        eng "Key part '%-.192s' length cannot be 0"
        ger "Länge des Schlüsselteils '%-.192s' kann nicht 0 sein"
ER_VIEW_CHECKSUM
        eng "View text checksum failed"
        ger "View-Text-Prüfsumme fehlgeschlagen"
        rus "Проверка контрольной суммы текста VIEW провалилась"
        ukr "Перевірка контрольної суми тексту VIEW не пройшла"
ER_VIEW_MULTIUPDATE
        eng "Can not modify more than one base table through a join view '%-.192s.%-.192s'"
        ger "Kann nicht mehr als eine Basistabelle über Join-View '%-.192s.%-.192s' ändern"
        rus "Нельзя изменить больше чем одну базовую таблицу используя многотабличный VIEW '%-.192s.%-.192s'"
        ukr "Неможливо оновити більш ниж одну базову таблицю выкористовуючи VIEW '%-.192s.%-.192s', що містіть декілька таблиць"
ER_VIEW_NO_INSERT_FIELD_LIST
        eng "Can not insert into join view '%-.192s.%-.192s' without fields list"
        ger "Kann nicht ohne Feldliste in Join-View '%-.192s.%-.192s' einfügen"
        rus "Нельзя вставлять записи в многотабличный VIEW '%-.192s.%-.192s' без списка полей"
        ukr "Неможливо уставити рядки у VIEW '%-.192s.%-.192s', що містить декілька таблиць, без списку стовбців"
ER_VIEW_DELETE_MERGE_VIEW
        eng "Can not delete from join view '%-.192s.%-.192s'"
        ger "Kann nicht aus Join-View '%-.192s.%-.192s' löschen"
        rus "Нельзя удалять из многотабличного VIEW '%-.192s.%-.192s'"
        ukr "Неможливо видалити рядки у VIEW '%-.192s.%-.192s', що містить декілька таблиць"
ER_CANNOT_USER
        eng "Operation %s failed for %.256s"
        ger "Operation %s schlug fehl für %.256s"
        norwegian-ny "Operation %s failed for '%.256s'"
ER_XAER_NOTA XAE04
        eng "XAER_NOTA: Unknown XID"
        ger "XAER_NOTA: Unbekannte XID"
ER_XAER_INVAL XAE05
        eng "XAER_INVAL: Invalid arguments (or unsupported command)"
        ger "XAER_INVAL: Ungültige Argumente (oder nicht unterstützter Befehl)"
ER_XAER_RMFAIL XAE07
        eng "XAER_RMFAIL: The command cannot be executed when global transaction is in the  %.64s state"
        ger "XAER_RMFAIL: DEr Befehl kann nicht ausgeführt werden, wenn die globale Transaktion im Zustand %.64s ist"
        rus "XAER_RMFAIL: эту команду нельзя выполнять когда глобальная транзакция находится в состоянии '%.64s'"
ER_XAER_OUTSIDE XAE09
        eng "XAER_OUTSIDE: Some work is done outside global transaction"
        ger "XAER_OUTSIDE: Einige Arbeiten werden außerhalb der globalen Transaktion verrichtet"
ER_XAER_RMERR XAE03
        eng "XAER_RMERR: Fatal error occurred in the transaction branch - check your data for consistency"
        ger "XAER_RMERR: Schwerwiegender Fehler im Transaktionszweig - prüfen Sie Ihre Daten auf Konsistenz"
ER_XA_RBROLLBACK XA100
        eng "XA_RBROLLBACK: Transaction branch was rolled back"
        ger "XA_RBROLLBACK: Transaktionszweig wurde zurückgerollt"
ER_NONEXISTING_PROC_GRANT 42000
        eng "There is no such grant defined for user '%-.48s' on host '%-.255s' on routine '%-.192s'"
        ger "Es gibt diese Berechtigung für Benutzer '%-.48s' auf Host '%-.255s' für Routine '%-.192s' nicht"
ER_PROC_AUTO_GRANT_FAIL
        eng "Failed to grant EXECUTE and ALTER ROUTINE privileges"
        ger "Gewährung von EXECUTE- und ALTER-ROUTINE-Rechten fehlgeschlagen"
ER_PROC_AUTO_REVOKE_FAIL
        eng "Failed to revoke all privileges to dropped routine"
        ger "Rücknahme aller Rechte für die gelöschte Routine fehlgeschlagen"
ER_DATA_TOO_LONG 22001
        eng "Data too long for column '%s' at row %ld"
        ger "Daten zu lang für Feld '%s' in Zeile %ld"
ER_SP_BAD_SQLSTATE 42000
        eng "Bad SQLSTATE: '%s'"
        ger "Ungültiger SQLSTATE: '%s'"
ER_STARTUP
        eng "%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s"
        ger "%s: bereit für Verbindungen. Version: '%s'  Socket: '%s'  Port: %d  %s"
ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR
        eng "Can't load value from file with fixed size rows to variable"
        ger "Kann Wert aus Datei mit Zeilen fester Größe nicht in Variable laden"
ER_CANT_CREATE_USER_WITH_GRANT 42000
        eng "You are not allowed to create a user with GRANT"
        ger "Sie dürfen keinen Benutzer mit GRANT anlegen"
ER_WRONG_VALUE_FOR_TYPE
        eng "Incorrect %-.32s value: '%-.128s' for function %-.32s"
        ger "Falscher %-.32s-Wert: '%-.128s' für Funktion %-.32s"
ER_TABLE_DEF_CHANGED
        eng "Table definition has changed, please retry transaction"
        ger "Tabellendefinition wurde geändert, bitte starten Sie die Transaktion neu"
ER_SP_DUP_HANDLER 42000
        eng "Duplicate handler declared in the same block"
        ger "Doppelter Handler im selben Block deklariert"
ER_SP_NOT_VAR_ARG 42000
        eng "OUT or INOUT argument %d for routine %s is not a variable or NEW pseudo-variable in BEFORE trigger"
        ger "OUT- oder INOUT-Argument %d für Routine %s ist keine Variable"
ER_SP_NO_RETSET 0A000
        eng "Not allowed to return a result set from a %s"
        ger "Rückgabe einer Ergebnismenge aus einer %s ist nicht erlaubt"
ER_CANT_CREATE_GEOMETRY_OBJECT 22003
        eng "Cannot get geometry object from data you send to the GEOMETRY field"
        ger "Kann kein Geometrieobjekt aus den Daten machen, die Sie dem GEOMETRY-Feld übergeben haben"
OBSOLETE_ER_FAILED_ROUTINE_BREAK_BINLOG
        eng "A routine failed and has neither NO SQL nor READS SQL DATA in its declaration and binary logging is enabled; if non-transactional tables were updated, the binary log will miss their changes"
        ger "Eine Routine, die weder NO SQL noch READS SQL DATA in der Deklaration hat, schlug fehl und Binärlogging ist aktiv. Wenn Nicht-Transaktions-Tabellen aktualisiert wurden, enthält das Binärlog ihre Änderungen nicht"
ER_BINLOG_UNSAFE_ROUTINE
        eng "This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)"
        ger "Diese Routine hat weder DETERMINISTIC, NO SQL noch READS SQL DATA in der Deklaration und Binärlogging ist aktiv (*vielleicht* sollten Sie die weniger sichere Variable log_bin_trust_function_creators verwenden)"
ER_BINLOG_CREATE_ROUTINE_NEED_SUPER
        eng "You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)"
        ger "Sie haben keine SUPER-Berechtigung und Binärlogging ist aktiv (*vielleicht* sollten Sie die weniger sichere Variable log_bin_trust_function_creators verwenden)"
OBSOLETE_ER_EXEC_STMT_WITH_OPEN_CURSOR
        eng "You can't execute a prepared statement which has an open cursor associated with it. Reset the statement to re-execute it."
        ger "Sie können keine vorbereitete Anweisung ausführen, die mit einem geöffneten Cursor verknüpft ist. Setzen Sie die Anweisung zurück, um sie neu auszuführen"
ER_STMT_HAS_NO_OPEN_CURSOR
        eng "The statement (%lu) has no open cursor."
        ger "Die Anweisung (%lu) hat keinen geöffneten Cursor"
ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG
        eng "Explicit or implicit commit is not allowed in stored function or trigger."
        ger "Explizites oder implizites Commit ist in gespeicherten Funktionen und in Triggern nicht erlaubt"
ER_NO_DEFAULT_FOR_VIEW_FIELD
        eng "Field of view '%-.192s.%-.192s' underlying table doesn't have a default value"
        ger "Ein Feld der dem View '%-.192s.%-.192s' zugrundeliegenden Tabelle hat keinen Vorgabewert"
ER_SP_NO_RECURSION
        eng "Recursive stored functions and triggers are not allowed."
        ger "Rekursive gespeicherte Routinen und Triggers sind nicht erlaubt"
ER_TOO_BIG_SCALE 42000 S1009
        eng "Too big scale %d specified for column '%-.192s'. Maximum is %lu."
        ger "Zu großer Skalierungsfaktor %d für Feld '%-.192s' angegeben. Maximum ist %lu"
ER_TOO_BIG_PRECISION 42000 S1009
        eng "Too-big precision %d specified for '%-.192s'. Maximum is %lu."
        ger "Zu große Genauigkeit %d für Feld '%-.192s' angegeben. Maximum ist %lu"
ER_M_BIGGER_THAN_D 42000 S1009
        eng "For float(M,D), double(M,D) or decimal(M,D), M must be >= D (column '%-.192s')."
        ger "Für FLOAT(M,D), DOUBLE(M,D) oder DECIMAL(M,D) muss M >= D sein (Feld '%-.192s')"
ER_WRONG_LOCK_OF_SYSTEM_TABLE
        eng "You can't combine write-locking of system tables with other tables or lock types"
	ger "Sie können Schreibsperren auf der Systemtabelle nicht mit anderen Tabellen kombinieren"
ER_CONNECT_TO_FOREIGN_DATA_SOURCE
        eng "Unable to connect to foreign data source: %.64s"
        ger "Kann nicht mit Fremddatenquelle verbinden: %.64s"
ER_QUERY_ON_FOREIGN_DATA_SOURCE
        eng "There was a problem processing the query on the foreign data source. Data source error: %-.64s"
        ger "Bei der Verarbeitung der Abfrage ist in der Fremddatenquelle ein Problem aufgetreten. Datenquellenfehlermeldung: %-.64s"
ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST
        eng "The foreign data source you are trying to reference does not exist. Data source error:  %-.64s"
        ger "Die Fremddatenquelle, auf die Sie zugreifen wollen, existiert nicht. Datenquellenfehlermeldung:  %-.64s"
ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE
        eng "Can't create federated table. The data source connection string '%-.64s' is not in the correct format"
        ger "Kann föderierte Tabelle nicht erzeugen. Der Datenquellen-Verbindungsstring '%-.64s' hat kein korrektes Format"
ER_FOREIGN_DATA_STRING_INVALID
        eng "The data source connection string '%-.64s' is not in the correct format"
        ger "Der Datenquellen-Verbindungsstring '%-.64s' hat kein korrektes Format"
OBSOLETE_ER_CANT_CREATE_FEDERATED_TABLE
        eng "Can't create federated table. Foreign data src error:  %-.64s"
        ger "Kann föderierte Tabelle nicht erzeugen. Fremddatenquellenfehlermeldung:  %-.64s"
ER_TRG_IN_WRONG_SCHEMA
        eng "Trigger in wrong schema"
        ger "Trigger im falschen Schema"
ER_STACK_OVERRUN_NEED_MORE
        eng "Thread stack overrun:  %ld bytes used of a %ld byte stack, and %ld bytes needed.  Use 'mysqld --thread_stack=#' to specify a bigger stack."
        ger "Thread-Stack-Überlauf: %ld Bytes eines %ld-Byte-Stacks in Verwendung, und %ld Bytes benötigt. Verwenden Sie 'mysqld --thread_stack=#', um einen größeren Stack anzugeben"
        jpn "スレッドスタック不足です(使用: %ld ; サイズ: %ld ; 要求: %ld)。より大きい値で 'mysqld --thread_stack=#' の指定をしてください。"
ER_TOO_LONG_BODY 42000 S1009
        eng "Routine body for '%-.100s' is too long"
        ger "Routinen-Body für '%-.100s' ist zu lang"
ER_WARN_CANT_DROP_DEFAULT_KEYCACHE
        eng "Cannot drop default keycache"
        ger "Der vorgabemäßige Schlüssel-Cache kann nicht gelöscht werden"
ER_TOO_BIG_DISPLAYWIDTH 42000 S1009
        eng "Display width out of range for column '%-.192s' (max = %lu)"
        ger "Anzeigebreite außerhalb des zulässigen Bereichs für Spalte '%-.192s' (Maximum: %lu)"
ER_XAER_DUPID XAE08
        eng "XAER_DUPID: The XID already exists"
        ger "XAER_DUPID: Die XID existiert bereits"
ER_DATETIME_FUNCTION_OVERFLOW 22008
        eng "Datetime function: %-.32s field overflow"
        ger "Datetime-Funktion: %-.32s Feldüberlauf"
ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
        eng "Can't update table '%-.192s' in stored function/trigger because it is already used by statement which invoked this stored function/trigger."
        ger "Kann Tabelle '%-.192s' in gespeicherter Funktion oder Trigger nicht aktualisieren, weil sie bereits von der Anweisung verwendet wird, die diese gespeicherte Funktion oder den Trigger aufrief"
ER_VIEW_PREVENT_UPDATE
        eng "The definition of table '%-.192s' prevents operation %.192s on table '%-.192s'."
        ger "Die Definition der Tabelle '%-.192s' verhindert die Operation %.192s auf Tabelle '%-.192s'"
ER_PS_NO_RECURSION
        eng "The prepared statement contains a stored routine call that refers to that same statement. It's not allowed to execute a prepared statement in such a recursive manner"
        ger "Die vorbereitete Anweisung enthält einen Aufruf einer gespeicherten Routine, die auf eben dieselbe Anweisung verweist. Es ist nicht erlaubt, eine vorbereitete Anweisung in solch rekursiver Weise auszuführen"
ER_SP_CANT_SET_AUTOCOMMIT
        eng "Not allowed to set autocommit from a stored function or trigger"
        ger "Es ist nicht erlaubt, innerhalb einer gespeicherten Funktion oder eines Triggers AUTOCOMMIT zu setzen"
OBSOLETE_ER_MALFORMED_DEFINER
        eng "Definer is not fully qualified"
        ger "Definierer des View ist nicht vollständig spezifiziert"
ER_VIEW_FRM_NO_USER
        eng "View '%-.192s'.'%-.192s' has no definer information (old table format). Current user is used as definer. Please recreate the view!"
        ger "View '%-.192s'.'%-.192s' hat keine Definierer-Information (altes Tabellenformat). Der aktuelle Benutzer wird als Definierer verwendet. Bitte erstellen Sie den View neu"
ER_VIEW_OTHER_USER
        eng "You need the SUPER privilege for creation view with '%-.192s'@'%-.192s' definer"
        ger "Sie brauchen die SUPER-Berechtigung, um einen View mit dem Definierer '%-.192s'@'%-.192s' zu erzeugen"
ER_NO_SUCH_USER
  eng "The user specified as a definer ('%-.64s'@'%-.64s') does not exist"
  ger "Der als Definierer angegebene Benutzer ('%-.64s'@'%-.64s') existiert nicht"
ER_FORBID_SCHEMA_CHANGE
        eng "Changing schema from '%-.192s' to '%-.192s' is not allowed."
        ger "Wechsel des Schemas von '%-.192s' auf '%-.192s' ist nicht erlaubt"
ER_ROW_IS_REFERENCED_2 23000
        eng "Cannot delete or update a parent row: a foreign key constraint fails (%.192s)"
        ger "Kann Eltern-Zeile nicht löschen oder aktualisieren: eine Fremdschlüsselbedingung schlägt fehl (%.192s)"
ER_NO_REFERENCED_ROW_2 23000
        eng "Cannot add or update a child row: a foreign key constraint fails (%.192s)"
        ger "Kann Kind-Zeile nicht hinzufügen oder aktualisieren: eine Fremdschlüsselbedingung schlägt fehl (%.192s)"
ER_SP_BAD_VAR_SHADOW 42000
        eng "Variable '%-.64s' must be quoted with `...`, or renamed"
        ger "Variable '%-.64s' muss mit `...` geschützt oder aber umbenannt werden"
ER_TRG_NO_DEFINER
        eng "No definer attribute for trigger '%-.192s'.'%-.192s'. It's disallowed to create trigger without definer."
ER_OLD_FILE_FORMAT
        eng "'%-.192s' has an old format, you should re-create the '%s' object(s)"
        ger "'%-.192s' hat altes Format, Sie sollten die '%s'-Objekt(e) neu erzeugen"
ER_SP_RECURSION_LIMIT
        eng "Recursive limit %d (as set by the max_sp_recursion_depth variable) was exceeded for routine %.192s"
        ger "Rekursionsgrenze %d (durch Variable max_sp_recursion_depth gegeben) wurde für Routine %.192s überschritten"
OBSOLETE_ER_SP_PROC_TABLE_CORRUPT
        eng "Failed to load routine %-.192s. The data dictionary table missing, corrupt, or contains bad data (internal code %d)"
        ger "Routine %-.192s konnte nicht geladen werden. Die data dictionary Tabelle fehlt, ist beschädigt, oder enthält fehlerhaften Daten (interner Code: %d)"
ER_SP_WRONG_NAME 42000
        eng "Incorrect routine name '%-.192s'"
        ger "Ungültiger Routinenname '%-.192s'"
ER_TABLE_NEEDS_UPGRADE
        eng "Table upgrade required. Please do \"REPAIR TABLE `%-.64s`\" or dump/reload to fix it!"
        ger "Tabellenaktualisierung erforderlich. Bitte zum Reparieren \"REPAIR TABLE `%-.64s`\" eingeben!"
ER_SP_NO_AGGREGATE 42000
        eng "AGGREGATE is not supported for stored functions"
        ger "AGGREGATE wird bei gespeicherten Funktionen nicht unterstützt"
ER_MAX_PREPARED_STMT_COUNT_REACHED 42000
        eng "Can't create more than max_prepared_stmt_count statements (current value: %lu)"
        ger "Kann nicht mehr Anweisungen als max_prepared_stmt_count erzeugen (aktueller Wert: %lu)"
ER_VIEW_RECURSIVE
        eng "`%-.192s`.`%-.192s` contains view recursion"
        ger "`%-.192s`.`%-.192s` enthält View-Rekursion"

# the one below is not used anymore:
ER_NON_GROUPING_FIELD_USED 42000
        eng "Non-grouping field '%-.192s' is used in %-.64s clause"
        ger "In der %-.192s-Klausel wird das die Nicht-Gruppierungsspalte '%-.64s' verwendet"
ER_TABLE_CANT_HANDLE_SPKEYS
        eng "The used table type doesn't support SPATIAL indexes"
        ger "Der verwendete Tabellentyp unterstützt keine SPATIAL-Indizes"
ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA
        eng "Triggers can not be created on system tables"
        ger "Trigger können nicht auf Systemtabellen erzeugt werden"
ER_REMOVED_SPACES
        eng "Leading spaces are removed from name '%s'"
        ger "Führende Leerzeichen werden aus dem Namen '%s' entfernt"
ER_AUTOINC_READ_FAILED
        eng "Failed to read auto-increment value from storage engine"
        ger "Lesen des Autoincrement-Werts von der Speicher-Engine fehlgeschlagen"
ER_USERNAME
        eng "user name"
        ger "Benutzername"
ER_HOSTNAME
        eng "host name"
        ger "Hostname"
ER_WRONG_STRING_LENGTH
        eng "String '%-.70s' is too long for %s (should be no longer than %d)"
        ger "String '%-.70s' ist zu lang für %s (sollte nicht länger sein als %d)"
ER_NON_INSERTABLE_TABLE
        eng "The target table %-.100s of the %s is not insertable-into"
        ger "Die Zieltabelle %-.100s von %s ist nicht einfügbar"
        jpn "対象表 %-.100s は挿入可能ではないので、%s を行えません。"
ER_ADMIN_WRONG_MRG_TABLE
  eng "Table '%-.64s' is differently defined or of non-MyISAM type or doesn't exist"
  ger "Tabelle '%-.64s' ist unterschiedlich definiert, nicht vom Typ MyISAM oder existiert nicht"
ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT
  eng "Too high level of nesting for select"
  ger "Zu tief verschachtelte SELECT-Anweisungen"
ER_NAME_BECOMES_EMPTY
  eng "Name '%-.64s' has become ''"
  ger "Name '%-.64s' wurde zu ''"
ER_AMBIGUOUS_FIELD_TERM
  eng "First character of the FIELDS TERMINATED string is ambiguous; please use non-optional and non-empty FIELDS ENCLOSED BY"
  ger "Das erste Zeichen der Zeichenkette FIELDS TERMINATED ist mehrdeutig; bitte benutzen Sie nicht optionale und nicht leere FIELDS ENCLOSED BY"
ER_FOREIGN_SERVER_EXISTS
  eng "The foreign server, %s, you are trying to create already exists."
  ger "Der entfernte Server %s, den Sie versuchen zu erzeugen, existiert schon."
ER_FOREIGN_SERVER_DOESNT_EXIST
        eng "The foreign server name you are trying to reference does not exist. Data source error:  %-.64s"
	ger "Die externe Verbindung, auf die Sie zugreifen wollen, existiert nicht. Datenquellenfehlermeldung:  %-.64s"
ER_ILLEGAL_HA_CREATE_OPTION
        eng "Table storage engine '%-.64s' does not support the create option '%.64s'"
        ger "Speicher-Engine '%-.64s' der Tabelle unterstützt die Option '%.64s' nicht"
ER_PARTITION_REQUIRES_VALUES_ERROR
        eng "Syntax error: %-.64s PARTITIONING requires definition of VALUES %-.64s for each partition"
        ger "Fehler in der SQL-Syntax: %-.64s-PARTITIONierung erfordert Definition von VALUES %-.64s für jede Partition"
        swe "Syntaxfel: %-.64s PARTITIONering kräver definition av VALUES %-.64s för varje partition"
ER_PARTITION_WRONG_VALUES_ERROR
        eng "Only %-.64s PARTITIONING can use VALUES %-.64s in partition definition"
        ger "Nur %-.64s-PARTITIONierung kann VALUES %-.64s in der Partitionsdefinition verwenden"
        swe "Endast %-.64s partitionering kan använda VALUES %-.64s i definition av partitionen"
ER_PARTITION_MAXVALUE_ERROR
        eng "MAXVALUE can only be used in last partition definition"
        ger "MAXVALUE kann nur für die Definition der letzten Partition verwendet werden"
        swe "MAXVALUE kan bara användas i definitionen av den sista partitionen"
OBSOLETE_ER_PARTITION_SUBPARTITION_ERROR
        eng "Subpartitions can only be hash partitions and by key"
        ger "Unterpartitionen dürfen nur HASH- oder KEY-Partitionen sein"
        swe "Subpartitioner kan bara vara hash och key partitioner"
OBSOLETE_ER_PARTITION_SUBPART_MIX_ERROR
        eng "Must define subpartitions on all partitions if on one partition"
        ger "Wenn Sie Unterpartitionen auf einer Partition definieren, müssen Sie das für alle Partitionen tun"
        swe "Subpartitioner måste definieras på alla partitioner om på en"
ER_PARTITION_WRONG_NO_PART_ERROR
        eng "Wrong number of partitions defined, mismatch with previous setting"
        ger "Falsche Anzahl von Partitionen definiert, stimmt nicht mit vorherigen Einstellungen überein"
        swe "Antal partitioner definierade och antal partitioner är inte lika"
ER_PARTITION_WRONG_NO_SUBPART_ERROR
        eng "Wrong number of subpartitions defined, mismatch with previous setting"
        ger "Falsche Anzahl von Unterpartitionen definiert, stimmt nicht mit vorherigen Einstellungen überein"
        swe "Antal subpartitioner definierade och antal subpartitioner är inte lika"
ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR
        eng "Constant, random or timezone-dependent expressions in (sub)partitioning function are not allowed"
        ger "Konstante oder Random-Ausdrücke in (Unter-)Partitionsfunktionen sind nicht erlaubt"
        swe "Konstanta uttryck eller slumpmässiga uttryck är inte tillåtna (sub)partitioneringsfunktioner"
OBSOLETE_ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR
        eng "Expression in RANGE/LIST VALUES must be constant"
        ger "Ausdrücke in RANGE/LIST VALUES müssen konstant sein"
        swe "Uttryck i RANGE/LIST VALUES måste vara ett konstant uttryck"
ER_FIELD_NOT_FOUND_PART_ERROR
        eng "Field in list of fields for partition function not found in table"
        ger "Felder in der Feldliste der Partitionierungsfunktion wurden in der Tabelle nicht gefunden"
        swe "Fält i listan av fält för partitionering med key inte funnen i tabellen"
OBSOLETE_ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR
        eng "List of fields is only allowed in KEY partitions"
        ger "Eine Feldliste ist nur in KEY-Partitionen erlaubt"
        swe "En lista av fält är endast tillåtet för KEY partitioner"
ER_INCONSISTENT_PARTITION_INFO_ERROR
        eng "The partition info in the frm file is not consistent with what can be written into the frm file"
        ger "Die Partitionierungsinformationen in der frm-Datei stimmen nicht mit dem überein, was in die frm-Datei geschrieben werden kann"
        swe "Partitioneringsinformationen i frm-filen är inte konsistent med vad som kan skrivas i frm-filen"
ER_PARTITION_FUNC_NOT_ALLOWED_ERROR
        eng "The %-.192s function returns the wrong type"
        ger "Die %-.192s-Funktion gibt einen falschen Typ zurück"
        swe "%-.192s-funktionen returnerar felaktig typ"
ER_PARTITIONS_MUST_BE_DEFINED_ERROR
        eng "For %-.64s partitions each partition must be defined"
        ger "Für %-.64s-Partitionen muss jede Partition definiert sein"
        swe "För %-.64s partitionering så måste varje partition definieras"
ER_RANGE_NOT_INCREASING_ERROR
        eng "VALUES LESS THAN value must be strictly increasing for each partition"
        ger "Werte in VALUES LESS THAN müssen für jede Partition strikt aufsteigend sein"
        swe "Värden i VALUES LESS THAN måste vara strikt växande för varje partition"
ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR
        eng "VALUES value must be of same type as partition function"
        ger "VALUES-Werte müssen vom selben Typ wie die Partitionierungsfunktion sein"
        swe "Värden i VALUES måste vara av samma typ som partitioneringsfunktionen"
ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR
        eng "Multiple definition of same constant in list partitioning"
        ger "Mehrfachdefinition derselben Konstante bei Listen-Partitionierung"
        swe "Multipel definition av samma konstant i list partitionering"
ER_PARTITION_ENTRY_ERROR
        eng "Partitioning can not be used stand-alone in query"
        ger "Partitionierung kann in einer Abfrage nicht alleinstehend benutzt werden"
        swe "Partitioneringssyntax kan inte användas på egen hand i en SQL-fråga"
ER_MIX_HANDLER_ERROR
        eng "The mix of handlers in the partitions is not allowed in this version of MySQL"
        ger "Das Vermischen von Handlern in Partitionen ist in dieser Version von MySQL nicht erlaubt"
        swe "Denna mix av lagringsmotorer är inte tillåten i denna version av MySQL"
ER_PARTITION_NOT_DEFINED_ERROR
        eng "For the partitioned engine it is necessary to define all %-.64s"
        ger "Für die partitionierte Engine müssen alle %-.64s definiert sein"
        swe "För partitioneringsmotorn så är det nödvändigt att definiera alla %-.64s"
ER_TOO_MANY_PARTITIONS_ERROR
        eng "Too many partitions (including subpartitions) were defined"
        ger "Es wurden zu vielen Partitionen (einschließlich Unterpartitionen) definiert"
        swe "För många partitioner (inkluderande subpartitioner) definierades"
ER_SUBPARTITION_ERROR
        eng "It is only possible to mix RANGE/LIST partitioning with HASH/KEY partitioning for subpartitioning"
        ger "RANGE/LIST-Partitionierung kann bei Unterpartitionen nur zusammen mit HASH/KEY-Partitionierung verwendet werden"
        swe "Det är endast möjligt att blanda RANGE/LIST partitionering med HASH/KEY partitionering för subpartitionering"
ER_CANT_CREATE_HANDLER_FILE
        eng "Failed to create specific handler file"
        ger "Erzeugen einer spezifischen Handler-Datei fehlgeschlagen"
        swe "Misslyckades med att skapa specifik fil i lagringsmotor"
ER_BLOB_FIELD_IN_PART_FUNC_ERROR
        eng "A BLOB field is not allowed in partition function"
        ger "In der Partitionierungsfunktion sind BLOB-Spalten nicht erlaubt"
        swe "Ett BLOB-fält är inte tillåtet i partitioneringsfunktioner"
ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF
        eng "A %-.192s must include all columns in the table's partitioning function (prefixed columns are not considered)."
ER_NO_PARTS_ERROR
        eng "Number of %-.64s = 0 is not an allowed value"
        ger "Eine Anzahl von %-.64s = 0 ist kein erlaubter Wert"
        swe "Antal %-.64s = 0 är inte ett tillåten värde"
ER_PARTITION_MGMT_ON_NONPARTITIONED
        eng "Partition management on a not partitioned table is not possible"
        ger "Partitionsverwaltung einer nicht partitionierten Tabelle ist nicht möglich"
        swe "Partitioneringskommando på en opartitionerad tabell är inte möjligt"
ER_FOREIGN_KEY_ON_PARTITIONED
        eng "Foreign keys are not yet supported in conjunction with partitioning"
        ger "Fremdschlüssel-Beschränkungen sind im Zusammenhang mit Partitionierung nicht zulässig"
        swe "Foreign keys är inte ännu implementerad i kombination med partitionering"
ER_DROP_PARTITION_NON_EXISTENT
        eng "Error in list of partitions to %-.64s"
        ger "Fehler in der Partitionsliste bei %-.64s"
        swe "Fel i listan av partitioner att %-.64s"
ER_DROP_LAST_PARTITION
        eng "Cannot remove all partitions, use DROP TABLE instead"
        ger "Es lassen sich nicht sämtliche Partitionen löschen, benutzen Sie statt dessen DROP TABLE"
        swe "Det är inte tillåtet att ta bort alla partitioner, använd DROP TABLE istället"
ER_COALESCE_ONLY_ON_HASH_PARTITION
        eng "COALESCE PARTITION can only be used on HASH/KEY partitions"
        ger "COALESCE PARTITION kann nur auf HASH- oder KEY-Partitionen benutzt werden"
        swe "COALESCE PARTITION kan bara användas på HASH/KEY partitioner"
ER_REORG_HASH_ONLY_ON_SAME_NO
        eng "REORGANIZE PARTITION can only be used to reorganize partitions not to change their numbers"
        ger "REORGANIZE PARTITION kann nur zur Reorganisation von Partitionen verwendet werden, nicht, um ihre Nummern zu ändern"
        swe "REORGANIZE PARTITION kan bara användas för att omorganisera partitioner, inte för att ändra deras antal"
ER_REORG_NO_PARAM_ERROR
        eng "REORGANIZE PARTITION without parameters can only be used on auto-partitioned tables using HASH PARTITIONs"
        ger "REORGANIZE PARTITION ohne Parameter kann nur für auto-partitionierte Tabellen verwendet werden, die HASH-Partitionierung benutzen"
        swe "REORGANIZE PARTITION utan parametrar kan bara användas på auto-partitionerade tabeller som använder HASH partitionering"
ER_ONLY_ON_RANGE_LIST_PARTITION
        eng "%-.64s PARTITION can only be used on RANGE/LIST partitions"
        ger "%-.64s PARTITION kann nur für RANGE- oder LIST-Partitionen verwendet werden"
        swe "%-.64s PARTITION kan bara användas på RANGE/LIST-partitioner"
ER_ADD_PARTITION_SUBPART_ERROR
        eng "Trying to Add partition(s) with wrong number of subpartitions"
        ger "Es wurde versucht, eine oder mehrere Partitionen mit der falschen Anzahl von Unterpartitionen hinzuzufügen"
        swe "ADD PARTITION med fel antal subpartitioner"
ER_ADD_PARTITION_NO_NEW_PARTITION
        eng "At least one partition must be added"
        ger "Es muss zumindest eine Partition hinzugefügt werden"
        swe "Åtminstone en partition måste läggas till vid ADD PARTITION"
ER_COALESCE_PARTITION_NO_PARTITION
        eng "At least one partition must be coalesced"
        ger "Zumindest eine Partition muss mit COALESCE PARTITION zusammengefügt werden"
        swe "Åtminstone en partition måste slås ihop vid COALESCE PARTITION"
ER_REORG_PARTITION_NOT_EXIST
        eng "More partitions to reorganize than there are partitions"
        ger "Es wurde versucht, mehr Partitionen als vorhanden zu reorganisieren"
        swe "Fler partitioner att reorganisera än det finns partitioner"
ER_SAME_NAME_PARTITION
        eng "Duplicate partition name %-.192s"
        ger "Doppelter Partitionsname: %-.192s"
        swe "Duplicerat partitionsnamn %-.192s"
ER_NO_BINLOG_ERROR
        eng "It is not allowed to shut off binlog on this command"
        ger "Es es nicht erlaubt, bei diesem Befehl binlog abzuschalten"
        swe "Det är inte tillåtet att stänga av binlog på detta kommando"
ER_CONSECUTIVE_REORG_PARTITIONS
        eng "When reorganizing a set of partitions they must be in consecutive order"
        ger "Bei der Reorganisation eines Satzes von Partitionen müssen diese in geordneter Reihenfolge vorliegen"
        swe "När ett antal partitioner omorganiseras måste de vara i konsekutiv ordning"
ER_REORG_OUTSIDE_RANGE
        eng "Reorganize of range partitions cannot change total ranges except for last partition where it can extend the range"
        ger "Die Reorganisation von RANGE-Partitionen kann Gesamtbereiche nicht verändern, mit Ausnahme der letzten Partition, die den Bereich erweitern kann"
        swe "Reorganisering av rangepartitioner kan inte ändra den totala intervallet utom för den sista partitionen där intervallet kan utökas"
ER_PARTITION_FUNCTION_FAILURE
        eng "Partition function not supported in this version for this handler"
        ger "Partitionsfunktion in dieser Version dieses Handlers nicht unterstützt"
OBSOLETE_ER_PART_STATE_ERROR
        eng "Partition state cannot be defined from CREATE/ALTER TABLE"
        ger "Partitionszustand kann nicht von CREATE oder ALTER TABLE aus definiert werden"
        swe "Partition state kan inte definieras från CREATE/ALTER TABLE"
ER_LIMITED_PART_RANGE
        eng "The %-.64s handler only supports 32 bit integers in VALUES"
        ger "Der Handler %-.64s unterstützt in VALUES nur 32-Bit-Integers"
        swe "%-.64s stödjer endast 32 bitar i integers i VALUES"
ER_PLUGIN_IS_NOT_LOADED
        eng "Plugin '%-.192s' is not loaded"
        ger "Plugin '%-.192s' ist nicht geladen"
ER_WRONG_VALUE
        eng "Incorrect %-.32s value: '%-.128s'"
        ger "Falscher %-.32s-Wert: '%-.128s'"
ER_NO_PARTITION_FOR_GIVEN_VALUE
        eng "Table has no partition for value %-.64s"
        ger "Tabelle hat für den Wert %-.64s keine Partition"
ER_FILEGROUP_OPTION_ONLY_ONCE
        eng "It is not allowed to specify %s more than once"
        ger "%s darf nicht mehr als einmal angegegeben werden"
ER_CREATE_FILEGROUP_FAILED
        eng "Failed to create %s"
        ger "Anlegen von %s fehlgeschlagen"
ER_DROP_FILEGROUP_FAILED
        eng "Failed to drop %s"
        ger "Löschen von %s fehlgeschlagen"
ER_TABLESPACE_AUTO_EXTEND_ERROR
        eng "The handler doesn't support autoextend of tablespaces"
        ger "Der Handler unterstützt keine automatische Erweiterung (Autoextend) von Tablespaces"
ER_WRONG_SIZE_NUMBER
        eng "A size parameter was incorrectly specified, either number or on the form 10M"
        ger "Ein Größen-Parameter wurde unkorrekt angegeben, muss entweder Zahl sein oder im Format 10M"
ER_SIZE_OVERFLOW_ERROR
        eng "The size number was correct but we don't allow the digit part to be more than 2 billion"
        ger "Die Zahl für die Größe war korrekt, aber der Zahlanteil darf nicht größer als 2 Milliarden sein"
ER_ALTER_FILEGROUP_FAILED
        eng "Failed to alter: %s"
        ger "Änderung von %s fehlgeschlagen"
ER_BINLOG_ROW_LOGGING_FAILED
        eng "Writing one row to the row-based binary log failed"
        ger "Schreiben einer Zeilen ins zeilenbasierte Binärlog fehlgeschlagen"
OBSOLETE_ER_BINLOG_ROW_WRONG_TABLE_DEF
        eng "Table definition on source and replica does not match: %s"
        ger "Tabellendefinition auf Master und Slave stimmt nicht überein: %s"
OBSOLETE_ER_BINLOG_ROW_RBR_TO_SBR
        eng "Replica running with --log-replica-updates must use row-based binary logging to be able to replicate row-based binary log events"
        ger "Slave, die mit --log-replica-updates laufen, müssen zeilenbasiertes Loggen verwenden, um zeilenbasierte Binärlog-Ereignisse loggen zu können"
ER_EVENT_ALREADY_EXISTS
        eng "Event '%-.192s' already exists"
        ger "Event '%-.192s' existiert bereits"
OBSOLETE_ER_EVENT_STORE_FAILED
        eng "Failed to store event %s. Error code %d from storage engine."
        ger "Speichern von Event %s fehlgeschlagen. Fehlercode der Speicher-Engine: %d"
ER_EVENT_DOES_NOT_EXIST
        eng "Unknown event '%-.192s'"
        ger "Unbekanntes Event '%-.192s'"
OBSOLETE_ER_EVENT_CANT_ALTER
        eng "Failed to alter event '%-.192s'"
        ger "Ändern des Events '%-.192s' fehlgeschlagen"
OBSOLETE_ER_EVENT_DROP_FAILED
        eng "Failed to drop %s"
        ger "Löschen von %s fehlgeschlagen"
ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG
        eng "INTERVAL is either not positive or too big"
        ger "INTERVAL ist entweder nicht positiv oder zu groß"
ER_EVENT_ENDS_BEFORE_STARTS
        eng "ENDS is either invalid or before STARTS"
        ger "ENDS ist entweder ungültig oder liegt vor STARTS"
ER_EVENT_EXEC_TIME_IN_THE_PAST
  eng "Event execution time is in the past. Event has been disabled"
  ger "Ausführungszeit des Events liegt in der Vergangenheit. Event wurde deaktiviert"
OBSOLETE_ER_EVENT_OPEN_TABLE_FAILED
        eng "Failed to open mysql.event"
        ger "Öffnen von mysql.event fehlgeschlagen"
OBSOLETE_ER_EVENT_NEITHER_M_EXPR_NOR_M_AT
        eng "No datetime expression provided"
        ger "Kein DATETIME-Ausdruck angegeben"

# OBSOLETE, USE ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2
OBSOLETE_ER_COL_COUNT_DOESNT_MATCH_CORRUPTED
        eng "Column count of mysql.%s is wrong. Expected %d, found %d. The table is probably corrupted"
        ger "Spaltenanzahl von mysql.%s falsch. %d erwartet, aber %d gefunden. Tabelle ist wahrscheinlich beschädigt"

# OBSOLETE, USE ER_CANNOT_LOAD_FROM_TABLE_V2
OBSOLETE_ER_CANNOT_LOAD_FROM_TABLE
        eng "Cannot load from mysql.%s. The table is probably corrupted"
        ger "Kann mysql.%s nicht einlesen. Tabelle ist wahrscheinlich beschädigt"

OBSOLETE_ER_EVENT_CANNOT_DELETE
        eng "Failed to delete the event from mysql.event"
        ger "Löschen des Events aus mysql.event fehlgeschlagen"
OBSOLETE_ER_EVENT_COMPILE_ERROR
        eng "Error during compilation of event's body"
        ger "Fehler beim Kompilieren des Event-Bodys"
ER_EVENT_SAME_NAME
        eng "Same old and new event name"
        ger "Alter und neuer Event-Name sind gleich"
OBSOLETE_ER_EVENT_DATA_TOO_LONG
        eng "Data for column '%s' too long"
        ger "Daten der Spalte '%s' zu lang"
ER_DROP_INDEX_FK
        eng "Cannot drop index '%-.192s': needed in a foreign key constraint"
        ger "Kann Index '%-.192s' nicht löschen: wird für eine Fremdschlüsselbeschränkung benötigt"
# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
ER_WARN_DEPRECATED_SYNTAX_WITH_VER
        eng  "The syntax '%s' is deprecated and will be removed in MySQL %s. Please use %s instead"
        ger "Die Syntax '%s' ist veraltet und wird in MySQL %s entfernt. Bitte benutzen Sie statt dessen %s"
OBSOLETE_ER_CANT_WRITE_LOCK_LOG_TABLE
        eng "You can't write-lock a log table. Only read access is possible"
        ger "Eine Log-Tabelle kann nicht schreibgesperrt werden. Es ist ohnehin nur Lesezugriff möglich"
ER_CANT_LOCK_LOG_TABLE
        eng "You can't use locks with log tables."
        ger "Log-Tabellen können nicht gesperrt werden."
ER_FOREIGN_DUPLICATE_KEY_OLD_UNUSED 23000 S1009
        eng "Upholding foreign key constraints for table '%.192s', entry '%-.192s', key %d would lead to a duplicate entry"
# OBSOLETE, USE ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2
ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE
        eng "The column count of mysql.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure."
        ger "Spaltenanzahl von mysql.%s falsch. %d erwartet, aber %d erhalten. Erzeugt mit MySQL %d, jetzt unter %d. Bitte verwenden Sie die MySQL-Upgrade-Prozedur, um den Fehler zu beheben."
OBSOLETE_ER_TEMP_TABLE_PREVENTS_SWITCH_OUT_OF_RBR
        eng "Cannot switch out of the row-based binary log format when the session has open temporary tables"
        ger "Kann nicht aus dem zeilenbasierten Binärlog-Format herauswechseln, wenn die Sitzung offene temporäre Tabellen hat"
ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT
        eng "Cannot change the binary logging format inside a stored function or trigger"
        ger "Das Binärlog-Format kann innerhalb einer gespeicherten Funktion oder eines Triggers nicht geändert werden"
OBSOLETE_ER_NDB_CANT_SWITCH_BINLOG_FORMAT
        eng "The NDB cluster engine does not support changing the binlog format on the fly yet"
        ger "Die Speicher-Engine NDB Cluster unterstützt das Ändern des Binärlog-Formats zur Laufzeit noch nicht"
ER_PARTITION_NO_TEMPORARY
        eng "Cannot create temporary table with partitions"
        ger "Anlegen temporärer Tabellen mit Partitionen nicht möglich"
ER_PARTITION_CONST_DOMAIN_ERROR
        eng "Partition constant is out of partition function domain"
        ger "Partitionskonstante liegt außerhalb der Partitionsfunktionsdomäne"
        swe "Partitionskonstanten är utanför partitioneringsfunktionens domän"
ER_PARTITION_FUNCTION_IS_NOT_ALLOWED
        eng "This partition function is not allowed"
        ger "Diese Partitionierungsfunktion ist nicht erlaubt"
        swe "Denna partitioneringsfunktion är inte tillåten"
OBSOLETE_ER_DDL_LOG_ERROR_UNUSED
        eng "Error in DDL log"
        ger "Fehler im DDL-Log"
ER_NULL_IN_VALUES_LESS_THAN
        eng "Not allowed to use NULL value in VALUES LESS THAN"
        ger "In VALUES LESS THAN dürfen keine NULL-Werte verwendet werden"
        swe "Det är inte tillåtet att använda NULL-värden i VALUES LESS THAN"
ER_WRONG_PARTITION_NAME
        eng "Incorrect partition name"
        ger "Falscher Partitionsname"
        swe "Felaktigt partitionsnamn"
ER_CANT_CHANGE_TX_CHARACTERISTICS 25001
        eng "Transaction characteristics can't be changed while a transaction is in progress"
ER_DUP_ENTRY_AUTOINCREMENT_CASE
        eng "ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry '%-.192s' for key '%-.192s'"
        ger "ALTER TABLE führt zur Neusequenzierung von auto_increment, wodurch der doppelte Eintrag '%-.192s' für Schlüssel '%-.192s' auftritt"
OBSOLETE_ER_EVENT_MODIFY_QUEUE_ERROR
        eng "Internal scheduler error %d"
        ger "Interner Scheduler-Fehler %d"
ER_EVENT_SET_VAR_ERROR
        eng "Error during starting/stopping of the scheduler. Error code %u"
        ger "Fehler während des Startens oder Anhalten des Schedulers. Fehlercode %u"
ER_PARTITION_MERGE_ERROR
        eng "Engine cannot be used in partitioned tables"
        ger "Engine kann in partitionierten Tabellen nicht verwendet werden"
        swe "Engine inte användas i en partitionerad tabell"
OBSOLETE_ER_CANT_ACTIVATE_LOG
        eng "Cannot activate '%-.64s' log"
        ger "Kann Logdatei '%-.64s' nicht aktivieren"
OBSOLETE_ER_RBR_NOT_AVAILABLE
        eng "The server was not built with row-based replication"
        ger "Der Server wurde nicht mit zeilenbasierter Replikation gebaut"
ER_BASE64_DECODE_ERROR
        eng "Decoding of base64 string failed"
        swe "Avkodning av base64 sträng misslyckades"
        ger "Der Server hat keine zeilenbasierte Replikation"
ER_EVENT_RECURSION_FORBIDDEN
        eng "Recursion of EVENT DDL statements is forbidden when body is present"
        ger "Rekursivität von EVENT-DDL-Anweisungen ist unzulässig wenn ein Hauptteil (Body) existiert"
OBSOLETE_ER_EVENTS_DB_ERROR
        eng "Cannot proceed because system tables used by Event Scheduler were found damaged at server start"
        ger "Kann nicht weitermachen, weil die Tabellen, die von Events verwendet werden, beim Serverstart als beschädigt markiert wurden"
ER_ONLY_INTEGERS_ALLOWED
        eng "Only integers allowed as number here"
        ger "An dieser Stelle sind nur Ganzzahlen zulässig"
ER_UNSUPORTED_LOG_ENGINE
        eng "This storage engine cannot be used for log tables"
        ger "Diese Speicher-Engine kann für Logtabellen nicht verwendet werden"
ER_BAD_LOG_STATEMENT
        eng "You cannot '%s' a log table if logging is enabled"
        ger "Sie können eine Logtabelle nicht '%s', wenn Loggen angeschaltet ist"
ER_CANT_RENAME_LOG_TABLE
        eng "Cannot rename '%s'. When logging enabled, rename to/from log table must rename two tables: the log table to an archive table and another table back to '%s'"
        ger "Kann '%s' nicht umbenennen. Wenn Loggen angeschaltet ist, müssen zwei Tabellen umbenannt werden: die Logtabelle zu einer Archivtabelle, und eine weitere Tabelle zu '%s'"
ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT 42000
        eng "Incorrect parameter count in the call to native function '%-.192s'"
        ger "Falsche Anzahl von Parametern beim Aufruf der nativen Funktion '%-.192s'"
ER_WRONG_PARAMETERS_TO_NATIVE_FCT 42000
        eng "Incorrect parameters in the call to native function '%-.192s'"
        ger "Falscher Parameter beim Aufruf der nativen Funktion '%-.192s'"
ER_WRONG_PARAMETERS_TO_STORED_FCT 42000
        eng "Incorrect parameters in the call to stored function %-.192s"
        ger "Falsche Parameter beim Aufruf der gespeicherten Funktion %-.192s"
ER_NATIVE_FCT_NAME_COLLISION
        eng "This function '%-.192s' has the same name as a native function"
        ger "Die Funktion '%-.192s' hat denselben Namen wie eine native Funktion"
# When using this error message, use the ER_DUP_ENTRY error code.  See, for
# example, code in handler.cc.
ER_DUP_ENTRY_WITH_KEY_NAME 23000 S1009
        cze "Zvojený klíč '%-.64s' (číslo klíče '%-.385s')"
        dan "Ens værdier '%-.64s' for indeks '%-.385s'"
        nla "Dubbele ingang '%-.64s' voor zoeksleutel '%-.385s'"
        eng "Duplicate entry '%-.64s' for key '%-.385s'"
        est "Kattuv väärtus '%-.64s' võtmele '%-.385s'"
        fre "Duplicata du champ '%-.64s' pour la clef '%-.385s'"
        ger "Doppelter Eintrag '%-.64s' für Schlüssel '%-.385s'"
        greek "Διπλή εγγραφή '%-.64s' για το κλειδί '%-.385s'"
        hun "Duplikalt bejegyzes '%-.64s' a '%-.385s' kulcs szerint."
        ita "Valore duplicato '%-.64s' per la chiave '%-.385s'"
        jpn "'%-.64s' は索引 '%-.385s' で重複しています。"
        kor "중복된 입력 값 '%-.64s': key '%-.385s'"
        nor "Like verdier '%-.64s' for nøkkel '%-.385s'"
        norwegian-ny "Like verdiar '%-.64s' for nykkel '%-.385s'"
        pol "Powtórzone wystąpienie '%-.64s' dla klucza '%-.385s'"
        por "Entrada '%-.64s' duplicada para a chave '%-.385s'"
        rum "Cimpul '%-.64s' e duplicat pentru cheia '%-.385s'"
        rus "Дублирующаяся запись '%-.64s' по ключу '%-.385s'"
        serbian "Dupliran unos '%-.64s' za ključ '%-.385s'"
        slo "Opakovaný kľúč '%-.64s' (číslo kľúča '%-.385s')"
        spa "Entrada duplicada '%-.64s' para la clave '%-.385s'"
        swe "Dublett '%-.64s' för nyckel '%-.385s'"
        ukr "Дублюючий запис '%-.64s' для ключа '%-.385s'"
ER_BINLOG_PURGE_EMFILE
  eng "Too many files opened, please execute the command again"
  ger "Zu viele offene Dateien, bitte führen Sie den Befehl noch einmal aus"
ER_EVENT_CANNOT_CREATE_IN_THE_PAST
  eng "Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was dropped immediately after creation."
  ger "Ausführungszeit des Events liegt in der Vergangenheit, und es wurde ON COMPLETION NOT PRESERVE gesetzt. Das Event wurde unmittelbar nach Erzeugung gelöscht."
ER_EVENT_CANNOT_ALTER_IN_THE_PAST
  eng "Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future."
  ger "Execution Zeitpunkt des Ereignisses in der Vergangenheit liegt, und es war NACH ABSCHLUSS Set nicht erhalten. Die Veranstaltung wurde nicht verändert. Geben Sie einen Zeitpunkt in der Zukunft."
OBSOLETE_ER_SLAVE_INCIDENT
  eng "The incident %s occurred on the source. Message: %s"
  ger "Der Vorfall %s passierte auf dem Master. Meldung: %s"
ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT
  eng "Table has no partition for some existing values"
  ger "Tabelle hat für einige bestehende Werte keine Partition"
ER_BINLOG_UNSAFE_STATEMENT
  eng "Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. %s"
  swe "Detta är inte säkert att logga i statement-format, för BINLOG_FORMAT = STATEMENT. %s"
  ger "Unsichere Anweisung ins Binärlog geschrieben, weil Anweisungsformat BINLOG_FORMAT = STATEMENT. %s"
ER_BINLOG_FATAL_ERROR
  eng "Fatal error: %s"
  ger "Fataler Fehler: %s"
OBSOLETE_ER_SLAVE_RELAY_LOG_READ_FAILURE
  eng "Relay log read failure: %s"
  ger "Relaylog-Lesefehler: %s"
OBSOLETE_ER_SLAVE_RELAY_LOG_WRITE_FAILURE
  eng "Relay log write failure: %s"
  ger "Relaylog-Schreibfehler: %s"
OBSOLETE_ER_SLAVE_CREATE_EVENT_FAILURE
  eng "Failed to create %s"
  ger "Erzeugen von %s fehlgeschlagen"
OBSOLETE_ER_SLAVE_MASTER_COM_FAILURE
  eng "Source command %s failed: %s"
  ger "Master-Befehl %s fehlgeschlagen: %s"
ER_BINLOG_LOGGING_IMPOSSIBLE
  eng "Binary logging not possible. Message: %s"
  ger "Binärlogging nicht möglich. Meldung: %s"
ER_VIEW_NO_CREATION_CTX
  eng "View `%-.64s`.`%-.64s` has no creation context"
  ger "View `%-.64s`.`%-.64s` hat keinen Erzeugungskontext"
ER_VIEW_INVALID_CREATION_CTX
  eng "Creation context of view `%-.64s`.`%-.64s' is invalid"
  ger "Erzeugungskontext des Views`%-.64s`.`%-.64s' ist ungültig"
OBSOLETE_ER_SR_INVALID_CREATION_CTX
  eng "Creation context of stored routine `%-.64s`.`%-.64s` is invalid"
  ger "Erzeugungskontext der gespeicherten Routine`%-.64s`.`%-.64s` ist ungültig"
ER_TRG_CORRUPTED_FILE
  eng "Corrupted TRG file for table `%-.64s`.`%-.64s`"
  ger "Beschädigte TRG-Datei für Tabelle `%-.64s`.`%-.64s`"
ER_TRG_NO_CREATION_CTX
  eng "Triggers for table `%-.64s`.`%-.64s` have no creation context"
  ger "Trigger für Tabelle `%-.64s`.`%-.64s` haben keinen Erzeugungskontext"
ER_TRG_INVALID_CREATION_CTX
  eng "Trigger creation context of table `%-.64s`.`%-.64s` is invalid"
  ger "Trigger-Erzeugungskontext der Tabelle `%-.64s`.`%-.64s` ist ungültig"
ER_EVENT_INVALID_CREATION_CTX
  eng "Creation context of event `%-.64s`.`%-.64s` is invalid"
  ger "Erzeugungskontext des Events `%-.64s`.`%-.64s` ist ungültig"
ER_TRG_CANT_OPEN_TABLE
  eng "Cannot open table for trigger `%-.64s`.`%-.64s`"
  ger "Kann Tabelle für den Trigger `%-.64s`.`%-.64s` nicht öffnen"
OBSOLETE_ER_CANT_CREATE_SROUTINE
  eng "Cannot create stored routine `%-.64s`. Check warnings"
  ger "Kann gespeicherte Routine `%-.64s` nicht erzeugen. Beachten Sie die Warnungen"
OBSOLETE_ER_NEVER_USED
  eng "Ambiguous replica modes combination. %s"
  ger "Mehrdeutige Kombination von Slave-Modi. %s"
ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT
  eng "The BINLOG statement of type `%s` was not preceded by a format description BINLOG statement."
  ger "Der BINLOG-Anweisung vom Typ `%s` ging keine BINLOG-Anweisung zur Formatbeschreibung voran."
ER_REPLICA_CORRUPT_EVENT
  eng "Corrupted replication event was detected"
  ger "Beschädigtes Replikationsereignis entdeckt"
OBSOLETE_ER_LOAD_DATA_INVALID_COLUMN_UNUSED
  eng "Invalid column reference (%-.64s) in LOAD DATA"
  ger "Ungültige Spaltenreferenz (%-.64s) bei LOAD DATA"
ER_LOG_PURGE_NO_FILE
  eng "Being purged log %s was not found"
  ger "Zu bereinigende Logdatei %s wurde nicht gefunden"
ER_XA_RBTIMEOUT XA106
  eng "XA_RBTIMEOUT: Transaction branch was rolled back: took too long"
  ger "XA_RBTIMEOUT: Transaktionszweig wurde zurückgerollt: Zeitüberschreitung"
ER_XA_RBDEADLOCK XA102
  eng "XA_RBDEADLOCK: Transaction branch was rolled back: deadlock was detected"
  ger "XA_RBDEADLOCK: Transaktionszweig wurde zurückgerollt: Deadlock entdeckt"
ER_NEED_REPREPARE
  eng "Prepared statement needs to be re-prepared"
  ger "Vorbereitete Anweisungen müssen noch einmal vorbereitet werden"
OBSOLETE_ER_DELAYED_NOT_SUPPORTED
  eng "DELAYED option not supported for table '%-.192s'"
  ger "Die DELAYED-Option wird für Tabelle '%-.192s' nicht unterstützt"
WARN_NO_CONNECTION_METADATA
  eng "The connection metadata structure does not exist"
  ger "Die Master-Info-Struktur existiert nicht"
WARN_OPTION_IGNORED
  eng "<%-.64s> option ignored"
  ger "Option <%-.64s> ignoriert"
ER_PLUGIN_DELETE_BUILTIN
  eng "Built-in plugins cannot be deleted"
  ger "Eingebaute Plugins können nicht gelöscht werden"
WARN_PLUGIN_BUSY
  eng "Plugin is busy and will be uninstalled on shutdown"
  ger "Plugin wird verwendet und wird erst beim Herunterfahren deinstalliert"
ER_VARIABLE_IS_READONLY
  eng "%s variable '%s' is read-only. Use SET %s to assign the value"
  ger "%s Variable '%s' ist nur lesbar. Benutzen Sie SET %s, um einen Wert zuzuweisen"
ER_WARN_ENGINE_TRANSACTION_ROLLBACK
  eng "Storage engine %s does not support rollback for this statement. Transaction rolled back and must be restarted"
  ger "Speicher-Engine %s unterstützt für diese Anweisung kein Rollback. Transaktion wurde zurückgerollt und muss neu gestartet werden"
OBSOLETE_ER_SLAVE_HEARTBEAT_FAILURE
  eng "Unexpected source's heartbeat data: %s"
  ger "Unerwartete Daten vom Heartbeat des Masters: %s"
ER_REPLICA_HEARTBEAT_VALUE_OUT_OF_RANGE
  eng "The requested value for the heartbeat period is either negative or exceeds the maximum allowed (%s seconds)."
ER_NDB_REPLICATION_SCHEMA_ERROR
  eng "Bad schema for mysql.ndb_replication table. Message: %-.64s"
  ger "Fehlerhaftes Schema für mysql.ndb_replication table. Meldung: %-.64s"
ER_CONFLICT_FN_PARSE_ERROR
  eng "Error in parsing conflict function. Message: %-.64s"
  ger "Fehler beim Parsen einer Konflikt-Funktion. Meldung: %-.64s"
ER_EXCEPTIONS_WRITE_ERROR
  eng "Write to exceptions table failed. Message: %-.128s"
  ger "Schreiben in Ausnahme-Tabelle fehlgeschlagen. Meldung: %-.128s"
ER_TOO_LONG_TABLE_COMMENT
  eng "Comment for table '%-.64s' is too long (max = %lu)"
  por "Comentário para a tabela '%-.64s' é longo demais (max = %lu)"
  ger "Kommentar für Tabelle '%-.64s' ist zu lang (max = %lu)"
ER_TOO_LONG_FIELD_COMMENT
  eng "Comment for field '%-.64s' is too long (max = %lu)"
  por "Comentário para o campo '%-.64s' é longo demais (max = %lu)"
  ger "Kommentar für Feld '%-.64s' ist zu lang (max = %lu)"
ER_FUNC_INEXISTENT_NAME_COLLISION 42000
  eng "FUNCTION %s does not exist. Check the 'Function Name Parsing and Resolution' section in the Reference Manual"
  ger "FUNCTION %s existiert nicht. Erläuterungen im Abschnitt 'Function Name Parsing and Resolution' im Referenzhandbuch"
ER_DATABASE_NAME
  eng "Database"
  swe "Databas"
  ger "Datenbank"
ER_TABLE_NAME
  eng "Table"
  swe "Tabell"
  ger "Tabelle"
ER_PARTITION_NAME
  eng "Partition"
  swe "Partition"
  ger "Partition"
ER_SUBPARTITION_NAME
  eng "Subpartition"
  swe "Subpartition"
  ger "Unterpartition"
ER_TEMPORARY_NAME
  eng "Temporary"
  swe "Temporär"
  ger "Temporär"
ER_RENAMED_NAME
  eng "Renamed"
  swe "Namnändrad"
  ger "Umbenannt"
ER_TOO_MANY_CONCURRENT_TRXS
  eng  "Too many active concurrent transactions"
  ger  "Zu viele aktive simultane Transaktionen"
WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED
  eng "Non-ASCII separator arguments are not fully supported"
  ger "Nicht-ASCII-Trennargumente werden nicht vollständig unterstützt"
ER_DEBUG_SYNC_TIMEOUT
  eng "debug sync point wait timed out"
  ger "Debug Sync Point Wartezeit überschritten"
ER_DEBUG_SYNC_HIT_LIMIT
  eng "debug sync point hit limit reached"
  ger "Debug Sync Point Hit Limit erreicht"
ER_DUP_SIGNAL_SET 42000
  eng "Duplicate condition information item '%s'"
  ger "Informationselement '%s' für Duplikatbedingung"
# Note that the SQLSTATE is not 01000, it is provided by SIGNAL/RESIGNAL
ER_SIGNAL_WARN 01000
  eng "Unhandled user-defined warning condition"
  ger "Unbehandelte benutzerdefinierte Warnbedingung"
# Note that the SQLSTATE is not 02000, it is provided by SIGNAL/RESIGNAL
ER_SIGNAL_NOT_FOUND 02000
  eng "Unhandled user-defined not found condition"
  ger "Unbehandelte benutzerdefinierte Nicht-gefunden-Bedingung"
# Note that the SQLSTATE is not HY000, it is provided by SIGNAL/RESIGNAL
ER_SIGNAL_EXCEPTION HY000
  eng "Unhandled user-defined exception condition"
  ger "Unbehandelte benutzerdefinierte Ausnahmebedingung"
ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER 0K000
  eng "RESIGNAL when handler not active"
  ger "RESIGNAL bei nicht aktivem Handler"
ER_SIGNAL_BAD_CONDITION_TYPE
  eng "SIGNAL/RESIGNAL can only use a CONDITION defined with SQLSTATE"
  ger "SIGNAL/RESIGNAL kann nur mit einer Bedingung (CONDITION) benutzt werden, die bei SQLSTATE definiert wurde"
WARN_COND_ITEM_TRUNCATED
  eng "Data truncated for condition item '%s'"
  ger "Daten gekürzt für Bedingungselement '%s'"
ER_COND_ITEM_TOO_LONG
  eng "Data too long for condition item '%s'"
  ger "Daten zu lang für Bedingungselement '%s'"
ER_UNKNOWN_LOCALE
  eng "Unknown locale: '%-.64s'"
  ger "Unbekannte Locale: '%-.64s'"
ER_REPLICA_IGNORE_SERVER_IDS
  eng "The requested server id %d clashes with the replica startup option --replicate-same-server-id"
  ger "Die angeforderte Server-ID %d steht im Konflikt mit der Startoption --replicate-same-server-id für den Slave"
OBSOLETE_ER_QUERY_CACHE_DISABLED
  eng "Query cache is disabled; restart the server with query_cache_type=1 to enable it"
  ger "Abfragen-Cache ist deaktiviert. Starten Sie den Server neu mit query_cache_type=1, um ihn zu aktivieren"
ER_SAME_NAME_PARTITION_FIELD
  eng "Duplicate partition field name '%-.192s'"
  ger "Partitionsfeld '%-.192s' ist ein Duplikat"
ER_PARTITION_COLUMN_LIST_ERROR
  eng "Inconsistency in usage of column lists for partitioning"
  ger "Inkonsistenz bei der Benutzung von Spaltenlisten für Partitionierung"
ER_WRONG_TYPE_COLUMN_VALUE_ERROR
  eng "Partition column values of incorrect type"
  ger "Partitionsspaltenwerte sind vom falschen Typ"
ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR
  eng "Too many fields in '%-.192s'"
  ger "Zu viele Felder in '%-.192s'"
ER_MAXVALUE_IN_VALUES_IN
  eng "Cannot use MAXVALUE as value in VALUES IN"
  ger "MAXVALUE kann nicht als Wert in VALUES IN verwendet werden"
ER_TOO_MANY_VALUES_ERROR
  eng "Cannot have more than one value for this type of %-.64s partitioning"
  ger "Für den Partionierungstyp %-.64s darf es nicht mehr als einen Wert geben"
ER_ROW_SINGLE_PARTITION_FIELD_ERROR
  eng "Row expressions in VALUES IN only allowed for multi-field column partitioning"
  ger "Zeilenausdrücke in VALUES IN sind nur für Mehrfeld-Spaltenpartionierung erlaubt"
ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD
  eng "Field '%-.192s' is of a not allowed type for this type of partitioning"
  ger "Feld '%-.192s' ist für diese Art von Partitionierung von einem nicht zulässigen Typ"
ER_PARTITION_FIELDS_TOO_LONG
  eng "The total length of the partitioning fields is too large"
  ger "Die Gesamtlänge der Partitionsfelder ist zu groß"
ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE
  eng "Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved."
ER_BINLOG_ROW_MODE_AND_STMT_ENGINE
  eng "Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging."
ER_BINLOG_UNSAFE_AND_STMT_ENGINE
  eng "Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s"
ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE
  eng "Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging."
ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
  eng "Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s"
ER_BINLOG_ROW_INJECTION_AND_STMT_MODE
  eng "Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT."
ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE
  eng "Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging."

ER_BINLOG_UNSAFE_LIMIT
  eng "The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted."
OBSOLETE_ER_UNUSED4
  eng "The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted."
ER_BINLOG_UNSAFE_SYSTEM_TABLE
  eng "The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on replicas."
ER_BINLOG_UNSAFE_AUTOINC_COLUMNS
  eng "Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly."
ER_BINLOG_UNSAFE_UDF
  eng "Statement is unsafe because it uses a UDF which may not return the same value on the replica."
ER_BINLOG_UNSAFE_SYSTEM_VARIABLE
  eng "Statement is unsafe because it uses a system variable that may have a different value on the replica."
ER_BINLOG_UNSAFE_SYSTEM_FUNCTION
  eng "Statement is unsafe because it uses a system function that may return a different value on the replica."
ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS
  eng "Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction."

ER_MESSAGE_AND_STATEMENT
  eng "%s Statement: %s"

OBSOLETE_ER_SLAVE_CONVERSION_FAILED
  eng "Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'"
ER_REPLICA_CANT_CREATE_CONVERSION
  eng "Can't create conversion table for table '%-.192s.%-.192s'"
ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT
  eng "Cannot modify @@session.binlog_format inside a transaction"
ER_PATH_LENGTH
  eng "The path specified for %.64s is too long."
ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT
  eng "'%s' is deprecated and will be removed in a future release."
  ger "'%s' ist veraltet und wird in einer zukünftigen Version entfernt werden."

ER_WRONG_NATIVE_TABLE_STRUCTURE
        eng "Native table '%-.64s'.'%-.64s' has the wrong structure"

ER_WRONG_PERFSCHEMA_USAGE
        eng "Invalid performance_schema usage."
ER_WARN_I_S_SKIPPED_TABLE
  eng "Table '%s'.'%s' was skipped since its definition is being modified by concurrent DDL statement"

ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT
  eng "Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction"
ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT
  eng "Cannot change the binlog direct flag inside a stored function or trigger"
ER_SPATIAL_MUST_HAVE_GEOM_COL 42000
  eng "A SPATIAL index may only contain a geometrical type column"
  ger "Ein raumbezogener Index (SPATIAL) darf nur Spalten geometrischen Typs enthalten"
ER_TOO_LONG_INDEX_COMMENT
  eng "Comment for index '%-.64s' is too long (max = %lu)"

ER_LOCK_ABORTED
  eng "Wait on a lock was aborted due to a pending exclusive lock"

ER_DATA_OUT_OF_RANGE 22003
  eng "%s value is out of range in '%s'"

OBSOLETE_ER_WRONG_SPVAR_TYPE_IN_LIMIT
  eng "A variable of a non-integer based type in LIMIT clause"

ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE
  eng "Mixing self-logging and non-self-logging engines in a statement is unsafe."

ER_BINLOG_UNSAFE_MIXED_STATEMENT
  eng "Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them."

ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN
  eng "Cannot modify @@session.sql_log_bin inside a transaction"

ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN
  eng "Cannot change the sql_log_bin inside a stored function or trigger"

ER_FAILED_READ_FROM_PAR_FILE
  eng "Failed to read from the .par file"
  swe "Misslyckades läsa från .par filen"

ER_VALUES_IS_NOT_INT_TYPE_ERROR
  eng "VALUES value for partition '%-.64s' must have type INT"
  swe "Värden i VALUES för partition '%-.64s' måste ha typen INT"

ER_ACCESS_DENIED_NO_PASSWORD_ERROR 28000
        cze "Přístup pro uživatele '%-.48s'@'%-.64s'"
        dan "Adgang nægtet bruger: '%-.48s'@'%-.64s'"
        nla "Toegang geweigerd voor gebruiker: '%-.48s'@'%-.64s'"
        eng "Access denied for user '%-.48s'@'%-.64s'"
        est "Ligipääs keelatud kasutajale '%-.48s'@'%-.64s'"
        fre "Accès refusé pour l'utilisateur: '%-.48s'@'@%-.64s'"
        ger "Benutzer '%-.48s'@'%-.64s' hat keine Zugriffsberechtigung"
        greek "Δεν επιτέρεται η πρόσβαση στο χρήστη: '%-.48s'@'%-.64s'"
        hun "A(z) '%-.48s'@'%-.64s' felhasznalo szamara tiltott eleres."
        ita "Accesso non consentito per l'utente: '%-.48s'@'%-.64s'"
        jpn "ユーザー '%-.48s'@'%-.64s' のアクセスは拒否されました。"
        kor "'%-.48s'@'%-.64s' 사용자는 접근이 거부 되었습니다."
        nor "Tilgang nektet for bruker: '%-.48s'@'%-.64s'"
        norwegian-ny "Tilgang ikke tillate for brukar: '%-.48s'@'%-.64s'"
        por "Acesso negado para o usuário '%-.48s'@'%-.64s'"
        rum "Acces interzis pentru utilizatorul: '%-.48s'@'%-.64s'"
        rus "Доступ закрыт для пользователя '%-.48s'@'%-.64s'"
        serbian "Pristup je zabranjen korisniku '%-.48s'@'%-.64s'"
        slo "Zakázaný prístup pre užívateľa: '%-.48s'@'%-.64s'"
        spa "Acceso negado para usuario: '%-.48s'@'%-.64s'"
        swe "Användare '%-.48s'@'%-.64s' är ej berättigad att logga in"
        ukr "Доступ заборонено для користувача: '%-.48s'@'%-.64s'"

OBSOLETE_ER_SET_PASSWORD_AUTH_PLUGIN
        eng "SET PASSWORD has no significance for users authenticating via plugins"

OBSOLETE_ER_GRANT_PLUGIN_USER_EXISTS
        eng "GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists"

ER_TRUNCATE_ILLEGAL_FK 42000
  eng "Cannot truncate a table referenced in a foreign key constraint (%.192s)"

ER_PLUGIN_IS_PERMANENT
  eng "Plugin '%s' is force_plus_permanent and can not be unloaded"

ER_REPLICA_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN
  eng "The requested value for the heartbeat period is less than 1 millisecond. The value is reset to 0, meaning that heartbeating will effectively be disabled."

ER_REPLICA_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX
  eng "The requested value for the heartbeat period exceeds the value of `replica_net_timeout' seconds. A sensible value for the period should be less than the timeout."

ER_STMT_CACHE_FULL
        eng "Multi-row statements required more than 'max_binlog_stmt_cache_size' bytes of storage; increase this mysqld variable and try again"

ER_MULTI_UPDATE_KEY_CONFLICT
  eng "Primary key/partition key update is not allowed since the table is updated both as '%-.192s' and '%-.192s'."

# When translating this error message make sure to include "ALTER TABLE" in the
# message as mysqlcheck parses the error message looking for ALTER TABLE.
ER_TABLE_NEEDS_REBUILD
        eng "Table rebuild required. Please do \"ALTER TABLE `%-.64s` FORCE\" or dump/reload to fix it!"

WARN_OPTION_BELOW_LIMIT
  eng "The value of '%s' should be no less than the value of '%s'"

ER_INDEX_COLUMN_TOO_LONG
  eng "Index column size too large. The maximum column size is %lu bytes."

ER_ERROR_IN_TRIGGER_BODY
  eng "Trigger '%-.64s' has an error in its body: '%-.256s'"

ER_ERROR_IN_UNKNOWN_TRIGGER_BODY
  eng "Unknown trigger has an error in its body: '%-.256s'"

ER_INDEX_CORRUPT
  eng "Index %s is corrupted"

ER_UNDO_RECORD_TOO_BIG
  eng "Undo log record is too big."

ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT
  eng "INSERT IGNORE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE
  eng "INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_REPLACE_SELECT
 eng "REPLACE... SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT
  eng "CREATE... IGNORE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT
  eng "CREATE... REPLACE SELECT is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are replaced. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_UPDATE_IGNORE
  eng "UPDATE IGNORE is unsafe because the order in which rows are updated determines which (if any) rows are ignored. This order cannot be predicted and may differ on source and the replica."

ER_PLUGIN_NO_UNINSTALL
  eng "Plugin '%s' is marked as not dynamically uninstallable. You have to stop the server to uninstall it."

ER_PLUGIN_NO_INSTALL
  eng "Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it."

ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT
  eng "Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC
  eng "CREATE TABLE... SELECT...  on a table with an auto-increment column is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are inserted. This order cannot be predicted and may differ on source and the replica."

ER_BINLOG_UNSAFE_INSERT_TWO_KEYS
  eng "INSERT... ON DUPLICATE KEY UPDATE  on a table with more than one UNIQUE KEY is unsafe"

ER_TABLE_IN_FK_CHECK
  eng "Table is being used in foreign key check."

ER_UNSUPPORTED_ENGINE
  eng "Storage engine '%s' does not support system tables. [%s.%s]"

ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST
  eng "INSERT into autoincrement field which is not the first part in the composed primary key is unsafe."
#
#  End of 5.5 error messages.
#

ER_CANNOT_LOAD_FROM_TABLE_V2
  eng "Cannot load from %s.%s. The table is probably corrupted"
  ger "Kann %s.%s nicht einlesen. Tabelle ist wahrscheinlich beschädigt"

ER_SOURCE_DELAY_VALUE_OUT_OF_RANGE
  eng "The requested value %s for the source delay exceeds the maximum %u"
ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT
  eng "Only Format_description_log_event and row events are allowed in BINLOG statements (but %s was provided)"

ER_PARTITION_EXCHANGE_DIFFERENT_OPTION
  eng "Non matching attribute '%-.64s' between partition and table"
  swe "Attributet '%-.64s' är olika mellan partition och tabell"
ER_PARTITION_EXCHANGE_PART_TABLE
  eng "Table to exchange with partition is partitioned: '%-.64s'"
  swe "Tabellen att byta ut mot partition är partitionerad: '%-.64s'"
ER_PARTITION_EXCHANGE_TEMP_TABLE
  eng "Table to exchange with partition is temporary: '%-.64s'"
  swe "Tabellen att byta ut mot partition är temporär: '%-.64s'"
ER_PARTITION_INSTEAD_OF_SUBPARTITION
  eng "Subpartitioned table, use subpartition instead of partition"
  swe "Subpartitionerad tabell, använd subpartition istället för partition"
ER_UNKNOWN_PARTITION
  eng "Unknown partition '%-.64s' in table '%-.64s'"
  swe "Okänd partition '%-.64s' i tabell '%-.64s'"
ER_TABLES_DIFFERENT_METADATA
  eng "Tables have different definitions"
  swe "Tabellerna har olika definitioner"
ER_ROW_DOES_NOT_MATCH_PARTITION
  eng "Found a row that does not match the partition"
  swe "Hittade en rad som inte passar i partitionen"
ER_BINLOG_CACHE_SIZE_GREATER_THAN_MAX
  eng "Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size."
ER_WARN_INDEX_NOT_APPLICABLE
  eng "Cannot use %-.64s access on index '%-.64s' due to type or collation conversion on field '%-.64s'"

ER_PARTITION_EXCHANGE_FOREIGN_KEY
  eng "Table to exchange with partition has foreign key references: '%-.64s'"
  swe "Tabellen att byta ut mot partition har foreign key referenser: '%-.64s'"
OBSOLETE_ER_NO_SUCH_KEY_VALUE
  eng "Key value '%-.192s' was not found in table '%-.192s.%-.192s'"
ER_RPL_INFO_DATA_TOO_LONG
  eng "Data for column '%s' too long"
OBSOLETE_ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE
  eng "Replication event checksum verification failed while reading from network."
OBSOLETE_ER_BINLOG_READ_EVENT_CHECKSUM_FAILURE
  eng "Replication event checksum verification failed while reading from a log file."

ER_BINLOG_STMT_CACHE_SIZE_GREATER_THAN_MAX
  eng "Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size."
ER_CANT_UPDATE_TABLE_IN_CREATE_TABLE_SELECT
  eng "Can't update table '%-.192s' while '%-.192s' is being created."

ER_PARTITION_CLAUSE_ON_NONPARTITIONED
  eng "PARTITION () clause on non partitioned table"
  swe "PARTITION () klausul för en icke partitionerad tabell"
ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET
  eng "Found a row not matching the given partition set"
  swe "Hittade en rad som inte passar i någon given partition"

# Not used any longer, use ER_UNKNOWN_PARTITION which includes the tablename.
# was ER_NO_SUCH_PARTITION
OBSOLETE_ER_NO_SUCH_PARTITION__UNUSED
  cze "partion '%-.64s' neexistuje"
  dan "partition '%-.64s' eksisterer ikke"
  nla "partition '%-.64s' bestaat niet"
  eng "partition '%-.64s' doesn't exist"
  est "partition '%-.64s' ei eksisteeri"
  fre "La partition '%-.64s' n'existe pas"
  ger "Die partition '%-.64s' existiert nicht"
  hun "A '%-.64s' partition nem letezik"
  ita "La tabella particione '%-.64s' non esiste"
  jpn "パーティション '%-.64s' は存在しません。"
  nor "Partition '%-.64s' doesn't exist"
  norwegian-ny "Partition '%-.64s' doesn't exist"
  pol "Partition '%-.64s' doesn't exist"
  por "Particion '%-.64s' n?o existe"
  rum "Partition '%-.64s' nu exista"
  serbian "Partition '%-.64s' ne postoji"
  slo "Partition '%-.64s' doesn't exist"
  spa "Particion '%-.64s' no existe"
  swe "Det finns ingen partition som heter '%-.64s'"

ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE
  eng "Failure while changing the type of replication repository: %s."

ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE
  eng "The creation of some temporary tables could not be rolled back."
ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE
  eng "Some temporary tables were dropped, but these operations could not be rolled back."

ER_MTA_FEATURE_IS_NOT_SUPPORTED
  eng "%s is not supported in multi-threaded replica mode. %s"
ER_MTA_UPDATED_DBS_GREATER_MAX
  eng "The number of modified databases exceeds the maximum %d; the database names will not be included in the replication event metadata."
ER_MTA_CANT_PARALLEL
  eng "Cannot execute the current event group in the parallel mode. Encountered event %s, relay-log name %s, position %s which prevents execution of this event group in parallel mode. Reason: %s."
ER_MTA_INCONSISTENT_DATA
  eng "%s"

ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING
  eng "FULLTEXT index is not supported for partitioned tables."
  swe "FULLTEXT index stöds ej för partitionerade tabeller."

ER_DA_INVALID_CONDITION_NUMBER 35000
  eng "Invalid condition number"
  por "Número de condição inválido"

ER_INSECURE_PLAIN_TEXT
  eng "Sending passwords in plain text without SSL/TLS is extremely insecure."

ER_INSECURE_CHANGE_SOURCE
  eng "Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information."

ER_FOREIGN_DUPLICATE_KEY_WITH_CHILD_INFO 23000 S1009
        eng "Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in table '%.192s', key '%.192s'"
        ger "Fremdschlüssel-Beschränkung für Tabelle '%.192s', Datensatz '%-.192s' würde zu einem doppelten Eintrag in Tabelle '%.192s', Schlüssel '%.192s' führen"
        swe "FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera barntabell '%.192s' på grund av nyckel '%.192s'"

ER_FOREIGN_DUPLICATE_KEY_WITHOUT_CHILD_INFO 23000 S1009
        eng "Foreign key constraint for table '%.192s', record '%-.192s' would lead to a duplicate entry in a child table"
        ger "Fremdschlüssel-Beschränkung für Tabelle '%.192s', Datensatz '%-.192s' würde zu einem doppelten Eintrag in einer Kind-Tabelle führen"
        swe "FOREIGN KEY constraint för tabell '%.192s', posten '%-.192s' kan inte uppdatera en barntabell på grund av UNIQUE-test"

ER_SQLTHREAD_WITH_SECURE_REPLICA
  eng "Setting authentication options is not possible when only the Replica SQL Thread is being started."

ER_TABLE_HAS_NO_FT
  eng "The table does not have FULLTEXT index to support this query"

ER_VARIABLE_NOT_SETTABLE_IN_SF_OR_TRIGGER
  eng "The system variable %.200s cannot be set in stored functions or triggers."

ER_VARIABLE_NOT_SETTABLE_IN_TRANSACTION
  eng "The system variable %.200s cannot be set when there is an ongoing transaction."

OBSOLETE_ER_GTID_NEXT_IS_NOT_IN_GTID_NEXT_LIST
  eng "The system variable @@SESSION.GTID_NEXT has the value %.200s, which is not listed in @@SESSION.GTID_NEXT_LIST."

OBSOLETE_ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION
  eng "The system variable @@SESSION.GTID_NEXT cannot change inside a transaction."

ER_SET_STATEMENT_CANNOT_INVOKE_FUNCTION
  eng "The statement 'SET %.200s' cannot invoke a stored function."

ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL
  eng "The system variable @@SESSION.GTID_NEXT cannot be 'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL."

OBSOLETE_ER_SKIPPING_LOGGED_TRANSACTION
  eng "Skipping transaction %.200s because it has already been executed and logged."

ER_MALFORMED_GTID_SET_SPECIFICATION
  eng "Malformed GTID set specification '%.200s'."

ER_MALFORMED_GTID_SET_ENCODING
  eng "Malformed GTID set encoding."

ER_MALFORMED_GTID_SPECIFICATION
  eng "Malformed GTID specification '%.200s'."

ER_GNO_EXHAUSTED
  eng "Impossible to generate GTID: the integer component reached the maximum value. Restart the server with a new server_uuid."

ER_BAD_REPLICA_AUTO_POSITION
  eng "Parameters SOURCE_LOG_FILE, SOURCE_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when SOURCE_AUTO_POSITION is active."

ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF
  eng "CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 cannot be executed because @@GLOBAL.GTID_MODE = OFF."

ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET
  eng "Cannot execute statements with implicit commit inside a transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'."

ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON
  eng "GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON."

OBSOLETE_ER_GTID_MODE_REQUIRES_BINLOG
  eng "@@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or OFF_PERMISSIVE requires --log-bin and --log-replica-updates."

ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF
  eng "@@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @@GLOBAL.GTID_MODE = OFF."

ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON
  eng "@@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON."

ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF
  eng "@@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL value when @@GLOBAL.GTID_MODE = OFF."

OBSOLETE_ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED
  eng "Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF."

ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE
  eng "Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables."

ER_GTID_UNSAFE_CREATE_SELECT
  eng "Statement violates GTID consistency: CREATE TABLE ... SELECT."

OBSOLETE_ER_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRANSACTION
  eng "Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions."

ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME
  eng "The value of @@GLOBAL.GTID_MODE can only be changed one step at a time: OFF <-> OFF_PERMISSIVE <-> ON_PERMISSIVE <-> ON. Also note that this value must be stepped up or down simultaneously on all servers. See the Manual for instructions."

ER_SOURCE_HAS_PURGED_REQUIRED_GTIDS
  eng "Cannot replicate because the source purged required binary logs. Replicate the missing transactions from elsewhere, or provision a new replica from backup. Consider increasing the source's binary log expiration period. %s"

ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID
  eng "@@SESSION.GTID_NEXT cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK."

ER_UNKNOWN_EXPLAIN_FORMAT
  eng "Unknown EXPLAIN format name: '%s'"
  rus "Неизвестное имя формата команды EXPLAIN: '%s'"

ER_CANT_EXECUTE_IN_READ_ONLY_TRANSACTION 25006
  eng "Cannot execute statement in a READ ONLY transaction."

ER_TOO_LONG_TABLE_PARTITION_COMMENT
  eng "Comment for table partition '%-.64s' is too long (max = %lu)"

ER_REPLICA_CONFIGURATION
  eng "Replica is not configured or failed to initialize properly. You must at least set --server-id to enable either a source or a replica. Additional error messages can be found in the MySQL error log."

ER_INNODB_FT_LIMIT
  eng "InnoDB presently supports one FULLTEXT index creation at a time"

ER_INNODB_NO_FT_TEMP_TABLE
  eng "Cannot create FULLTEXT index on temporary InnoDB table"

ER_INNODB_FT_WRONG_DOCID_COLUMN
  eng "Column '%-.192s' is of wrong type for an InnoDB FULLTEXT index"

ER_INNODB_FT_WRONG_DOCID_INDEX
  eng "Index '%-.192s' is of wrong type for an InnoDB FULLTEXT index"

ER_INNODB_ONLINE_LOG_TOO_BIG
  eng "Creating index '%-.192s' required more than 'innodb_online_alter_log_max_size' bytes of modification log. Please try again."

ER_UNKNOWN_ALTER_ALGORITHM
  eng "Unknown ALGORITHM '%s'"

ER_UNKNOWN_ALTER_LOCK
  eng "Unknown LOCK type '%s'"

ER_MTA_CHANGE_SOURCE_CANT_RUN_WITH_GAPS
  eng "CHANGE REPLICATION SOURCE cannot be executed when the replica was stopped with an error or killed in MTA mode. Consider using RESET REPLICA or START REPLICA UNTIL."

ER_MTA_RECOVERY_FAILURE
  eng "Cannot recover after REPLICA errored out in parallel execution mode. Additional error messages can be found in the MySQL error log."

ER_MTA_RESET_WORKERS
  eng "Cannot clean up worker info tables. Additional error messages can be found in the MySQL error log."

ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2
  eng "Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"
  ger "Spaltenanzahl von %s.%s falsch. %d erwartet, aber %d gefunden. Tabelle ist wahrscheinlich beschädigt"

ER_REPLICA_SILENT_RETRY_TRANSACTION
  eng "Replica must silently retry current transaction"

ER_DISCARD_FK_CHECKS_RUNNING
  eng "There is a foreign key check running on table '%-.192s'. Cannot discard the table."

ER_TABLE_SCHEMA_MISMATCH
  eng "Schema mismatch (%s)"

ER_TABLE_IN_SYSTEM_TABLESPACE
  eng "Table '%-.192s' in system tablespace"

ER_IO_READ_ERROR
  eng "IO Read error: (%lu, %s) %s"

ER_IO_WRITE_ERROR
  eng "IO Write error: (%lu, %s) %s"

ER_TABLESPACE_MISSING
  eng "Tablespace is missing for table %s."

ER_TABLESPACE_EXISTS
  eng "Tablespace '%-.192s' exists."

ER_TABLESPACE_DISCARDED
  eng "Tablespace has been discarded for table '%-.192s'"

ER_INTERNAL_ERROR
  eng "Internal error: %s"

ER_INNODB_IMPORT_ERROR
  eng "ALTER TABLE %-.192s IMPORT TABLESPACE failed with error %lu : '%s'"

ER_INNODB_INDEX_CORRUPT
  eng "Index corrupt: %s"

ER_INVALID_YEAR_COLUMN_LENGTH
  eng "Invalid display width. Use YEAR instead."

ER_NOT_VALID_PASSWORD
  eng "Your password does not satisfy the current policy requirements"

ER_MUST_CHANGE_PASSWORD
  eng "You must reset your password using ALTER USER statement before executing this statement."
  bgn "Трябва първо да си смените паролата със SET PASSWORD за да можете да изпълните тази команда"

ER_FK_NO_INDEX_CHILD
        eng "Failed to add the foreign key constraint. Missing index for constraint '%s' in the foreign table '%s'"

ER_FK_NO_INDEX_PARENT
        eng "Failed to add the foreign key constraint. Missing index for constraint '%s' in the referenced table '%s'"

ER_FK_FAIL_ADD_SYSTEM
        eng "Failed to add the foreign key constraint '%s' to system tables"

ER_FK_CANNOT_OPEN_PARENT
        eng "Failed to open the referenced table '%s'"

ER_FK_INCORRECT_OPTION
        eng "Failed to add the foreign key constraint on table '%s'. Incorrect options in FOREIGN KEY constraint '%s'"

ER_FK_DUP_NAME
	eng "Duplicate foreign key constraint name '%s'"

ER_PASSWORD_FORMAT
  eng "The password hash doesn't have the expected format."

ER_FK_COLUMN_CANNOT_DROP
        eng "Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s'"
        ger "Kann Spalte '%-.192s' nicht löschen: wird für eine Fremdschlüsselbeschränkung '%-.192s' benötigt"

ER_FK_COLUMN_CANNOT_DROP_CHILD
        eng "Cannot drop column '%-.192s': needed in a foreign key constraint '%-.192s' of table '%-.192s'"
        ger "Kann Spalte '%-.192s' nicht löschen: wird für eine Fremdschlüsselbeschränkung '%-.192s' der Tabelle '%-.192s' benötigt"

ER_FK_COLUMN_NOT_NULL
        eng "Column '%-.192s' cannot be NOT NULL: needed in a foreign key constraint '%-.192s' SET NULL"
        ger "Spalte '%-.192s' kann nicht NOT NULL sein: wird für eine Fremdschlüsselbeschränkung '%-.192s' SET NULL benötigt"

ER_DUP_INDEX
  eng "Duplicate index '%-.64s' defined on the table '%-.64s.%-.64s'. This is deprecated and will be disallowed in a future release."

ER_FK_COLUMN_CANNOT_CHANGE
  eng "Cannot change column '%-.192s': used in a foreign key constraint '%-.192s'"

ER_FK_COLUMN_CANNOT_CHANGE_CHILD
  eng "Cannot change column '%-.192s': used in a foreign key constraint '%-.192s' of table '%-.192s'"

# No longer used as IGNORE support for ALTER TABLE was removed.
OBSOLETE_ER_UNUSED5
  eng "Cannot delete rows from table which is parent in a foreign key constraint '%-.192s' of table '%-.192s'"

ER_MALFORMED_PACKET
  eng "Malformed communication packet."

ER_READ_ONLY_MODE
        eng "Running in read-only mode"

ER_GTID_NEXT_TYPE_UNDEFINED_GTID
  eng "When @@SESSION.GTID_NEXT is set to a GTID, you must explicitly set it to a different value after a COMMIT or ROLLBACK. Please check GTID_NEXT variable manual page for detailed explanation. Current @@SESSION.GTID_NEXT is '%s'."

ER_VARIABLE_NOT_SETTABLE_IN_SP
  eng "The system variable %.200s cannot be set in stored procedures."

OBSOLETE_ER_CANT_SET_GTID_PURGED_WHEN_GTID_MODE_IS_OFF
  eng "@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON."

ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY
  eng "@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty."

ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY
  eng "@@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients)."

ER_GTID_PURGED_WAS_CHANGED
  eng "@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'."

ER_GTID_EXECUTED_WAS_CHANGED
  eng "@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'."

ER_BINLOG_STMT_MODE_AND_NO_REPL_TABLES
  eng "Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to."

ER_ALTER_OPERATION_NOT_SUPPORTED 0A000
  eng "%s is not supported for this operation. Try %s."

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON 0A000
  eng "%s is not supported. Reason: %s. Try %s."

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY
  eng "COPY algorithm requires a lock"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION
  eng "Partition specific operations do not yet support LOCK/ALGORITHM"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME
  eng "Columns participating in a foreign key are renamed"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE
  eng "Cannot change column type INPLACE"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK
  eng "Adding foreign keys needs foreign_key_checks=OFF"

# No longer used as IGNORE support for ALTER TABLE was removed.
OBSOLETE_ER_UNUSED6
  eng "Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK
  eng "Dropping a primary key is not allowed without also adding a new primary key"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC
  eng "Adding an auto-increment column requires a lock"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS
  eng "Cannot replace hidden FTS_DOC_ID with a user-visible one"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS
  eng "Cannot drop or rename FTS_DOC_ID"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS
  eng "Fulltext index creation requires a lock"

OBSOLETE_ER_SQL_REPLICA_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE
  eng "sql_replica_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON. Instead, for each transaction that you want to skip, generate an empty transaction with the same GTID as the transaction"

ER_DUP_UNKNOWN_IN_INDEX 23000
  cze "Zdvojený klíč (číslo klíče '%-.192s')"
  dan "Flere ens nøgler for indeks '%-.192s'"
  nla "Dubbele ingang voor zoeksleutel '%-.192s'"
  eng "Duplicate entry for key '%-.192s'"
  est "Kattuv väärtus võtmele '%-.192s'"
  fre "Duplicata du champ pour la clef '%-.192s'"
  ger "Doppelter Eintrag für Schlüssel '%-.192s'"
  greek "Διπλή εγγραφή για το κλειδί '%-.192s'"
  hun "Duplikalt bejegyzes a '%-.192s' kulcs szerint."
  ita "Valore duplicato per la chiave '%-.192s'"
  jpn "は索引 '%-.192s' で重複しています。"
  kor "중복된 입력 값: key '%-.192s'"
  nor "Like verdier for nøkkel '%-.192s'"
  norwegian-ny "Like verdiar for nykkel '%-.192s'"
  pol "Powtórzone wystąpienie dla klucza '%-.192s'"
  por "Entrada duplicada para a chave '%-.192s'"
  rum "Cimpul e duplicat pentru cheia '%-.192s'"
  rus "Дублирующаяся запись по ключу '%-.192s'"
  serbian "Dupliran unos za ključ '%-.192s'"
  slo "Opakovaný kľúč (číslo kľúča '%-.192s')"
  spa "Entrada duplicada para la clave '%-.192s'"
  swe "Dublett för nyckel '%-.192s'"
  ukr "Дублюючий запис для ключа '%-.192s'"

ER_IDENT_CAUSES_TOO_LONG_PATH
  eng "Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'."

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL
  eng "cannot silently convert NULL values, as required in this SQL_MODE"

ER_MUST_CHANGE_PASSWORD_LOGIN
  eng "Your password has expired. To log in you must change it using a client that supports expired passwords."
  bgn "Паролата ви е изтекла. За да влезете трябва да я смените използвайки клиент който поддрържа такива пароли."

ER_ROW_IN_WRONG_PARTITION
  eng "Found a row in wrong partition %s"
  swe "Hittade en rad i fel partition %s"

ER_MTA_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX
  eng "Cannot schedule event %s, relay-log name %s, position %s to Worker thread because its size %lu exceeds %lu of replica_pending_jobs_size_max."

OBSOLETE_ER_INNODB_NO_FT_USES_PARSER
  eng "Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table"

ER_BINLOG_LOGICAL_CORRUPTION
  eng "The binary log file '%s' is logically corrupted: %s"

ER_WARN_PURGE_LOG_IN_USE
  eng "file %s was not purged because it was being read by %d thread(s), purged only %d out of %d files."

ER_WARN_PURGE_LOG_IS_ACTIVE
  eng "file %s was not purged because it is the active log file."

ER_AUTO_INCREMENT_CONFLICT
  eng "Auto-increment value in UPDATE conflicts with internally generated values"

WARN_ON_BLOCKHOLE_IN_RBR
  eng "Row events are not logged for %s statements that modify BLACKHOLE tables in row format. Table(s): '%-.192s'"

ER_REPLICA_CM_INIT_REPOSITORY
  eng "Replica failed to initialize connection metadata structure from the repository"

ER_REPLICA_AM_INIT_REPOSITORY
  eng "Replica failed to initialize applier metadata structure from the repository"

ER_ACCESS_DENIED_CHANGE_USER_ERROR 28000
        eng "Access denied trying to change to user '%-.48s'@'%-.64s' (using password: %s). Disconnecting."
        bgn "Отказан достъп при опит за смяна към потребител %-.48s'@'%-.64s' (използвана парола: %s). Затваряне на връзката."

ER_INNODB_READ_ONLY
  eng "InnoDB is in read only mode."

ER_STOP_REPLICA_SQL_THREAD_TIMEOUT
  eng "STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete."

ER_STOP_REPLICA_IO_THREAD_TIMEOUT
  eng "STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete."

ER_TABLE_CORRUPT
  eng "Operation cannot be performed. The table '%-.64s.%-.64s' is missing, corrupt or contains bad data."

ER_TEMP_FILE_WRITE_FAILURE
  eng "Temporary file write failure."

ER_INNODB_FT_AUX_NOT_HEX_ID
  eng "Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index."

ER_OLD_TEMPORALS_UPGRADED
  eng "TIME/TIMESTAMP/DATETIME columns of old format have been upgraded to the new format."

ER_INNODB_FORCED_RECOVERY
  eng "Operation not allowed when innodb_force_recovery > 0."

ER_AES_INVALID_IV
  eng "The initialization vector supplied to %s is too short. Must be at least %d bytes long"
  bgn "Инициализационния вектор подаден на %s е прекалено къс. Трябва да е поне %d байта"

ER_PLUGIN_CANNOT_BE_UNINSTALLED
  eng "Plugin '%s' cannot be uninstalled now. %s"

ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_ASSIGNED_GTID
  eng "Cannot execute statement because it needs to be written to the binary log as multiple statements, and this is not allowed when @@SESSION.GTID_NEXT == 'UUID:NUMBER'."

ER_REPLICA_HAS_MORE_GTIDS_THAN_SOURCE
  eng "Replica has more GTIDs than the source has, using the source's SERVER_UUID. This may indicate that the the last binary log file was truncated or lost, e.g., after a power failure when sync_binlog != 1. The source may have rolled back transactions that were already replicated to the replica. Replicate any transactions that source has rolled back from replica to source, and/or commit empty transactions on source to account for transactions that have been committed on source but are not included in GTID_EXECUTED."

ER_MISSING_KEY
  eng "The table '%s.%s' does not have the necessary key(s) defined on it. Please check the table definition and create index(s) accordingly."

WARN_NAMED_PIPE_ACCESS_EVERYONE
  eng "Setting named_pipe_full_access_group='%s' is insecure. Consider using a Windows group with fewer members."

#
#  End of 5.6 error messages (server-to-client).
#

################################################################################
# Error numbers 2000 to 2999 are reserved for the client libraries (for
# errors generated at the client side). Please do not use them for errors
# generated in the server. See the FAQ at the end of this file for further
# information!
################################################################################

reserved-error-section 2000 2999

################################################################################
# Error numbers starting at 3000: server-to-client messages 5.7
################################################################################

start-error-number 3000

ER_FILE_CORRUPT
  eng "File %s is corrupted"

ER_ERROR_ON_SOURCE
  eng "Query partially completed on the source (error on source: %d) and was aborted. There is a chance that your source is inconsistent at this point. If you are sure that your source is ok, run this query manually on the replica and then restart the replica with SET GLOBAL SQL_REPLICA_SKIP_COUNTER=1; START REPLICA;. Query:'%s'"

OBSOLETE_ER_INCONSISTENT_ERROR
  eng "Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'"

ER_STORAGE_ENGINE_NOT_LOADED
        eng "Storage engine for table '%s'.'%s' is not loaded."

ER_GET_STACKED_DA_WITHOUT_ACTIVE_HANDLER 0Z002
  eng "GET STACKED DIAGNOSTICS when handler not active"

ER_WARN_LEGACY_SYNTAX_CONVERTED
  eng "%s is no longer supported. The statement was converted to %s."

ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN
  eng "Statement is unsafe because it uses a fulltext parser plugin which may not return the same value on the replica."

ER_CANNOT_DISCARD_TEMPORARY_TABLE
  eng "Cannot DISCARD/IMPORT tablespace associated with temporary table"

ER_FK_DEPTH_EXCEEDED
  eng "Foreign key cascade delete/update exceeds max depth of %d."

ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2
        eng "The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure."
        ger "Spaltenanzahl von %s.%s falsch. %d erwartet, aber %d erhalten. Erzeugt mit MySQL %d, jetzt unter %d. Bitte verwenden Sie die MySQL-Upgrade-Prozedur, um den Fehler zu beheben."

ER_WARN_TRIGGER_DOESNT_HAVE_CREATED
  eng "Trigger %s.%s.%s does not have CREATED attribute."

ER_REFERENCED_TRG_DOES_NOT_EXIST
  eng "Referenced trigger '%s' for the given action time and event type does not exist."

ER_EXPLAIN_NOT_SUPPORTED
        eng "EXPLAIN FOR CONNECTION command is supported only for SELECT/UPDATE/INSERT/DELETE/REPLACE"
ER_INVALID_FIELD_SIZE
        eng "Invalid size for column '%-.192s'."

ER_MISSING_HA_CREATE_OPTION
        eng "Table storage engine '%-.64s' found required create option missing"

ER_ENGINE_OUT_OF_MEMORY
  eng "Out of memory in storage engine '%-.64s'."

ER_PASSWORD_EXPIRE_ANONYMOUS_USER
  eng "The password for anonymous user cannot be expired."

ER_REPLICA_SQL_THREAD_MUST_STOP
  eng "This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD first"

ER_NO_FT_MATERIALIZED_SUBQUERY
  eng "Cannot create FULLTEXT index on materialized subquery"

ER_INNODB_UNDO_LOG_FULL
  eng "Undo Log error: %s"

ER_INVALID_ARGUMENT_FOR_LOGARITHM 2201E
  eng "Invalid argument for logarithm"

ER_REPLICA_CHANNEL_IO_THREAD_MUST_STOP
  eng "This operation cannot be performed with a running replica io thread; run STOP REPLICA IO_THREAD FOR CHANNEL '%s' first."

ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO
  eng "This operation may not be safe when the replica has temporary tables. The tables will be kept open until the server restarts or until the tables are deleted by any replicated DROP statement. Suggest to wait until replica_open_temp_tables = 0."

ER_WARN_ONLY_SOURCE_LOG_FILE_NO_POS
  eng "CHANGE REPLICATION SOURCE TO with a SOURCE_LOG_FILE clause but no SOURCE_LOG_POS clause may not be safe. The old position value may not be valid for the new binary log file."

ER_QUERY_TIMEOUT
  eng "Query execution was interrupted, maximum statement execution time exceeded"

ER_NON_RO_SELECT_DISABLE_TIMER
  eng "Select is not a read only statement, disabling timer"

ER_DUP_LIST_ENTRY
  eng "Duplicate entry '%-.192s'."

OBSOLETE_ER_SQL_MODE_NO_EFFECT
  eng "'%s' mode no longer has any effect. Use STRICT_ALL_TABLES or STRICT_TRANS_TABLES instead."

ER_AGGREGATE_ORDER_FOR_UNION
  eng "Expression #%u of ORDER BY contains aggregate function and applies to a UNION, EXCEPT or INTERSECT"

ER_AGGREGATE_ORDER_NON_AGG_QUERY
  eng "Expression #%u of ORDER BY contains aggregate function and applies to the result of a non-aggregated query"

ER_REPLICA_WORKER_STOPPED_PREVIOUS_THD_ERROR
  eng "Replica worker has stopped after at least one previous worker encountered an error when replica-preserve-commit-order was enabled. To preserve commit order, the last transaction executed by this thread has not been committed. When restarting the replica after fixing any failed threads, you should fix this worker as well."

ER_DONT_SUPPORT_REPLICA_PRESERVE_COMMIT_ORDER
  eng "replica_preserve_commit_order is not supported %s."

ER_SERVER_OFFLINE_MODE
  eng "The server is currently in offline mode"

ER_GIS_DIFFERENT_SRIDS
  eng "Binary geometry function %s given two geometries of different srids: %u and %u, which should have been identical."

ER_GIS_UNSUPPORTED_ARGUMENT
  eng "Calling geometry function %s with unsupported types of arguments."

ER_GIS_UNKNOWN_ERROR
  eng "Unknown GIS error occurred in function %s."

ER_GIS_UNKNOWN_EXCEPTION
  eng "Unknown exception caught in GIS function %s."

ER_GIS_INVALID_DATA 22023
  eng "Invalid GIS data provided to function %s."

ER_BOOST_GEOMETRY_EMPTY_INPUT_EXCEPTION
  eng "The geometry has no data in function %s."

ER_BOOST_GEOMETRY_CENTROID_EXCEPTION
  eng "Unable to calculate centroid because geometry is empty in function %s."

ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION
  eng "Geometry overlay calculation error: geometry data is invalid in function %s."

ER_BOOST_GEOMETRY_TURN_INFO_EXCEPTION
  eng "Geometry turn info calculation error: geometry data is invalid in function %s."

ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION
  eng "Analysis procedures of intersection points interrupted unexpectedly in function %s."

ER_BOOST_GEOMETRY_UNKNOWN_EXCEPTION
  eng "Unknown exception thrown in function %s."

ER_STD_BAD_ALLOC_ERROR
  eng "Memory allocation error: %-.256s in function %s."

ER_STD_DOMAIN_ERROR
  eng "Domain error: %-.256s in function %s."

ER_STD_LENGTH_ERROR
  eng "Length error: %-.256s in function %s."

ER_STD_INVALID_ARGUMENT
  eng "Invalid argument error: %-.256s in function %s."

ER_STD_OUT_OF_RANGE_ERROR
  eng "Out of range error: %-.256s in function %s."

ER_STD_OVERFLOW_ERROR
  eng "Overflow error: %-.256s in function %s."

ER_STD_RANGE_ERROR
  eng "Range error: %-.256s in function %s."

ER_STD_UNDERFLOW_ERROR
  eng "Underflow error: %-.256s in function %s."

ER_STD_LOGIC_ERROR
  eng "Logic error: %-.256s in function %s."

ER_STD_RUNTIME_ERROR
  eng "Runtime error: %-.256s in function %s."

ER_STD_UNKNOWN_EXCEPTION
  eng "Unknown exception: %-.384s in function %s."

ER_GIS_DATA_WRONG_ENDIANESS
  eng "Geometry byte string must be little endian."

ER_CHANGE_SOURCE_PASSWORD_LENGTH
  eng "The password provided for the replication user exceeds the maximum length of 32 characters"

ER_USER_LOCK_WRONG_NAME 42000
  eng "Incorrect user-level lock name '%-.192s'. The name is empty, NULL, or can not be expressed in the current character-set."

# Should be different from ER_LOCK_DEADLOCK since it doesn't cause implicit
# rollback. Should not be mapped to SQLSTATE 40001 for the same reason.
ER_USER_LOCK_DEADLOCK
  eng "Deadlock found when trying to get user-level lock; try rolling back transaction/releasing locks and restarting lock acquisition."

ER_REPLACE_INACCESSIBLE_ROWS
  eng "REPLACE cannot be executed as it requires deleting rows that are not in the view"

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_GIS
  eng "Do not support online operation on table with GIS index"

ER_ILLEGAL_USER_VAR 42000 S1009
  eng "User variable name '%-.100s' is illegal"

ER_GTID_MODE_OFF
  eng "Cannot %s when GTID_MODE = OFF."

OBSOLETE_ER_UNSUPPORTED_BY_REPLICATION_THREAD
  eng "Cannot %s from a replica thread."

ER_INCORRECT_TYPE
  eng "Incorrect type for argument %s in function %s."

ER_FIELD_IN_ORDER_NOT_SELECT
  eng "Expression #%u of ORDER BY clause is not in SELECT list, references column '%-.192s' which is not in SELECT list; this is incompatible with %s"

ER_AGGREGATE_IN_ORDER_NOT_SELECT
  eng "Expression #%u of ORDER BY clause is not in SELECT list, contains aggregate function; this is incompatible with %s"

ER_INVALID_RPL_WILD_TABLE_FILTER_PATTERN
  eng "Supplied filter list contains a value which is not in the required format 'db_pattern.table_pattern'"

ER_NET_OK_PACKET_TOO_LARGE 08S01
  eng "OK packet too large"

ER_INVALID_JSON_DATA
  eng "Invalid JSON data provided to function %s: %s"

ER_INVALID_GEOJSON_MISSING_MEMBER
  eng "Invalid GeoJSON data provided to function %s: Missing required member '%s'"

ER_INVALID_GEOJSON_WRONG_TYPE
  eng "Invalid GeoJSON data provided to function %s: Member '%s' must be of type '%s'"

ER_INVALID_GEOJSON_UNSPECIFIED
  eng "Invalid GeoJSON data provided to function %s"

ER_DIMENSION_UNSUPPORTED
  eng "Unsupported number of coordinate dimensions in function %s: Found %u, expected %u"

ER_REPLICA_CHANNEL_DOES_NOT_EXIST
  eng "Replica channel '%s' does not exist."

OBSOLETE_ER_SLAVE_MULTIPLE_CHANNELS_HOST_PORT
  eng "A replica channel '%s' already exists for the given host and port combination."

ER_REPLICA_CHANNEL_NAME_INVALID_OR_TOO_LONG
  eng "Couldn't create channel: Channel name is either invalid or too long."

ER_REPLICA_NEW_CHANNEL_WRONG_REPOSITORY
  eng "To have multiple channels, repository cannot be of type FILE; Please check the repository configuration and convert them to TABLE."

OBSOLETE_ER_SLAVE_CHANNEL_DELETE
   eng "Cannot delete replica info objects for channel '%s'."

ER_REPLICA_MULTIPLE_CHANNELS_CMD
   eng "Multiple channels exist on the replica. Please provide channel name as an argument."

ER_REPLICA_MAX_CHANNELS_EXCEEDED
   eng "Maximum number of replication channels allowed exceeded."

ER_REPLICA_CHANNEL_MUST_STOP
   eng "This operation cannot be performed with running replication threads; run STOP REPLICA FOR CHANNEL '%s' first"

ER_REPLICA_CHANNEL_NOT_RUNNING
   eng "This operation requires running replication threads; configure replica and run START REPLICA FOR CHANNEL '%s'"

ER_REPLICA_CHANNEL_WAS_RUNNING
   eng "Replication thread(s) for channel '%s' are already runnning."

ER_REPLICA_CHANNEL_WAS_NOT_RUNNING
  eng "Replication thread(s) for channel '%s' are already stopped."

ER_REPLICA_CHANNEL_SQL_THREAD_MUST_STOP
  eng "This operation cannot be performed with a running replica sql thread; run STOP REPLICA SQL_THREAD FOR CHANNEL '%s' first."

ER_REPLICA_CHANNEL_SQL_SKIP_COUNTER
  eng "When sql_replica_skip_counter > 0, it is not allowed to start more than one SQL thread by using 'START REPLICA [SQL_THREAD]'. Value of sql_replica_skip_counter can only be used by one SQL thread at a time. Please use 'START REPLICA [SQL_THREAD] FOR CHANNEL' to start the SQL thread which will use the value of sql_replica_skip_counter."

# When using this error message, use the ER_WRONG_FIELD_WITH_GROUP error code.
ER_WRONG_FIELD_WITH_GROUP_V2
  eng "Expression #%u of %s is not in GROUP BY clause and contains nonaggregated column '%-.192s' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by"

# When using this error message, use the ER_MIX_OF_GROUP_FUNC_AND_FIELDS error code.
ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2
  eng "In aggregated query without GROUP BY, expression #%u of %s contains nonaggregated column '%-.192s'; this is incompatible with sql_mode=only_full_group_by"

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_SYSVAR_UPDATE
  eng "Updating '%s' is deprecated. It will be made read-only in a future release."

# Use this error message to deprecate SQL MODES
ER_WARN_DEPRECATED_SQLMODE
  eng "Changing sql mode '%s' is deprecated. It will be removed in a future release."

ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID
  eng "DROP DATABASE failed; some tables may have been dropped but the database directory remains. The GTID has not been added to GTID_EXECUTED and the statement was not written to the binary log. Fix this as follows: (1) remove all files from the database directory %-.192s; (2) SET GTID_NEXT='%-.192s'; (3) DROP DATABASE `%-.192s`."

ER_GROUP_REPLICATION_CONFIGURATION
  eng "The server is not configured properly to be an active member of the group. Please see more details on error log."

ER_GROUP_REPLICATION_RUNNING
  eng "The START GROUP_REPLICATION command failed since the group is already running."

ER_GROUP_REPLICATION_APPLIER_INIT_ERROR
  eng "The START GROUP_REPLICATION command failed as the applier module failed to start."

ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT
  eng "The STOP GROUP_REPLICATION command execution is incomplete: The applier thread got the stop signal while it was busy. The applier thread will stop once the current task is complete."

ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR
  eng "The START GROUP_REPLICATION command failed as there was an error when initializing the group communication layer."

ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR
  eng "The START GROUP_REPLICATION command failed as there was an error when joining the communication group."

ER_BEFORE_DML_VALIDATION_ERROR
  eng "The table does not comply with the requirements by an external plugin."

ER_PREVENTS_VARIABLE_WITHOUT_RBR
  eng "Cannot change the value of variable %s without binary log format as ROW."

ER_RUN_HOOK_ERROR
  eng "Error on observer while running replication hook '%s'."

ER_TRANSACTION_ROLLBACK_DURING_COMMIT 40000
  eng "Plugin instructed the server to rollback the current transaction."

ER_GENERATED_COLUMN_FUNCTION_IS_NOT_ALLOWED
  eng "Expression of generated column '%s' contains a disallowed function."

ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN
  eng "INPLACE ADD or DROP of virtual columns cannot be combined with other ALTER TABLE actions"

ER_WRONG_FK_OPTION_FOR_GENERATED_COLUMN
  eng "Cannot define foreign key with %s clause on a generated column."

ER_NON_DEFAULT_VALUE_FOR_GENERATED_COLUMN
  eng "The value specified for generated column '%s' in table '%s' is not allowed."

ER_UNSUPPORTED_ACTION_ON_GENERATED_COLUMN
  eng "'%s' is not supported for generated columns."

ER_GENERATED_COLUMN_NON_PRIOR
  eng "Generated column can refer only to generated columns defined prior to it."

ER_DEPENDENT_BY_GENERATED_COLUMN
  eng "Column '%s' has a generated column dependency."

ER_GENERATED_COLUMN_REF_AUTO_INC
  eng "Generated column '%s' cannot refer to auto-increment column."

ER_FEATURE_NOT_AVAILABLE
  eng "The '%-.64s' feature is not available; you need to remove '%-.64s' or use MySQL built with '%-.64s'"

ER_CANT_SET_GTID_MODE
  eng "SET @@GLOBAL.GTID_MODE = %-.64s is not allowed because %-.384s."

ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF
  eng "The replication receiver thread%-.192s cannot start in AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF."

OBSOLETE_ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION
  eng "Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.512s, position %lld."

OBSOLETE_ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON
  eng "Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.512s, position %lld."

OBSOLETE_ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF
  eng "Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.512s, position %lld."

ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX
  eng "Cannot set ENFORCE_GTID_CONSISTENCY = ON because there are ongoing transactions that violate GTID consistency."

ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX
  eng "There are ongoing transactions that violate GTID consistency."

ER_ACCOUNT_HAS_BEEN_LOCKED
  eng "Access denied for user '%-.48s'@'%-.64s'. Account is locked."
  pol "Odmowa dostępu dla użytkownika '%-.48s'@'%-.64s'. Konto zablokowane."

ER_WRONG_TABLESPACE_NAME 42000
  eng "Incorrect tablespace name `%-.192s`"

ER_TABLESPACE_IS_NOT_EMPTY
  eng "Tablespace `%-.192s` is not empty."

ER_WRONG_FILE_NAME
  eng "Incorrect File Name '%s'."

ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION
  eng "Inconsistent intersection points."

ER_WARN_OPTIMIZER_HINT_SYNTAX_ERROR
  eng "Optimizer hint syntax error"

ER_WARN_BAD_MAX_EXECUTION_TIME
  eng "Unsupported MAX_EXECUTION_TIME"

ER_WARN_UNSUPPORTED_MAX_EXECUTION_TIME
  eng "MAX_EXECUTION_TIME hint is supported by top-level standalone SELECT statements only"

ER_WARN_CONFLICTING_HINT
  eng "Hint %s is ignored as conflicting/duplicated"

ER_WARN_UNKNOWN_QB_NAME
  eng "Query block name %s is not found for %s hint"

ER_UNRESOLVED_HINT_NAME
  eng "Unresolved name %s for %s hint"

ER_WARN_ON_MODIFYING_GTID_EXECUTED_TABLE
  eng "Please do not modify the %s table. This is a mysql internal system table to store GTIDs for committed transactions. Modifying it can lead to an inconsistent GTID state."

ER_PLUGGABLE_PROTOCOL_COMMAND_NOT_SUPPORTED
  eng "Command not supported by pluggable protocols"

ER_LOCKING_SERVICE_WRONG_NAME 42000
  eng "Incorrect locking service lock name '%-.192s'."

# Should be different from ER_LOCK_DEADLOCK since it doesn't cause implicit
# rollback. Should not be mapped to SQLSTATE 40001 for the same reason.
ER_LOCKING_SERVICE_DEADLOCK
  eng "Deadlock found when trying to get locking service lock; try releasing locks and restarting lock acquisition."

ER_LOCKING_SERVICE_TIMEOUT
  eng "Service lock wait timeout exceeded."

ER_GIS_MAX_POINTS_IN_GEOMETRY_OVERFLOWED
  eng "Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s."

ER_SQL_MODE_MERGED
  eng "'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release."

ER_VTOKEN_PLUGIN_TOKEN_MISMATCH
  eng "Version token mismatch for %.*s. Correct value %.*s"
  bgn "Клеймото за версия %.*s не съвпада. Правилната стойност е %.*s"

ER_VTOKEN_PLUGIN_TOKEN_NOT_FOUND
  eng "Version token %.*s not found."
  bgn "Не е намерено клеймо за версия %.*s"

ER_CANT_SET_VARIABLE_WHEN_OWNING_GTID
  eng "Variable %-.192s cannot be changed by a client that owns a GTID. The client owns %s. Ownership is released on COMMIT or ROLLBACK."

ER_REPLICA_CHANNEL_OPERATION_NOT_ALLOWED
   eng "%-.192s cannot be performed on channel '%-.192s'."

ER_INVALID_JSON_TEXT 22032
  eng "Invalid JSON text: \"%s\" at position %u in value for column '%-.200s'."

# The last parameter is now always empty but kept for backward compatibility
ER_INVALID_JSON_TEXT_IN_PARAM 22032
  eng "Invalid JSON text in argument %u to function %s: \"%s\" at position %u.%-.0s"

ER_INVALID_JSON_BINARY_DATA
  eng "The JSON binary value contains invalid data."

ER_INVALID_JSON_PATH 42000
  eng "Invalid JSON path expression. The error is around character position %u.%-.200s"

ER_INVALID_JSON_CHARSET 22032
  eng "Cannot create a JSON value from a string with CHARACTER SET '%s'."

ER_INVALID_JSON_CHARSET_IN_FUNCTION 22032
  eng "Invalid JSON character data provided to function %s: '%s'; utf8 is required."

ER_INVALID_TYPE_FOR_JSON 22032
  eng "Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required."

ER_INVALID_CAST_TO_JSON 22032
  eng "Cannot CAST value to JSON."

ER_INVALID_JSON_PATH_CHARSET 42000
  eng "A path expression must be encoded in the utf8 character set. The path expression '%-.200s' is encoded in character set '%-.200s'."

ER_INVALID_JSON_PATH_WILDCARD 42000
  eng "In this situation, path expressions may not contain the * and ** tokens or an array range."

ER_JSON_VALUE_TOO_BIG 22032
  eng "The JSON value is too big to be stored in a JSON column."

ER_JSON_KEY_TOO_BIG 22032
  eng "The JSON object contains a key name that is too long."

ER_JSON_USED_AS_KEY 42000
  eng "JSON column '%-.192s' supports indexing only via generated columns on a specified JSON path."

ER_JSON_VACUOUS_PATH 42000
  eng "The path expression '$' is not allowed in this context."

ER_JSON_BAD_ONE_OR_ALL_ARG 42000
  eng "The oneOrAll argument to %s may take these values: 'one' or 'all'."

# The second parameter is now always empty but kept for backward compatibility
ER_NUMERIC_JSON_VALUE_OUT_OF_RANGE 22003
  eng "Out of range JSON value for CAST to %s%-.0s from column %s at row %ld"

# The second parameter is now always empty but kept for backward compatibility
ER_INVALID_JSON_VALUE_FOR_CAST 22018
  eng "Invalid JSON value for CAST to %s%-.0s from column %s at row %ld"

ER_JSON_DOCUMENT_TOO_DEEP 22032
  eng "The JSON document exceeds the maximum depth."

ER_JSON_DOCUMENT_NULL_KEY 22032
  eng "JSON documents may not contain NULL member names."

ER_SECURE_TRANSPORT_REQUIRED
  eng "Connections using insecure transport are prohibited while --require_secure_transport=ON."

ER_NO_SECURE_TRANSPORTS_CONFIGURED
  eng "No secure transports (SSL or Shared Memory) are configured, unable to set --require_secure_transport=ON."

ER_DISABLED_STORAGE_ENGINE
  eng "Storage engine %s is disabled (Table creation is disallowed)."

ER_USER_DOES_NOT_EXIST
  eng "Authorization ID %s does not exist."

ER_USER_ALREADY_EXISTS
  eng "Authorization ID %s already exists."

ER_AUDIT_API_ABORT
  eng "Aborted by Audit API ('%-.48s';%d)."

ER_INVALID_JSON_PATH_ARRAY_CELL 42000
  eng "A path expression is not a path to a cell in an array."

ER_BUFPOOL_RESIZE_INPROGRESS
  eng "Another buffer pool resize is already in progress."

ER_FEATURE_DISABLED_SEE_DOC
  eng "The '%s' feature is disabled; see the documentation for '%s'"

ER_SERVER_ISNT_AVAILABLE
  eng "Server isn't available"

ER_SESSION_WAS_KILLED
  eng "Session was killed"

ER_CAPACITY_EXCEEDED
  eng "Memory capacity of %llu bytes for '%s' exceeded. %s"

ER_CAPACITY_EXCEEDED_IN_RANGE_OPTIMIZER
  eng "Range optimization was not done for this query."

# This error code is needed only for 5.7, not used in 8.0+
OBSOLETE_ER_TABLE_NEEDS_UPG_PART
  eng "Partitioning upgrade required. Please dump/reload to fix it or do: ALTER TABLE `%-.192s`.`%-.192s` UPGRADE PARTITIONING"

ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID
  eng "The client holds ownership of the GTID %s. Therefore, WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID."

ER_CANNOT_ADD_FOREIGN_BASE_COL_VIRTUAL
  eng "Cannot add foreign key on the base column of indexed virtual column."

ER_CANNOT_CREATE_VIRTUAL_INDEX_CONSTRAINT
  eng "Cannot create index on virtual column whose base column has foreign constraint."

ER_ERROR_ON_MODIFYING_GTID_EXECUTED_TABLE
  eng "Please do not modify the %s table with an XA transaction. This is an internal system table used to store GTIDs for committed transactions. Although modifying it can lead to an inconsistent GTID state, if necessary you can modify it with a non-XA transaction."

ER_LOCK_REFUSED_BY_ENGINE
  eng "Lock acquisition refused by storage engine."

ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN
  eng "ADD COLUMN col...VIRTUAL, ADD INDEX(col)"

ER_MASTER_KEY_ROTATION_NOT_SUPPORTED_BY_SE
  eng "Master key rotation is not supported by storage engine."

OBSOLETE_ER_MASTER_KEY_ROTATION_ERROR_BY_SE
  eng "Encryption key rotation error reported by SE: %s"

ER_MASTER_KEY_ROTATION_BINLOG_FAILED
  eng "Write to binlog failed. However, master key rotation has been completed successfully."

ER_MASTER_KEY_ROTATION_SE_UNAVAILABLE
  eng "Storage engine is not available."

ER_TABLESPACE_CANNOT_ENCRYPT
  eng "This tablespace can't be encrypted."

ER_INVALID_ENCRYPTION_OPTION
  eng "Invalid encryption option."

ER_CANNOT_FIND_KEY_IN_KEYRING
  eng "Can't find master key from keyring, please check in the server log if a keyring is loaded and initialized successfully."

ER_CAPACITY_EXCEEDED_IN_PARSER
  eng "Parser bailed out for this query."

ER_UNSUPPORTED_ALTER_ENCRYPTION_INPLACE
  eng "Cannot alter encryption attribute by inplace algorithm."

ER_KEYRING_UDF_KEYRING_SERVICE_ERROR
  eng "Function '%s' failed because underlying keyring service returned an error. Please check if a keyring is installed and that provided arguments are valid for the keyring you are using."

ER_USER_COLUMN_OLD_LENGTH
  eng "It seems that your db schema is old. The %s column is 77 characters long and should be 93 characters long. Please perform the MySQL upgrade procedure."

ER_CANT_RESET_SOURCE
  eng "RESET SOURCE is not allowed because %-.384s."

ER_GROUP_REPLICATION_MAX_GROUP_SIZE
  eng "The START GROUP_REPLICATION command failed since the group already has 9 members."

ER_CANNOT_ADD_FOREIGN_BASE_COL_STORED
  eng "Cannot add foreign key on the base column of stored column. "

ER_TABLE_REFERENCED
  eng "Cannot complete the operation because table is referenced by another connection."

OBSOLETE_ER_PARTITION_ENGINE_DEPRECATED_FOR_TABLE
  eng "The partition engine, used by table '%-.192s.%-.192s', is deprecated and will be removed in a future release. Please use native partitioning instead."

OBSOLETE_ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID_ZERO 01000
  eng "%.192s(geometry) is deprecated and will be replaced by st_srid(geometry, 0) in a future version. Use %.192s(st_aswkb(geometry), 0) instead."

OBSOLETE_ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID 01000
  eng "%.192s(geometry, srid) is deprecated and will be replaced by st_srid(geometry, srid) in a future version. Use %.192s(st_aswkb(geometry), srid) instead."

ER_XA_RETRY
  eng "The resource manager is not able to commit the transaction branch at this time. Please retry later."

ER_KEYRING_AWS_UDF_AWS_KMS_ERROR
  eng "Function %s failed due to: %s."

ER_BINLOG_UNSAFE_XA
  eng "Statement is unsafe because it is being used inside a XA transaction. Concurrent XA transactions may deadlock on replicas when replicated using statements."

ER_UDF_ERROR
  eng "%s UDF failed; %s"

ER_KEYRING_MIGRATION_FAILURE
  eng "Can not perform keyring migration : %s"

ER_KEYRING_ACCESS_DENIED_ERROR 42000
  eng "Access denied; you need %-.128s privileges for this operation"

ER_KEYRING_MIGRATION_STATUS
  eng "Keyring migration %s."

OBSOLETE_ER_PLUGIN_FAILED_TO_OPEN_TABLES
  eng "Failed to open the %s filter tables."

OBSOLETE_ER_PLUGIN_FAILED_TO_OPEN_TABLE
  eng "Failed to open '%s.%s' %s table."

OBSOLETE_ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED
  eng "No keyring plugin installed."

OBSOLETE_ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET
  eng "Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one."

OBSOLETE_ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY
  eng "Could not create AES key. OpenSSL's EVP_BytesToKey function failed."

OBSOLETE_ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED
  eng "Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption."

OBSOLETE_ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED
  eng "Audit Log filtering has not been installed."

OBSOLETE_ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE
  eng "Request ignored for '%s'@'%s'. SUPER privilege or AUDIT_ADMIN role needed to perform operation"

OBSOLETE_ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED
  eng "SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user."

OBSOLETE_ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS
  eng "Could not reinitialize audit log filters."

OBSOLETE_ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE
  eng "Invalid argument type"

OBSOLETE_ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT
  eng "Invalid argument count"

OBSOLETE_ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED
  eng "audit_log plugin has not been installed using INSTALL PLUGIN syntax."

OBSOLETE_ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE
  eng "Invalid \"max_array_length\" argument type."

ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_VALUE
  eng "Invalid \"max_array_length\" argument value."

OBSOLETE_ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR
  eng "%s"

OBSOLETE_ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY
  eng "Filter name cannot be empty."

OBSOLETE_ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY
  eng "User cannot be empty."

OBSOLETE_ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXISTS
  eng "Specified filter has not been found."

OBSOLETE_ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC
  eng "First character of the user name must be alphanumeric."

OBSOLETE_ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER
  eng "Invalid character in the user name."

OBSOLETE_ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER
  eng "Invalid character in the host name."

OBSOLETE_WARN_DEPRECATED_MAXDB_SQL_MODE_FOR_TIMESTAMP
  eng "With the MAXDB SQL mode enabled, TIMESTAMP is identical with DATETIME. The MAXDB SQL mode is deprecated and will be removed in a future release. Please disable the MAXDB SQL mode and use DATETIME instead."

OBSOLETE_ER_XA_REPLICATION_FILTERS
  eng "The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica."

OBSOLETE_ER_CANT_OPEN_ERROR_LOG
  eng "Could not open file '%s' for error logging%s%s"

OBSOLETE_ER_GROUPING_ON_TIMESTAMP_IN_DST
  eng "Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query."

OBSOLETE_ER_CANT_START_SERVER_NAMED_PIPE
  eng "Can't start server : Named Pipe \"%s\" already in use."

ER_WRITE_SET_EXCEEDS_LIMIT
  eng "The size of writeset data for the current transaction exceeds a limit imposed by an external component. If using Group Replication check 'group_replication_transaction_size_limit'."

# Created in 8.0: ER_DEPRECATED_TLS_VERSION_SESSION (13745)
# Back ported in 5.7: ER_DEPRECATED_TLS_VERSION_SESSION (3232)
# Obsolete in 8.0: OBSOLETE_ER_DEPRECATED_TLS_VERSION_SESSION (13745)
# Reserved in 8.0: OBSOLETE_ER_DEPRECATED_TLS_VERSION_SESSION_57 (3232)
# This error was never used in 8.0,
# this entry is to preserve error numbering for 5.7 -> 8.0 merges.
OBSOLETE_ER_DEPRECATED_TLS_VERSION_SESSION_57
  eng "Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`"

# Created in 8.0: ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL_CLI (4038)
# Created in 8.0: ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL (13746)
# Back ported in 5.7: ER_WARN_DEPRECATED_TLS_VERSION (3233)
# Obsolete in 8.0: OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL_CLI (4038)
# Obsolete in 8.0: OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL (13746)
# Reserved in 8.0: OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_57 (3233)
# This error was never used in 8.0,
# this entry is to preserve error numbering for 5.7 -> 8.0 merges.
OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_57
  eng "A deprecated TLS version %s is enabled. Please use TLSv1.2 or higher."

# In 5.7: ER_WARN_WRONG_NATIVE_TABLE_STRUCTURE
# Not used in 8.0
OBSOLETE_ER_WARN_WRONG_NATIVE_TABLE_STRUCTURE
  eng "Optional native table '%-.64s'.'%-.64s' has the wrong structure or is missing."

ER_AES_INVALID_KDF_NAME
  eng "KDF method name is not valid. Please use hkdf or pbkdf2_hmac method name"

ER_AES_INVALID_KDF_ITERATIONS
  eng "For KDF method pbkdf2_hmac iterations value less than 1000 or more than 65535 is not allowed due to security reasons. Please provide iterations >= 1000 and iterations < 65535"

WARN_AES_KEY_SIZE
  eng "AES key size should be %d bytes length or secure KDF methods hkdf or pbkdf2_hmac should be used, please provide exact AES key size or use KDF methods for better security."

ER_AES_INVALID_KDF_OPTION_SIZE
  eng "KDF option size is invalid, please provide valid size < %d bytes and not NULL"

#
#  End of 5.7 error messages (server-to-client).
#

################################################################################
# Error numbers starting at 3500: server-to-client messages 8.0
################################################################################

# Do NOT add messages intended for the error log here;
# they have their own section below.
#
# See the FAQ at the end of the file for more information.

start-error-number 3500

ER_UNSUPPORT_COMPRESSED_TEMPORARY_TABLE
  eng "CREATE TEMPORARY TABLE is not allowed with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE."

ER_ACL_OPERATION_FAILED
  eng "The ACL operation failed due to the following error from SE: errcode %d - %.256s"

ER_UNSUPPORTED_INDEX_ALGORITHM
  eng "This storage engine does not support the %s index algorithm, storage engine default was used instead."

ER_NO_SUCH_DB 42Y07
  eng "Database '%-.192s' doesn't exist"

ER_TOO_BIG_ENUM
  eng "Too many enumeration values for column %.192s."

ER_TOO_LONG_SET_ENUM_VALUE
  eng "Too long enumeration/set value for column %.192s."

ER_INVALID_DD_OBJECT
  eng "%s dictionary object is invalid. (%.192s)"

ER_UPDATING_DD_TABLE
  eng "Failed to update %.192s dictionary object."

ER_INVALID_DD_OBJECT_ID
  eng "Dictionary object id (%lu) does not exist."

ER_INVALID_DD_OBJECT_NAME
  eng "Dictionary object name '%s' is invalid. (%.192s)"

ER_TABLESPACE_MISSING_WITH_NAME
   eng "Tablespace %-.192s doesn't exist."

ER_TOO_LONG_ROUTINE_COMMENT
  eng "Comment for routine '%-.64s' is too long (max = %lu)"

ER_SP_LOAD_FAILED
  eng "Failed to load routine '%-.64s'."

ER_INVALID_BITWISE_OPERANDS_SIZE
  eng "Binary operands of bitwise operators must be of equal length"

ER_INVALID_BITWISE_AGGREGATE_OPERANDS_SIZE
  eng "Aggregate bitwise functions cannot accept arguments longer than 511 bytes; consider using the SUBSTRING() function"

ER_WARN_UNSUPPORTED_HINT
  eng "Hints aren't supported in %s"

ER_UNEXPECTED_GEOMETRY_TYPE 22S01
  eng "%.64s value is a geometry of unexpected type %.64s in %.64s."

ER_SRS_PARSE_ERROR SR002
  eng "Can't parse the spatial reference system definition of SRID %u."

ER_SRS_PROJ_PARAMETER_MISSING SR003
  eng "The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter."

ER_WARN_SRS_NOT_FOUND 01000
  eng "There's no spatial reference system with SRID %u."

ER_SRS_NOT_CARTESIAN 22S00
  eng "Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian."

ER_SRS_NOT_CARTESIAN_UNDEFINED SR001
  eng "Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined."

ER_PK_INDEX_CANT_BE_INVISIBLE
  eng "A primary key index cannot be invisible"

ER_UNKNOWN_AUTHID
  eng "Unknown authorization ID `%.64s`@`%.64s`"

ER_FAILED_ROLE_GRANT
  eng "Failed to grant %.90s` to %.90s"

ER_OPEN_ROLE_TABLES
  eng "Failed to open the security system tables"

ER_FAILED_DEFAULT_ROLES
  eng "Failed to set default roles"

ER_COMPONENTS_NO_SCHEME
  eng "Cannot find schema in specified URN: '%.192s'."
  pol "Nie można znaleźć rodzaju zasobu w podanym URN: '%.192s'."

ER_COMPONENTS_NO_SCHEME_SERVICE
  eng "Cannot acquire scheme load service implementation for schema '%.192s' in specified URN: '%.192s'."
  pol "Nie można znaleźć implementacji usługi ładującej rodzaj zasobu dla zasobu '%.192s' w podanym URN: '%.192s'."

ER_COMPONENTS_CANT_LOAD
  eng "Cannot load component from specified URN: '%.192s'."
  pol "Nie można wczytać komponentu pod podanym URN: '%.192s'."

ER_ROLE_NOT_GRANTED
  eng "`%.64s`@`%.64s` is not granted to `%.64s`@`%.64s`"

ER_FAILED_REVOKE_ROLE
  eng "Could not revoke role from `%.64s`@`%.64s`"

ER_RENAME_ROLE
  eng  "Renaming of a role identifier is forbidden"

ER_COMPONENTS_CANT_ACQUIRE_SERVICE_IMPLEMENTATION
  eng "Cannot acquire specified service implementation: '%.192s'."
  pol "Nie można pozyskać podanej implementacji usługi: '%.192s'."

ER_COMPONENTS_CANT_SATISFY_DEPENDENCY
  eng "Cannot satisfy dependency for service '%.192s' required by component '%.192s'."
  pol "Nie można spełnić zależności w postaci usługi '%.192s' wymaganej przez komponent '%.192s'."

ER_COMPONENTS_LOAD_CANT_REGISTER_SERVICE_IMPLEMENTATION
  eng "Cannot register service implementation '%.192s' provided by component '%.192s'."
  pol "Nie można wpisać implementacji usługi '%.192s' dostarczanej przez komponent '%.192s'."

ER_COMPONENTS_LOAD_CANT_INITIALIZE
  eng "Initialization method provided by component '%.192s' failed."
  pol "Metoda inicjalizująca dostarczona przez komponent '%.192s' nie zakończyła się z powodzeniem."

ER_COMPONENTS_UNLOAD_NOT_LOADED
  eng "Component specified by URN '%.192s' to unload has not been loaded before."
  pol "Komponent podany do odłączenia przez URN '%.192s' nie był wcześniej załadowany."

ER_COMPONENTS_UNLOAD_CANT_DEINITIALIZE
  eng "De-initialization method provided by component '%.192s' failed."
  pol "Metoda de-inicjalizująca dostarczona przez komponent '%.192s' nie zakończyła się z powodzeniem."

ER_COMPONENTS_CANT_RELEASE_SERVICE
  eng "Release of previously acquired service implementation failed."
  pol "Zwolnienie wcześniej pozyskanej implementacji usługi nie powiodło się."

ER_COMPONENTS_UNLOAD_CANT_UNREGISTER_SERVICE
  eng "Unregistration of service implementation '%.192s' provided by component '%.192s' failed during unloading of the component."
  pol "Wyrejstrowanie implementacji usługi '%.192s' dostarczonej przez komponent '%.192s' wykonywane podczas odłączania komponentu nie zakończyła się z powodzeniem."

ER_COMPONENTS_CANT_UNLOAD
  eng "Cannot unload component from specified URN: '%.192s'."
  pol "Nie można odłączyć komponentu pod podanym URN: '%.192s'."

ER_WARN_UNLOAD_THE_NOT_PERSISTED
  eng "The Persistent Dynamic Loader was used to unload a component '%.192s', but it was not used to load that component before."
  pol "Persistent Dynamic Loader został użyty do odłączenia komponentu '%.192s', który nie był przez niego wcześniej wczytany."

ER_COMPONENT_TABLE_INCORRECT
  eng "The mysql.component table is missing or has an incorrect definition."
  pol "Tabela mysql.component nie istnieje lub ma nieodpowiednią definicję."

ER_COMPONENT_MANIPULATE_ROW_FAILED
  eng "Failed to manipulate component '%.192s' persistence data. Error code %d from storage engine."

ER_COMPONENTS_UNLOAD_DUPLICATE_IN_GROUP
  eng "The component with specified URN: '%.192s' was specified in group more than once."
  pol "Komponent z podanym URN: '%.192s' został podany w grupie więcej niż raz."

ER_CANT_SET_GTID_PURGED_DUE_SETS_CONSTRAINTS
  eng "@@GLOBAL.GTID_PURGED cannot be changed: %s"

ER_CANNOT_LOCK_USER_MANAGEMENT_CACHES
  eng "Can not lock user management caches for processing."

ER_SRS_NOT_FOUND SR001
  eng "There's no spatial reference system with SRID %u."

ER_VARIABLE_NOT_PERSISTED
  eng "Variables cannot be persisted. Please retry."

ER_IS_QUERY_INVALID_CLAUSE
  eng "Information schema queries do not support the '%s' clause."

ER_UNABLE_TO_STORE_STATISTICS
  eng "Unable to store dynamic %s statistics into data dictionary."

ER_NO_SYSTEM_SCHEMA_ACCESS
  eng "Access to system schema '%.64s' is rejected."

ER_NO_SYSTEM_TABLESPACE_ACCESS
  eng "Access to system tablespace '%.64s' is rejected."

ER_NO_SYSTEM_TABLE_ACCESS
  eng "Access to %.64s '%.64s.%.64s' is rejected."

ER_NO_SYSTEM_TABLE_ACCESS_FOR_DICTIONARY_TABLE
  eng "data dictionary table"

ER_NO_SYSTEM_TABLE_ACCESS_FOR_SYSTEM_TABLE
  eng "system table"

ER_NO_SYSTEM_TABLE_ACCESS_FOR_TABLE
  eng "table"

ER_INVALID_OPTION_KEY 22023
  eng "Invalid option key '%.192s' in function %.192s."

ER_INVALID_OPTION_VALUE 22023
  eng "Invalid value '%.192s' for option '%.192s' in function '%.192s'."

ER_INVALID_OPTION_KEY_VALUE_PAIR 22023
  eng "The string '%.192s' is not a valid key %c value pair in function %.192s."

ER_INVALID_OPTION_START_CHARACTER 22023
  eng "The options argument in function %.192s starts with the invalid character '%c'."
ER_INVALID_OPTION_END_CHARACTER 22023
  eng "The options argument in function %.192s ends with the invalid character '%c'."

ER_INVALID_OPTION_CHARACTERS 22023
  eng "The options argument in function %.192s contains the invalid character sequence '%.192s'."

ER_DUPLICATE_OPTION_KEY 22023
  eng "Duplicate option key '%.192s' in funtion '%.192s'."

ER_WARN_SRS_NOT_FOUND_AXIS_ORDER 01000
  eng "There's no spatial reference system with SRID %u. The axis order is unknown."

ER_NO_ACCESS_TO_NATIVE_FCT
  eng "Access to native function '%.64s' is rejected."

ER_RESET_SOURCE_TO_VALUE_OUT_OF_RANGE
  eng "The requested value '%llu' for the next binary log index is out of range. Please use a value between '1' and '%lu'."

ER_UNRESOLVED_TABLE_LOCK
  eng "Unresolved table name %s in locking clause."

ER_DUPLICATE_TABLE_LOCK
  eng "Table %s appears in multiple locking clauses."

ER_BINLOG_UNSAFE_SKIP_LOCKED
  eng "Statement is unsafe because it uses SKIP LOCKED. The set of inserted values is non-deterministic."
ER_BINLOG_UNSAFE_NOWAIT
  eng "Statement is unsafe because it uses NOWAIT. Whether the command will succeed or fail is not deterministic."

ER_LOCK_NOWAIT
  eng "Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set."

ER_CTE_RECURSIVE_REQUIRES_UNION
  eng "Recursive Common Table Expression '%s' should contain a UNION"

ER_CTE_RECURSIVE_REQUIRES_NONRECURSIVE_FIRST
  eng "Recursive Common Table Expression '%s' should have one or more non-recursive query blocks followed by one or more recursive ones"

ER_CTE_RECURSIVE_FORBIDS_AGGREGATION
  eng "Recursive Common Table Expression '%s' can contain neither aggregation nor window functions in recursive query block"

ER_CTE_RECURSIVE_FORBIDDEN_JOIN_ORDER
  eng "In recursive query block of Recursive Common Table Expression '%s', the recursive table must neither be in the right argument of a LEFT JOIN, nor be forced to be non-first with join order hints"

ER_CTE_RECURSIVE_REQUIRES_SINGLE_REFERENCE
  eng "In recursive query block of Recursive Common Table Expression '%s', the recursive table must be referenced only once, and not in any subquery"

ER_SWITCH_TMP_ENGINE
  eng "'%s' requires @@internal_tmp_disk_storage_engine=InnoDB"

ER_WINDOW_NO_SUCH_WINDOW
  eng "Window name '%s' is not defined."

ER_WINDOW_CIRCULARITY_IN_WINDOW_GRAPH
  eng "There is a circularity in the window dependency graph."

ER_WINDOW_NO_CHILD_PARTITIONING
  eng "A window which depends on another cannot define partitioning."

ER_WINDOW_NO_INHERIT_FRAME
  eng "Window '%s' has a frame definition, so cannot be referenced by another window."

ER_WINDOW_NO_REDEFINE_ORDER_BY
  eng "Window '%s' cannot inherit '%s' since both contain an ORDER BY clause."

ER_WINDOW_FRAME_START_ILLEGAL
  eng "Window '%s': frame start cannot be UNBOUNDED FOLLOWING."

ER_WINDOW_FRAME_END_ILLEGAL
  eng "Window '%s': frame end cannot be UNBOUNDED PRECEDING."

ER_WINDOW_FRAME_ILLEGAL
  eng "Window '%s': frame start or end is negative, NULL or of non-integral type"

ER_WINDOW_RANGE_FRAME_ORDER_TYPE
  eng "Window '%s' with RANGE N PRECEDING/FOLLOWING frame requires exactly one ORDER BY expression, of numeric or temporal type"

ER_WINDOW_RANGE_FRAME_TEMPORAL_TYPE
  eng "Window '%s' with RANGE frame has ORDER BY expression of datetime type. Only INTERVAL bound value allowed."

ER_WINDOW_RANGE_FRAME_NUMERIC_TYPE
  eng "Window '%s' with RANGE frame has ORDER BY expression of numeric type, INTERVAL bound value not allowed."

ER_WINDOW_RANGE_BOUND_NOT_CONSTANT
  eng "Window '%s' has a non-constant frame bound."

ER_WINDOW_DUPLICATE_NAME
  eng "Window '%s' is defined twice."

ER_WINDOW_ILLEGAL_ORDER_BY
  eng "Window '%s': ORDER BY or PARTITION BY uses legacy position indication which is not supported, use expression."

ER_WINDOW_INVALID_WINDOW_FUNC_USE
  eng "You cannot use the window function '%s' in this context.'"

ER_WINDOW_INVALID_WINDOW_FUNC_ALIAS_USE
  eng "You cannot use the alias '%s' of an expression containing a window function in this context.'"

ER_WINDOW_NESTED_WINDOW_FUNC_USE_IN_WINDOW_SPEC
  eng "You cannot nest a window function in the specification of window '%s'."

ER_WINDOW_ROWS_INTERVAL_USE
  eng "Window '%s': INTERVAL can only be used with RANGE frames."

ER_WINDOW_NO_GROUP_ORDER_UNUSED
  eng "ASC or DESC with GROUP BY isn't allowed with window functions; put ASC or DESC in ORDER BY"

ER_WINDOW_EXPLAIN_JSON
  eng "To get information about window functions use EXPLAIN FORMAT=JSON"

ER_WINDOW_FUNCTION_IGNORES_FRAME
  eng "Window function '%s' ignores the frame clause of window '%s' and aggregates over the whole partition"

ER_WL9236_NOW_UNUSED
  eng "Windowing requires @@internal_tmp_mem_storage_engine=TempTable."

ER_INVALID_NO_OF_ARGS
  eng "Too many arguments for function %s: %lu; maximum allowed is %s."

ER_FIELD_IN_GROUPING_NOT_GROUP_BY
  eng "Argument #%u of GROUPING function is not in GROUP BY"

ER_TOO_LONG_TABLESPACE_COMMENT
  eng "Comment for tablespace '%-.64s' is too long (max = %lu)"

ER_ENGINE_CANT_DROP_TABLE
  eng "Storage engine can't drop table '%-.129s'"

ER_ENGINE_CANT_DROP_MISSING_TABLE
  eng "Storage engine can't drop table '%-.129s' because it is missing. Use DROP TABLE IF EXISTS to remove it from data-dictionary."

ER_TABLESPACE_DUP_FILENAME
  eng "Duplicate file name for tablespace '%-.64s'"

ER_DB_DROP_RMDIR2
  eng "Problem while dropping database. Can't remove database directory (%s). Please remove it manually."

ER_IMP_NO_FILES_MATCHED
  eng "No SDI files matched the pattern '%s'"

ER_IMP_SCHEMA_DOES_NOT_EXIST
  eng "Schema '%.256s', referenced in SDI, does not exist."

ER_IMP_TABLE_ALREADY_EXISTS
  eng "Table '%.256s.%.256s', referenced in SDI, already exists."

ER_IMP_INCOMPATIBLE_MYSQLD_VERSION
  eng "Imported mysqld_version (%llu) is not compatible with current (%llu)"

ER_IMP_INCOMPATIBLE_DD_VERSION
  eng "Imported dd version (%u) is not compatible with current (%u)"

ER_IMP_INCOMPATIBLE_SDI_VERSION
  eng "Imported sdi version (%llu) is not compatible with current (%llu)"

ER_WARN_INVALID_HINT
  eng "Invalid number of arguments for hint %s"

ER_VAR_DOES_NOT_EXIST
  eng "Variable %s does not exist in persisted config file"

ER_LONGITUDE_OUT_OF_RANGE 22S02
  eng "Longitude %f is out of range in function %.192s. It must be within (%f, %f]."

ER_LATITUDE_OUT_OF_RANGE 22S03
  eng "Latitude %f is out of range in function %.192s. It must be within [%f, %f]."

ER_NOT_IMPLEMENTED_FOR_GEOGRAPHIC_SRS 22S00
  eng "%.192s(%.80s) has not been implemented for geographic spatial reference systems."

ER_ILLEGAL_PRIVILEGE_LEVEL
  eng "Illegal privilege level specified for %s"

ER_NO_SYSTEM_VIEW_ACCESS
  eng "Access to system view INFORMATION_SCHEMA.'%.64s' is rejected."

ER_COMPONENT_FILTER_FLABBERGASTED
  eng "The log-filter component \"%s\" got confused at \"%s\" ..."
  ger "Der Logfilter \"%s\" wunderte sich ueber \"%s\" ..."

ER_PART_EXPR_TOO_LONG
  eng "Partitioning expression is too long."

ER_UDF_DROP_DYNAMICALLY_REGISTERED
  eng "DROP FUNCTION can't drop a dynamically registered user defined function"

ER_UNABLE_TO_STORE_COLUMN_STATISTICS
  eng "Unable to store column statistics for column '%.64s' in table '%.64s'.'%.64s'"

ER_UNABLE_TO_UPDATE_COLUMN_STATISTICS
  eng "Unable to update column statistics for column '%.64s' in table '%.64s'.'%.64s'"

ER_UNABLE_TO_DROP_COLUMN_STATISTICS
  eng "Unable to remove column statistics for column '%.64s' in table '%.64s'.'%.64s'"

ER_UNABLE_TO_BUILD_HISTOGRAM
  eng "Unable to build histogram statistics for column '%.64s' in table '%.64s'.'%.64s'"

ER_MANDATORY_ROLE
  eng "The role %s is a mandatory role and can't be revoked or dropped. The restriction can be lifted by excluding the role identifier from the global variable mandatory_roles."

ER_MISSING_TABLESPACE_FILE
  eng "Tablespace '%.192s' does not have a file named '%.192s'"

ER_PERSIST_ONLY_ACCESS_DENIED_ERROR 42000
  eng "Access denied; you need %-.128s privileges for this operation"

ER_CMD_NEED_SUPER
  eng "You need the SUPER privilege for command '%-.192s'"

ER_PATH_IN_DATADIR
  eng "Path is within the current data directory '%-.192s'"

ER_CLONE_DDL_IN_PROGRESS
  eng "Concurrent DDL is performed during clone operation. Please try again."

ER_CLONE_TOO_MANY_CONCURRENT_CLONES
  eng "Too many concurrent clone operations. Maximum allowed - %d."

ER_APPLIER_LOG_EVENT_VALIDATION_ERROR
  eng "The table in transaction %s does not comply with the requirements by an external plugin."

ER_CTE_MAX_RECURSION_DEPTH
  eng "Recursive query aborted after %u iterations. Try increasing @@cte_max_recursion_depth to a larger value."

ER_NOT_HINT_UPDATABLE_VARIABLE
  eng "Variable %s cannot be set using SET_VAR hint."

ER_CREDENTIALS_CONTRADICT_TO_HISTORY
  eng "Cannot use these credentials for '%.*s@%.*s' because they contradict the password history policy"

ER_WARNING_PASSWORD_HISTORY_CLAUSES_VOID
  eng "Non-zero password history clauses ignored for user '%s'@'%s' as its authentication plugin %s does not support password history"

ER_CLIENT_DOES_NOT_SUPPORT
  eng "The client doesn't support %s"

ER_I_S_SKIPPED_TABLESPACE
  eng "Tablespace '%s' was skipped since its definition is being modified by concurrent DDL statement"

ER_TABLESPACE_ENGINE_MISMATCH
  eng "Engine '%.192s' does not match stored engine '%.192s' for tablespace '%.192s'"

ER_WRONG_SRID_FOR_COLUMN
  eng "The SRID of the geometry does not match the SRID of the column '%.64s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column."

ER_CANNOT_ALTER_SRID_DUE_TO_INDEX
  eng "The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification."

ER_WARN_BINLOG_PARTIAL_UPDATES_DISABLED
  eng "When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log."

ER_WARN_BINLOG_V1_ROW_EVENTS_DISABLED
  eng "When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log."

ER_WARN_BINLOG_PARTIAL_UPDATES_SUGGESTS_PARTIAL_IMAGES
  eng "When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%."

ER_COULD_NOT_APPLY_JSON_DIFF
  eng "Could not apply JSON diff in table %.*s, column %s."

ER_CORRUPTED_JSON_DIFF
  eng "Corrupted JSON diff for table %.*s, column %s."

ER_RESOURCE_GROUP_EXISTS
  eng "Resource Group '%-.192s' exists"

ER_RESOURCE_GROUP_NOT_EXISTS
  eng "Resource Group '%-.192s' does not exist."

ER_INVALID_VCPU_ID
  eng "Invalid cpu id %u"

ER_INVALID_VCPU_RANGE
  eng "Invalid VCPU range %u-%u"

ER_INVALID_THREAD_PRIORITY
  eng "Invalid thread priority value %d for %s resource group %s. Allowed range is [%d, %d]."

ER_DISALLOWED_OPERATION
  eng "%s operation is disallowed on %s"

ER_RESOURCE_GROUP_BUSY
  eng "Resource group %s is busy."

ER_RESOURCE_GROUP_DISABLED
  eng "Resource group %s is disabled."

ER_FEATURE_UNSUPPORTED
  eng "Feature %s is unsupported (%s)."

ER_ATTRIBUTE_IGNORED
  eng "Attribute %s is ignored (%s)."

ER_INVALID_THREAD_ID
  eng "Invalid thread id (%llu)."

ER_RESOURCE_GROUP_BIND_FAILED
  eng "Unable to bind resource group %s with thread id (%llu).(%s)."

ER_INVALID_USE_OF_FORCE_OPTION
  eng "Option FORCE invalid as DISABLE option is not specified."

ER_GROUP_REPLICATION_COMMAND_FAILURE
  eng "The %s command encountered a failure. %s"

ER_SDI_OPERATION_FAILED
  eng "Failed to %s SDI '%.192s.%.192s' in tablespace '%.192s'."

ER_MISSING_JSON_TABLE_VALUE 22035
  eng "Missing value for JSON_TABLE column '%.192s'"

ER_WRONG_JSON_TABLE_VALUE 2203F
  eng "Can't store an array or an object in the scalar JSON_TABLE column '%.192s'"

ER_TF_MUST_HAVE_ALIAS 42000
        eng "Every table function must have an alias"

ER_TF_FORBIDDEN_JOIN_TYPE
  eng "INNER or LEFT JOIN must be used for LATERAL references made by '%.192s'"

ER_JT_VALUE_OUT_OF_RANGE 22003
  eng "Value is out of range for JSON_TABLE's column '%.192s'"

ER_JT_MAX_NESTED_PATH 42000
  eng "More than supported %u NESTED PATHs were found in JSON_TABLE '%.192s'"

ER_PASSWORD_EXPIRATION_NOT_SUPPORTED_BY_AUTH_METHOD
  eng "The selected authentication method %.*s does not support password expiration"
  bgn "Избрания метод за удостоверяване %.*s не поддържа изтичане на пароли"

ER_INVALID_GEOJSON_CRS_NOT_TOP_LEVEL
  eng "Invalid GeoJSON data provided to function %s: Member 'crs' must be specified in the top level object."

ER_BAD_NULL_ERROR_NOT_IGNORED 23000
  eng "Column '%-.192s' cannot be null"

WARN_USELESS_SPATIAL_INDEX
  eng "The spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column."

ER_DISK_FULL_NOWAIT
  eng "Create table/tablespace '%-.192s' failed, as disk is full"

ER_PARSE_ERROR_IN_DIGEST_FN
  eng "Could not parse argument to digest function: \"%s\"."

ER_UNDISCLOSED_PARSE_ERROR_IN_DIGEST_FN
  eng "Could not parse argument to digest function."

ER_SCHEMA_DIR_EXISTS
  eng "Schema directory '%.192s' already exists. This must be resolved manually (e.g. by moving the schema directory to another location)."

ER_SCHEMA_DIR_MISSING
  eng "Schema directory '%.192s' does not exist"

ER_SCHEMA_DIR_CREATE_FAILED
  eng "Failed to create schema directory '%.192s' (errno: %d - %s)"

ER_SCHEMA_DIR_UNKNOWN
  eng "Schema '%.192s' does not exist, but schema directory '%.192s' was found. This must be resolved manually (e.g. by moving the schema directory to another location)."

ER_ONLY_IMPLEMENTED_FOR_SRID_0_AND_4326 22S00
  eng "Function %.192s is only defined for SRID 0 and SRID 4326."

ER_BINLOG_EXPIRE_LOG_DAYS_AND_SECS_USED_TOGETHER
  eng "The option expire_logs_days and binlog_expire_logs_seconds cannot be used together. Please use binlog_expire_logs_seconds to set the expire time (expire_logs_days is deprecated)"

#
# Regular expression errors. None of these should take any arguments.
# We strive to keep this list in the same order as in UErrorCode
# common/unicode/utypes.h.
#

ER_REGEXP_BUFFER_OVERFLOW
  eng "The result string is larger than the result buffer."

ER_REGEXP_ILLEGAL_ARGUMENT
  eng "Illegal argument to a regular expression."

ER_REGEXP_INDEX_OUTOFBOUNDS_ERROR
  eng "Index out of bounds in regular expression search."

ER_REGEXP_INTERNAL_ERROR
  eng "Internal error in the regular expression library."

ER_REGEXP_RULE_SYNTAX
  eng "Syntax error in regular expression on line %u, character %u."

ER_REGEXP_BAD_ESCAPE_SEQUENCE
  eng "Unrecognized escape sequence in regular expression."

ER_REGEXP_UNIMPLEMENTED
  eng "The regular expression contains a feature that is not implemented in this library version."

ER_REGEXP_MISMATCHED_PAREN
  eng "Mismatched parenthesis in regular expression."

ER_REGEXP_BAD_INTERVAL
  eng "Incorrect description of a {min,max} interval."

ER_REGEXP_MAX_LT_MIN
  eng "The maximum is less than the minumum in a {min,max} interval."

ER_REGEXP_INVALID_BACK_REF
  eng "Invalid back-reference in regular expression."

ER_REGEXP_LOOK_BEHIND_LIMIT
  eng "The look-behind assertion exceeds the limit in regular expression."

ER_REGEXP_MISSING_CLOSE_BRACKET
  eng "The regular expression contains an unclosed bracket expression."

ER_REGEXP_INVALID_RANGE
  eng "The regular expression contains an [x-y] character range where x comes after y."

ER_REGEXP_STACK_OVERFLOW
  eng "Overflow in the regular expression backtrack stack."

ER_REGEXP_TIME_OUT
  eng "Timeout exceeded in regular expression match."

ER_REGEXP_PATTERN_TOO_BIG
  eng "The regular expression pattern exceeds limits on size or complexity."

ER_CANT_SET_ERROR_LOG_SERVICE
  eng "Value for %s got confusing at or around \"%s\". Syntax may be wrong, component may not be INSTALLed, or a component that does not support instances may be listed more than once."

ER_EMPTY_PIPELINE_FOR_ERROR_LOG_SERVICE
  eng "Setting an empty %s pipeline disables error logging!"

# could use verbatim, but we want an error-code
ER_COMPONENT_FILTER_DIAGNOSTICS
  eng "filter %s: %s"

ER_NOT_IMPLEMENTED_FOR_CARTESIAN_SRS 22S00
  eng "%.192s(%.80s) has not been implemented for Cartesian spatial reference systems."

ER_NOT_IMPLEMENTED_FOR_PROJECTED_SRS 22S00
  eng "%.192s(%.80s) has not been implemented for projected spatial reference systems."

ER_NONPOSITIVE_RADIUS 22003
  eng "Invalid radius provided to function %s: Radius must be greater than zero."

ER_RESTART_SERVER_FAILED
  eng "Restart server failed (%s)."

ER_SRS_MISSING_MANDATORY_ATTRIBUTE SR006
  eng "Missing mandatory attribute %s."

ER_SRS_MULTIPLE_ATTRIBUTE_DEFINITIONS SR006
  eng "Multiple definitions of attribute %s."

ER_SRS_NAME_CANT_BE_EMPTY_OR_WHITESPACE SR006
  eng "The spatial reference system name can't be an empty string or start or end with whitespace."

ER_SRS_ORGANIZATION_CANT_BE_EMPTY_OR_WHITESPACE SR006
  eng "The organization name can't be an empty string or start or end with whitespace."

ER_SRS_ID_ALREADY_EXISTS SR004
  eng "There is already a spatial reference system with SRID %u."

ER_WARN_SRS_ID_ALREADY_EXISTS 01S00
  eng "There is already a spatial reference system with SRID %u."

ER_CANT_MODIFY_SRID_0 SR000
  eng "SRID 0 is not modifiable."

ER_WARN_RESERVED_SRID_RANGE 01S01
  eng "The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade."

ER_CANT_MODIFY_SRS_USED_BY_COLUMN SR005
  eng "Can't modify SRID %u. There is at least one column depending on it."

ER_SRS_INVALID_CHARACTER_IN_ATTRIBUTE SR006
  eng "Invalid character in attribute %s."

ER_SRS_ATTRIBUTE_STRING_TOO_LONG SR006
  eng "Attribute %s is too long. The maximum length is %u characters."

ER_DEPRECATED_UTF8_ALIAS
  eng "'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous."

ER_DEPRECATED_NATIONAL
  eng "NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous."

ER_INVALID_DEFAULT_UTF8MB4_COLLATION
  eng "Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected"

ER_UNABLE_TO_COLLECT_LOG_STATUS
  eng "Unable to collect information for column '%-.192s': %-.192s."

ER_RESERVED_TABLESPACE_NAME
  eng "The table '%-.192s' may not be created in the reserved tablespace '%-.192s'."

ER_UNABLE_TO_SET_OPTION
  eng "This option cannot be set %s."

ER_REPLICA_POSSIBLY_DIVERGED_AFTER_DDL
  eng "A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding."

ER_SRS_NOT_GEOGRAPHIC 22S00
  eng "Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic."

ER_POLYGON_TOO_LARGE 22023
  eng "Function %s encountered a polygon that was too large. Polygons must cover less than half the planet."

ER_SPATIAL_UNIQUE_INDEX
  eng "Spatial indexes can't be primary or unique indexes."

ER_INDEX_TYPE_NOT_SUPPORTED_FOR_SPATIAL_INDEX
  eng "The index type %.20s is not supported for spatial indexes."

ER_FK_CANNOT_DROP_PARENT
  eng "Cannot drop table '%s' referenced by a foreign key constraint '%s' on table '%s'."

ER_GEOMETRY_PARAM_LONGITUDE_OUT_OF_RANGE 22S02
  eng "A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f]."

ER_GEOMETRY_PARAM_LATITUDE_OUT_OF_RANGE 22S03
  eng "A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f]."

ER_FK_CANNOT_USE_VIRTUAL_COLUMN
  eng "Foreign key '%s' uses virtual column '%s' which is not supported."

ER_FK_NO_COLUMN_PARENT
  eng "Failed to add the foreign key constraint. Missing column '%s' for constraint '%s' in the referenced table '%s'"

ER_CANT_SET_ERROR_SUPPRESSION_LIST
  eng "%s: Could not add suppression rule for code \"%s\". Rule-set may be full, or code may not correspond to an error-log message."

ER_SRS_GEOGCS_INVALID_AXES SR002
  eng "The spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST."

ER_SRS_INVALID_SEMI_MAJOR_AXIS SR002
  eng "The length of the semi-major axis must be a positive number."

ER_SRS_INVALID_INVERSE_FLATTENING SR002
  eng "The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere."

ER_SRS_INVALID_ANGULAR_UNIT SR002
  eng "The angular unit conversion factor must be a positive number."

ER_SRS_INVALID_PRIME_MERIDIAN SR002
  eng "The prime meridian must be within (-180, 180] degrees, specified in the SRS angular unit."

ER_TRANSFORM_SOURCE_SRS_NOT_SUPPORTED 22S00
  eng "Transformation from SRID %u is not supported."

ER_TRANSFORM_TARGET_SRS_NOT_SUPPORTED 22S00
  eng "Transformation to SRID %u is not supported."

ER_TRANSFORM_SOURCE_SRS_MISSING_TOWGS84 22S00
  eng "Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause."

ER_TRANSFORM_TARGET_SRS_MISSING_TOWGS84 22S00
  eng "Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause."

ER_TEMP_TABLE_PREVENTS_SWITCH_SESSION_BINLOG_FORMAT
  eng "Changing @@session.binlog_format is disallowed when the session has open temporary table(s). You could wait until these temporary table(s) are dropped and try again."

ER_TEMP_TABLE_PREVENTS_SWITCH_GLOBAL_BINLOG_FORMAT
  eng "Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel has open temporary table(s). You could wait until Replica_open_temp_tables = 0 and try again"

ER_RUNNING_APPLIER_PREVENTS_SWITCH_GLOBAL_BINLOG_FORMAT
  eng "Changing @@global.binlog_format or @@persist.binlog_format is disallowed when any replication channel applier thread is running. You could execute STOP REPLICA SQL_THREAD and try again."

ER_CLIENT_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR
  eng "Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT."

OBSOLETE_ER_XA_CANT_CREATE_MDL_BACKUP
  eng "XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect."

ER_TABLE_WITHOUT_PK
  eng "Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting."

ER_WARN_DATA_TRUNCATED_FUNCTIONAL_INDEX 01000
  eng "Data truncated for functional index '%s' at row %ld"

ER_WARN_DATA_OUT_OF_RANGE_FUNCTIONAL_INDEX 22003
  eng "Value is out of range for functional index '%s' at row %ld"

ER_FUNCTIONAL_INDEX_ON_JSON_OR_GEOMETRY_FUNCTION 42000
  eng "Cannot create a functional index on a function that returns a JSON or GEOMETRY value."

ER_FUNCTIONAL_INDEX_REF_AUTO_INCREMENT
  eng "Functional index '%.64s' cannot refer to an auto-increment column."

ER_CANNOT_DROP_COLUMN_FUNCTIONAL_INDEX
  eng "Cannot drop column '%-.64s' because it is used by a functional index. In order to drop the column, you must remove the functional index."

ER_FUNCTIONAL_INDEX_PRIMARY_KEY
  eng "The primary key cannot be a functional index"

ER_FUNCTIONAL_INDEX_ON_LOB
  eng "Cannot create a functional index on an expression that returns a BLOB or TEXT. Please consider using CAST."

ER_FUNCTIONAL_INDEX_FUNCTION_IS_NOT_ALLOWED
  eng "Expression of functional index '%s' contains a disallowed function."

ER_FULLTEXT_FUNCTIONAL_INDEX
  eng "Fulltext functional index is not supported."

ER_SPATIAL_FUNCTIONAL_INDEX
  eng "Spatial functional index is not supported."

ER_WRONG_KEY_COLUMN_FUNCTIONAL_INDEX
  eng "The used storage engine cannot index the expression '%s'."

ER_FUNCTIONAL_INDEX_ON_FIELD
  eng "Functional index on a column is not supported. Consider using a regular index instead."

ER_GENERATED_COLUMN_NAMED_FUNCTION_IS_NOT_ALLOWED
  eng "Expression of generated column '%s' contains a disallowed function: %s."

ER_GENERATED_COLUMN_ROW_VALUE
  eng "Expression of generated column '%s' cannot refer to a row value."

ER_GENERATED_COLUMN_VARIABLES
  eng "Expression of generated column '%s' cannot refer user or system variables."

ER_DEPENDENT_BY_DEFAULT_GENERATED_VALUE
  eng "Column '%s' of table '%s' has a default value expression dependency and cannot be dropped or renamed."

ER_DEFAULT_VAL_GENERATED_NON_PRIOR
  eng "Default value expression of column '%s' cannot refer to a column defined after it if that column is a generated column or has an expression as default value."

ER_DEFAULT_VAL_GENERATED_REF_AUTO_INC
  eng "Default value expression of column '%s' cannot refer to an auto-increment column."

ER_DEFAULT_VAL_GENERATED_FUNCTION_IS_NOT_ALLOWED
  eng "Default value expression of column '%s' contains a disallowed function."

ER_DEFAULT_VAL_GENERATED_NAMED_FUNCTION_IS_NOT_ALLOWED
  eng "Default value expression of column '%s' contains a disallowed function: %s."

ER_DEFAULT_VAL_GENERATED_ROW_VALUE
  eng "Default value expression of column '%s' cannot refer to a row value."

ER_DEFAULT_VAL_GENERATED_VARIABLES
  eng "Default value expression of column '%s' cannot refer user or system variables."

ER_DEFAULT_AS_VAL_GENERATED
  eng "DEFAULT function cannot be used with default value expressions"

ER_UNSUPPORTED_ACTION_ON_DEFAULT_VAL_GENERATED
  eng "'%s' is not supported for default value expressions."

ER_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION
  eng "Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT."

ER_FK_CANNOT_CHANGE_ENGINE
  eng "Cannot change table's storage engine because the table participates in a foreign key constraint."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
ER_WARN_DEPRECATED_USER_SET_EXPR
  eng "Setting user variables within expressions is deprecated and will be removed in a future release. Consider alternatives: 'SET variable=expression, ...', or 'SELECT expression(s) INTO variables(s)'."

ER_WARN_DEPRECATED_UTF8MB3_COLLATION
  eng "'%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_NESTED_COMMENT_SYNTAX
  eng "Nested comment syntax is deprecated and will be removed in a future release."

ER_FK_INCOMPATIBLE_COLUMNS
  eng "Referencing column '%s' and referenced column '%s' in foreign key constraint '%s' are incompatible."

ER_GR_HOLD_WAIT_TIMEOUT
  eng "Timeout exceeded for held statement while new Group Replication primary member is applying backlog."

ER_GR_HOLD_KILLED
  eng "Held statement aborted because Group Replication plugin got shut down or thread was killed while new primary member was applying backlog."

ER_GR_HOLD_MEMBER_STATUS_ERROR
  eng "Held statement was aborted due to member being in error state, while backlog is being applied during Group Replication primary election."

ER_RPL_ENCRYPTION_FAILED_TO_FETCH_KEY
  eng "Failed to fetch key from keyring, please check if keyring is loaded."

ER_RPL_ENCRYPTION_KEY_NOT_FOUND
  eng "Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully."

ER_RPL_ENCRYPTION_KEYRING_INVALID_KEY
  eng "Fetched an invalid key from keyring."

ER_RPL_ENCRYPTION_HEADER_ERROR
  eng "Error reading a replication log encryption header: %s."

ER_RPL_ENCRYPTION_FAILED_TO_ROTATE_LOGS
  eng "Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually."

ER_RPL_ENCRYPTION_KEY_EXISTS_UNEXPECTED
  eng "Key %s exists unexpected."

ER_RPL_ENCRYPTION_FAILED_TO_GENERATE_KEY
  eng "Failed to generate key, please check if keyring is loaded."

ER_RPL_ENCRYPTION_FAILED_TO_STORE_KEY
  eng "Failed to store key, please check if keyring is loaded."

ER_RPL_ENCRYPTION_FAILED_TO_REMOVE_KEY
  eng "Failed to remove key, please check if keyring is loaded."

ER_RPL_ENCRYPTION_UNABLE_TO_CHANGE_OPTION
  eng "Failed to change binlog_encryption value. %-.80s."

ER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED
  eng "Unable to recover binlog encryption master key, please check if keyring is loaded."

ER_SLOW_LOG_MODE_IGNORED_WHEN_NOT_LOGGING_TO_FILE
  eng "slow query log file format changed as requested, but setting will have no effect when not actually logging to a file."

ER_GRP_TRX_CONSISTENCY_NOT_ALLOWED
  eng "The option group_replication_consistency cannot be used on the current member state."

ER_GRP_TRX_CONSISTENCY_BEFORE
  eng "Error while waiting for group transactions commit on group_replication_consistency= 'BEFORE'."

ER_GRP_TRX_CONSISTENCY_AFTER_ON_TRX_BEGIN
  eng "Error while waiting for transactions with group_replication_consistency= 'AFTER' to commit."

ER_GRP_TRX_CONSISTENCY_BEGIN_NOT_ALLOWED
  eng "The Group Replication plugin is stopping, therefore new transactions are not allowed to start."

ER_FUNCTIONAL_INDEX_ROW_VALUE_IS_NOT_ALLOWED
  eng "Expression of functional index '%s' cannot refer to a row value."

ER_RPL_ENCRYPTION_FAILED_TO_ENCRYPT
  eng "Failed to encrypt content to write into binlog file: %s."

ER_PAGE_TRACKING_NOT_STARTED
  eng "Page Tracking is not started yet."

ER_PAGE_TRACKING_RANGE_NOT_TRACKED
  eng "Tracking was not enabled for the LSN range specified"

ER_PAGE_TRACKING_CANNOT_PURGE
  eng "Cannot purge data when concurrent clone is in progress. Try later."

ER_RPL_ENCRYPTION_CANNOT_ROTATE_BINLOG_MASTER_KEY
  eng "Cannot rotate binary log master key when 'binlog-encryption' is off."

ER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION
  eng "Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong."

ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_OPERATE_KEY
  eng "Failed to operate binary log master key on keyring, please check if keyring is loaded. The statement had no effect: the old binary log master key is still in use, the keyring, binary and relay log files are unchanged, and the server could not start using a new binary log master key for encrypting new binary and relay log files."

ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_ROTATE_LOGS
  eng "Failed to rotate one or more binary or relay log files. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key."

ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_REENCRYPT_LOG
  eng "%s. A new binary log master key was generated and will be used to encrypt new binary and relay log files. There may still exist binary or relay log files using the previous binary log master key."

ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_UNUSED_KEYS
  eng "Failed to remove unused binary log encryption keys from the keyring, please check if keyring is loaded. The unused binary log encryption keys may still exist in the keyring, and they will be removed upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution."

ER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY
  eng "Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution."

ER_NON_BOOLEAN_EXPR_FOR_CHECK_CONSTRAINT
  eng "An expression of non-boolean type specified to a check constraint '%-.192s'."

ER_COLUMN_CHECK_CONSTRAINT_REFERENCES_OTHER_COLUMN
  eng "Column check constraint '%-.192s' references other column."

ER_CHECK_CONSTRAINT_NAMED_FUNCTION_IS_NOT_ALLOWED
  eng "An expression of a check constraint '%-.192s' contains disallowed function: %s."

ER_CHECK_CONSTRAINT_FUNCTION_IS_NOT_ALLOWED
  eng "An expression of a check constraint '%-.192s' contains disallowed function."

ER_CHECK_CONSTRAINT_VARIABLES
  eng "An expression of a check constraint '%-.192s' cannot refer to a user or system variable."

ER_CHECK_CONSTRAINT_ROW_VALUE
  eng "Check constraint '%-.192s' cannot refer to a row value."

ER_CHECK_CONSTRAINT_REFERS_AUTO_INCREMENT_COLUMN
  eng "Check constraint '%-.192s' cannot refer to an auto-increment column."

ER_CHECK_CONSTRAINT_VIOLATED
  eng "Check constraint '%-.192s' is violated."

ER_CHECK_CONSTRAINT_REFERS_UNKNOWN_COLUMN
  eng "Check constraint '%-.192s' refers to non-existing column '%-.192s'."

ER_CHECK_CONSTRAINT_NOT_FOUND
  eng "Check constraint '%-.192s' is not found in the table."

ER_CHECK_CONSTRAINT_DUP_NAME
  eng "Duplicate check constraint name '%-.192s'."

ER_CHECK_CONSTRAINT_CLAUSE_USING_FK_REFER_ACTION_COLUMN
  eng "Column '%-.192s' cannot be used in a check constraint '%-.192s': needed in a foreign key constraint '%-.192s' referential action."

WARN_UNENCRYPTED_TABLE_IN_ENCRYPTED_DB
  eng "Creating an unencrypted table in a database with default encryption enabled."

ER_INVALID_ENCRYPTION_REQUEST
  eng "Request to create %s table while using an %s tablespace."

ER_CANNOT_SET_TABLE_ENCRYPTION
  eng "Table encryption differ from its database default encryption, and user doesn't have enough privilege."

ER_CANNOT_SET_DATABASE_ENCRYPTION
  eng "Database default encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege."

ER_CANNOT_SET_TABLESPACE_ENCRYPTION
  eng "Tablespace encryption differ from 'default_table_encryption' setting, and user doesn't have enough privilege."

ER_TABLESPACE_CANNOT_BE_ENCRYPTED
  eng "This tablespace can't be encrypted, because one of table's schema has default encryption OFF and user doesn't have enough privilege."

ER_TABLESPACE_CANNOT_BE_DECRYPTED
  eng "This tablespace can't be decrypted, because one of table's schema has default encryption ON and user doesn't have enough privilege."

ER_TABLESPACE_TYPE_UNKNOWN
  eng "Cannot determine the type of the tablespace named '%s'."

ER_TARGET_TABLESPACE_UNENCRYPTED
  eng "Source tablespace is encrypted but target tablespace is not."

ER_CANNOT_USE_ENCRYPTION_CLAUSE
  eng "ENCRYPTION clause is not valid for %s tablespace."

ER_INVALID_MULTIPLE_CLAUSES
  eng "Multiple %s clauses"

ER_UNSUPPORTED_USE_OF_GRANT_AS
  eng "GRANT ... AS is currently supported only for global privileges."

ER_UKNOWN_AUTH_ID_OR_ACCESS_DENIED_FOR_GRANT_AS
  eng "Either some of the authorization IDs in the AS clause are invalid or the current user lacks privileges to execute the statement."

ER_DEPENDENT_BY_FUNCTIONAL_INDEX
  eng "Column '%s' has a functional index dependency and cannot be dropped or renamed."

ER_PLUGIN_NOT_EARLY
  eng "Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc."
  bgn "Приставката '%s' не може да се използва като ранна приставка. Не я добавайте в --early-plugin-load и т.н."

ER_INNODB_REDO_LOG_ARCHIVE_START_SUBDIR_PATH
  eng "Redo log archiving start prohibits path name in 'subdir' argument"

ER_INNODB_REDO_LOG_ARCHIVE_START_TIMEOUT
  eng "Redo log archiving start timed out"

ER_INNODB_REDO_LOG_ARCHIVE_DIRS_INVALID
  eng "Server variable 'innodb_redo_log_archive_dirs' is NULL or empty"

ER_INNODB_REDO_LOG_ARCHIVE_LABEL_NOT_FOUND
  eng "Label '%.192s' not found in server variable 'innodb_redo_log_archive_dirs'"

ER_INNODB_REDO_LOG_ARCHIVE_DIR_EMPTY
  eng "Directory is empty after label '%.192s' in server variable 'innodb_redo_log_archive_dirs'"

ER_INNODB_REDO_LOG_ARCHIVE_NO_SUCH_DIR
  eng "Redo log archive directory '%.192s' does not exist or is not a directory"

ER_INNODB_REDO_LOG_ARCHIVE_DIR_CLASH
  eng "Redo log archive directory '%.192s' is in, under, or over server directory '%.192s' - '%.192s'"

ER_INNODB_REDO_LOG_ARCHIVE_DIR_PERMISSIONS
  eng "Redo log archive directory '%.192s' is accessible to all OS users"

ER_INNODB_REDO_LOG_ARCHIVE_FILE_CREATE
  eng "Cannot create redo log archive file '%.512s' (OS errno: %d - %.128s)"

ER_INNODB_REDO_LOG_ARCHIVE_ACTIVE
  eng "Redo log archiving has been started on '%.512s' - Call innodb_redo_log_archive_stop() first"

ER_INNODB_REDO_LOG_ARCHIVE_INACTIVE
  eng "Redo log archiving is not active"

ER_INNODB_REDO_LOG_ARCHIVE_FAILED
  eng "Redo log archiving failed: %.512s"

ER_INNODB_REDO_LOG_ARCHIVE_SESSION
  eng "Redo log archiving has not been started by this session"

ER_STD_REGEX_ERROR
  eng "Regex error: %-.256s in function %s."

ER_INVALID_JSON_TYPE 22032
  eng "Invalid JSON type in argument %u to function %s; an %s is required."

ER_CANNOT_CONVERT_STRING
  eng "Cannot convert string '%.64s' from %s to %s"

ER_DEPENDENT_BY_PARTITION_FUNC
  eng "Column '%s' has a partitioning function dependency and cannot be dropped or renamed."

ER_WARN_DEPRECATED_FLOAT_AUTO_INCREMENT
  eng "AUTO_INCREMENT support for FLOAT/DOUBLE columns is deprecated and will be removed in a future release. Consider removing AUTO_INCREMENT from column '%-.192s'."

ER_RPL_CANT_STOP_REPLICA_WHILE_LOCKED_BACKUP
  eng "Cannot stop the replica SQL thread while the instance is locked for backup. Try running `UNLOCK INSTANCE` first."

# When using this error message, use the
# ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_FLOAT_DIGITS
  eng "Specifying number of digits for floating point data types is deprecated and will be removed in a future release."

# When using this error message, use the
# ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_FLOAT_UNSIGNED
  eng "UNSIGNED for decimal and floating point data types is deprecated and support for it will be removed in a future release."

# When using this error message, use the
# ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_INTEGER_DISPLAY_WIDTH
  eng "Integer display width is deprecated and will be removed in a future release."

# When using this error message, use the
# ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_ZEROFILL
  eng "The ZEROFILL attribute is deprecated and will be removed in a future release. Use the LPAD function to zero-pad numbers, or store the formatted numbers in a CHAR column."

ER_CLONE_DONOR
  eng "Clone Donor Error: %.512s."

ER_CLONE_PROTOCOL
  eng "Clone received unexpected response from Donor : %.512s."

ER_CLONE_DONOR_VERSION
  eng "Clone Donor MySQL version: %.64s is different from Recipient MySQL version %.64s."

ER_CLONE_OS
  eng "Clone Donor OS: %.64s is different from Recipient OS: %.64s."

ER_CLONE_PLATFORM
  eng "Clone Donor platform: %.64s is different from Recipient platform: %.64s."

ER_CLONE_CHARSET
  eng "Clone Donor collation: %.128s is unavailable in Recipient."

ER_CLONE_CONFIG
  eng "Clone Configuration %.128s: Donor value: %.128s is different from Recipient value: %.128s."

ER_CLONE_SYS_CONFIG
  eng "Clone system configuration: %.512s"

ER_CLONE_PLUGIN_MATCH
  eng "Clone Donor plugin %.128s is not active in Recipient."

ER_CLONE_LOOPBACK
  eng "Clone cannot use loop back connection while cloning into current data directory."

ER_CLONE_ENCRYPTION
  eng "Clone needs SSL connection for encrypted table."

ER_CLONE_DISK_SPACE
  eng "Clone estimated database size is %.64s. Available space %.64s is not enough."

ER_CLONE_IN_PROGRESS
  eng "Concurrent clone in progress. Please try after clone is complete."

ER_CLONE_DISALLOWED
  eng "The clone operation cannot be executed when %s."

ER_CANNOT_GRANT_ROLES_TO_ANONYMOUS_USER
  eng "Cannot grant roles to an anonymous user."

ER_SECONDARY_ENGINE_PLUGIN
  eng "%s"

ER_SECOND_PASSWORD_CANNOT_BE_EMPTY
  eng "Empty password can not be retained as second password for user '%s'@'%s'."

ER_DB_ACCESS_DENIED
  eng "Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'."

ER_DA_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES
  eng "Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege."

ER_DA_RPL_GTID_TABLE_CANNOT_OPEN
  eng "Gtid table is not ready to be used. Table '%s.%s' cannot be opened."

ER_GEOMETRY_IN_UNKNOWN_LENGTH_UNIT SU001
  eng "The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'."

ER_DA_PLUGIN_INSTALL_ERROR
  eng "Error installing plugin '%s': %s"

ER_NO_SESSION_TEMP
  eng "Storage engine could not allocate temporary tablespace for this session."

ER_DA_UNKNOWN_ERROR_NUMBER
  eng "Got unknown error: %d"

ER_COLUMN_CHANGE_SIZE
  eng "Could not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes."

ER_REGEXP_INVALID_CAPTURE_GROUP_NAME
  eng "A capture group has an invalid name."

ER_DA_SSL_LIBRARY_ERROR
   eng "Failed to set up SSL because of the following SSL library error: %s"

ER_SECONDARY_ENGINE
  eng "Secondary engine operation failed. %s."

ER_SECONDARY_ENGINE_DDL
  eng "DDLs on a table with a secondary engine defined are not allowed."

ER_INCORRECT_CURRENT_PASSWORD
  eng "Incorrect current password. Specify the correct password which has to be replaced."

ER_MISSING_CURRENT_PASSWORD
  eng "Current password needs to be specified in the REPLACE clause in order to change it."

ER_CURRENT_PASSWORD_NOT_REQUIRED
  eng "Do not specify the current password while changing it for other users."

ER_PASSWORD_CANNOT_BE_RETAINED_ON_PLUGIN_CHANGE
  eng "Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed."

ER_CURRENT_PASSWORD_CANNOT_BE_RETAINED
  eng "Current password can not be retained for user '%s'@'%s' because new password is empty."

ER_PARTIAL_REVOKES_EXIST
  eng "At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON."

ER_CANNOT_GRANT_SYSTEM_PRIV_TO_MANDATORY_ROLE
  eng "AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege."

ER_XA_REPLICATION_FILTERS
  eng "The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica."

ER_UNSUPPORTED_SQL_MODE
  eng "sql_mode=0x%08x is not supported."

ER_REGEXP_INVALID_FLAG
  eng "Invalid match mode flag in regular expression."

ER_PARTIAL_REVOKE_AND_DB_GRANT_BOTH_EXISTS
  eng "'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean that the 'mysql' schema is corrupted."

ER_UNIT_NOT_FOUND SU001
  eng "There's no unit of measure named '%s'."

ER_INVALID_JSON_VALUE_FOR_FUNC_INDEX 22018
  eng "Invalid JSON value for CAST for functional index '%-.64s'."

ER_JSON_VALUE_OUT_OF_RANGE_FOR_FUNC_INDEX 22003
  eng "Out of range JSON value for CAST for functional index '%-.64s'."

ER_EXCEEDED_MV_KEYS_NUM
  eng "Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)."

ER_EXCEEDED_MV_KEYS_SPACE
  eng "Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes."

ER_FUNCTIONAL_INDEX_DATA_IS_TOO_LONG 22001
  eng "Data too long for functional index '%-.64s'."

ER_WRONG_MVI_VALUE
  eng "Cannot store an array or an object in a scalar key part of the index '%.192s'."

ER_WARN_FUNC_INDEX_NOT_APPLICABLE
  eng "Cannot use functional index '%-.64s' due to type or collation conversion."

ER_GRP_RPL_UDF_ERROR
  eng "The function '%s' failed. %s"

ER_UPDATE_GTID_PURGED_WITH_GR
  eng "Cannot update GTID_PURGED with the Group Replication plugin running"

ER_GROUPING_ON_TIMESTAMP_IN_DST
  eng "Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query."

ER_TABLE_NAME_CAUSES_TOO_LONG_PATH
  eng "Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS."

ER_AUDIT_LOG_INSUFFICIENT_PRIVILEGE
  eng "Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'"

OBSOLETE_ER_AUDIT_LOG_PASSWORD_HAS_BEEN_COPIED
  eng "'audit_log' password has been copied into '%.32s' and will be removed with first purged password."

ER_DA_GRP_RPL_STARTED_AUTO_REJOIN
  eng "Started auto-rejoin procedure attempt %lu of %lu"

ER_SYSVAR_CHANGE_DURING_QUERY
  eng "A plugin was loaded or unloaded during a query, a system variable table was changed."

ER_GLOBSTAT_CHANGE_DURING_QUERY
  eng "A plugin was loaded or unloaded during a query, a global status variable was changed."

ER_GRP_RPL_MESSAGE_SERVICE_INIT_FAILURE
  eng "The START GROUP_REPLICATION command failed to start its message service."

ER_CHANGE_SOURCE_WRONG_COMPRESSION_ALGORITHM_CLIENT
  eng "Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' for channel '%.192s'."

ER_CHANGE_SOURCE_WRONG_COMPRESSION_LEVEL_CLIENT
  eng "Invalid SOURCE_ZSTD_COMPRESSION_LEVEL %u for channel '%.192s'."

ER_WRONG_COMPRESSION_ALGORITHM_CLIENT
  eng "Invalid compression algorithm '%.192s'."

ER_WRONG_COMPRESSION_LEVEL_CLIENT
  eng "Invalid zstd compression level for algorithm '%.192s'."

ER_CHANGE_SOURCE_WRONG_COMPRESSION_ALGORITHM_LIST_CLIENT
  eng "Specified compression algorithm list '%.192s' exceeds total count of 3 for channel '%.192s'."

ER_CLIENT_PRIVILEGE_CHECKS_USER_CANNOT_BE_ANONYMOUS
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to ``@`%.255s`, but anonymous users are disallowed for PRIVILEGE_CHECKS_USER."

ER_CLIENT_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user."

ER_CLIENT_PRIVILEGE_CHECKS_USER_CORRUPT
  eng "Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration."

ER_CLIENT_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege."

ER_WARN_DA_PRIVILEGE_NOT_REGISTERED
  eng "Dynamic privilege '%s' is not registered with the server."

ER_CLIENT_KEYRING_UDF_KEY_INVALID
  eng "Function '%s' failed because key is invalid."

ER_CLIENT_KEYRING_UDF_KEY_TYPE_INVALID
  eng "Function '%s' failed because key type is invalid."

ER_CLIENT_KEYRING_UDF_KEY_TOO_LONG
  eng "Function '%s' failed because key length is too long."

ER_CLIENT_KEYRING_UDF_KEY_TYPE_TOO_LONG
  eng "Function '%s' failed because key type is too long."

ER_JSON_SCHEMA_VALIDATION_ERROR_WITH_DETAILED_REPORT
  eng "%s."

ER_DA_UDF_INVALID_CHARSET_SPECIFIED
  eng "Invalid character set '%s' was specified. It must be either character set name or collation name as supported by server."

ER_DA_UDF_INVALID_CHARSET
  eng "Invalid character set '%s' was specified. It must be a character set name as supported by server."

ER_DA_UDF_INVALID_COLLATION
  eng "Invalid collation '%s' was specified. It must be a collation name as supported by server."

ER_DA_UDF_INVALID_EXTENSION_ARGUMENT_TYPE
  eng "Invalid extension argument type '%s' was specified. Refer the MySQL manual for the valid UDF extension arguments type."

ER_MULTIPLE_CONSTRAINTS_WITH_SAME_NAME
  eng "Table has multiple constraints with the name '%-.192s'. Please use constraint specific '%s' clause."

ER_CONSTRAINT_NOT_FOUND
  eng "Constraint '%-.192s' does not exist."

ER_ALTER_CONSTRAINT_ENFORCEMENT_NOT_SUPPORTED
  eng "Altering constraint enforcement is not supported for the constraint '%-.192s'. Enforcement state alter is not supported for the PRIMARY, UNIQUE and FOREIGN KEY type constraints."

ER_TABLE_VALUE_CONSTRUCTOR_MUST_HAVE_COLUMNS
  eng "Each row of a VALUES clause must have at least one column, unless when used as source in an INSERT statement."

ER_TABLE_VALUE_CONSTRUCTOR_CANNOT_HAVE_DEFAULT
  eng "A VALUES clause cannot use DEFAULT values, unless used as a source in an INSERT statement."

ER_CLIENT_QUERY_FAILURE_INVALID_NON_ROW_FORMAT
  eng "The query does not comply with variable require_row_format restrictions."

ER_REQUIRE_ROW_FORMAT_INVALID_VALUE
  eng "The requested value %s is invalid for REQUIRE_ROW_FORMAT, must be either 0 or 1."

ER_FAILED_TO_DETERMINE_IF_ROLE_IS_MANDATORY
  eng "Failed to acquire lock on user management service, unable to determine if role `%s`@`%s` is mandatory"

ER_FAILED_TO_FETCH_MANDATORY_ROLE_LIST
  eng "Failed to acquire lock on user management service, unable to fetch mandatory role list"

ER_CLIENT_LOCAL_FILES_DISABLED 42000
  eng "Loading local data is disabled; this must be enabled on both the client and server sides"

ER_IMP_INCOMPATIBLE_CFG_VERSION
  eng "Failed to import %s because the CFG file version (%u) is not compatible with the current version (%u)"

ER_DA_OOM
  eng "Out of memory"

ER_DA_UDF_INVALID_ARGUMENT_TO_SET_CHARSET
  eng "Character set can be set only for the UDF argument type STRING."

ER_DA_UDF_INVALID_RETURN_TYPE_TO_SET_CHARSET
  eng "Character set can be set only for the UDF RETURN type STRING."

ER_MULTIPLE_INTO_CLAUSES
  eng "Multiple INTO clauses in one query block."

ER_MISPLACED_INTO
  eng "Misplaced INTO clause, INTO is not allowed inside subqueries, and must be placed at end of UNION clauses."

ER_USER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK
  eng "Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins."

# When using this error message, use the
# ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_DEPRECATED_YEAR_UNSIGNED
  eng "UNSIGNED for the YEAR data type is deprecated and support for it will be removed in a future release."

ER_CLONE_NETWORK_PACKET
  eng "Clone needs max_allowed_packet value to be %u or more. Current value is %u"

ER_SDI_OPERATION_FAILED_MISSING_RECORD
  eng "Failed to %s sdi for %s.%s in %s due to missing record."

ER_DEPENDENT_BY_CHECK_CONSTRAINT
  eng "Check constraint '%-.192s' uses column '%-.192s', hence column cannot be dropped or renamed."

ER_GRP_OPERATION_NOT_ALLOWED_GR_MUST_STOP
   eng "This operation cannot be performed while Group Replication is running; run STOP GROUP_REPLICATION first"

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error code.
ER_WARN_DEPRECATED_JSON_TABLE_ON_ERROR_ON_EMPTY
  eng "Specifying an ON EMPTY clause after the ON ERROR clause in a JSON_TABLE column definition is deprecated syntax and will be removed in a future release. Specify ON EMPTY before ON ERROR instead."

ER_WARN_DEPRECATED_INNER_INTO
  eng "The INTO clause is deprecated inside query blocks of query expressions and will be removed in a future release. Please move the INTO clause to the end of statement instead."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error code.
ER_WARN_DEPRECATED_VALUES_FUNCTION_ALWAYS_NULL
  eng "The VALUES function is deprecated and will be removed in a future release. It always returns NULL in this context. If you meant to access a value from the VALUES clause of the INSERT statement, consider using an alias (INSERT INTO ... VALUES (...) AS alias) and reference alias.col instead of VALUES(col) in the ON DUPLICATE KEY UPDATE clause."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
ER_WARN_DEPRECATED_SQL_CALC_FOUND_ROWS
  eng "SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
ER_WARN_DEPRECATED_FOUND_ROWS
  eng "FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead."

ER_MISSING_JSON_VALUE 22035
  eng "No value was found by '%.192s' on the specified path."

ER_MULTIPLE_JSON_VALUES 22034
  eng "More than one value was found by '%.192s' on the specified path."

ER_HOSTNAME_TOO_LONG
  eng "Hostname cannot be longer than %d characters."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT error code.
ER_WARN_CLIENT_DEPRECATED_PARTITION_PREFIX_KEY
  eng "Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release."

ER_GROUP_REPLICATION_USER_EMPTY_MSG
  eng "The START GROUP_REPLICATION command failed since the username provided for recovery channel is empty."

ER_GROUP_REPLICATION_USER_MANDATORY_MSG
  eng "The START GROUP_REPLICATION command failed since the USER option was not provided with PASSWORD for recovery channel."

ER_GROUP_REPLICATION_PASSWORD_LENGTH
  eng "The START GROUP_REPLICATION command failed since the password provided for the recovery channel exceeds the maximum length of 32 characters."

ER_SUBQUERY_TRANSFORM_REJECTED
  eng "Statement requires a transform of a subquery to a non-SET operation (like IN2EXISTS, or subquery-to-LATERAL-derived-table). This is not allowed with optimizer switch 'subquery_to_derived' on".

ER_DA_GRP_RPL_RECOVERY_ENDPOINT_FORMAT
  eng "Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)".

ER_DA_GRP_RPL_RECOVERY_ENDPOINT_INVALID
  eng "The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints."

ER_WRONG_VALUE_FOR_VAR_PLUS_ACTIONABLE_PART
  eng "Variable '%-.64s' cannot be set to the value of '%-.200s'. %-.200s"

ER_STATEMENT_NOT_ALLOWED_AFTER_START_TRANSACTION
  eng "Only BINLOG INSERT, COMMIT and ROLLBACK statements are allowed after CREATE TABLE with START TRANSACTION statement."

ER_FOREIGN_KEY_WITH_ATOMIC_CREATE_SELECT
  eng "Foreign key creation is not allowed with CREATE TABLE as SELECT and CREATE TABLE with START TRANSACTION statement."

ER_NOT_ALLOWED_WITH_START_TRANSACTION
  eng "START TRANSACTION clause cannot be used %.128s".

ER_INVALID_JSON_ATTRIBUTE
  eng "Invalid json attribute, error: \"%s\" at pos %u: '%s'"

ER_ENGINE_ATTRIBUTE_NOT_SUPPORTED
  eng "Storage engine '%s' does not support ENGINE_ATTRIBUTE."

ER_INVALID_USER_ATTRIBUTE_JSON
  eng "The user attribute must be a valid JSON object"

ER_INNODB_REDO_DISABLED
  eng "Cannot perform operation as InnoDB redo logging is disabled. Please retry after enabling redo log with ALTER INSTANCE"

ER_INNODB_REDO_ARCHIVING_ENABLED
  eng "Cannot perform operation as InnoDB is archiving redo log. Please retry after stopping redo archive by invoking innodb_redo_log_archive_stop()"

ER_MDL_OUT_OF_RESOURCES
  eng "Not enough resources to complete lock request."

ER_IMPLICIT_COMPARISON_FOR_JSON
  eng "Evaluating a JSON value in SQL boolean context does an implicit comparison against JSON integer 0; if this is not what you want, consider converting JSON to a SQL numeric type with JSON_VALUE RETURNING"

ER_FUNCTION_DOES_NOT_SUPPORT_CHARACTER_SET
  eng "The function %s does not support the character set '%s'."

ER_IMPOSSIBLE_STRING_CONVERSION
  eng "Conversion from collation %s into %s impossible for %s"

ER_SCHEMA_READ_ONLY
  eng "Schema '%s' is in read only mode."

ER_RPL_ASYNC_RECONNECT_GTID_MODE_OFF
  eng "Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when @@GLOBAL.GTID_MODE = ON."

ER_RPL_ASYNC_RECONNECT_AUTO_POSITION_OFF
  eng "Failed to enable Asynchronous Replication Connection Failover feature. The CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1 can only be set when SOURCE_AUTO_POSITION option of CHANGE REPLICATION SOURCE TO is enabled."

ER_DISABLE_GTID_MODE_REQUIRES_ASYNC_RECONNECT_OFF
  eng "The @@GLOBAL.GTID_MODE = %-.64s cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1."

ER_DISABLE_AUTO_POSITION_REQUIRES_ASYNC_RECONNECT_OFF
  eng "CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 cannot be executed because Asynchronous Replication Connection Failover is enabled i.e. CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 1."

ER_INVALID_PARAMETER_USE
  eng "Invalid use of parameters in '%s'"

ER_CHARACTER_SET_MISMATCH
  eng "Character set '%s' cannot be used in conjunction with '%s' in call to %s."

ER_WARN_VAR_VALUE_CHANGE_NOT_SUPPORTED
  eng "Changing %s not supported on this platform. Falling back to the default."

ER_INVALID_TIME_ZONE_INTERVAL
  eng "Invalid time zone interval: '%s'"

ER_INVALID_CAST
  eng "Cannot cast value to %s."

ER_HYPERGRAPH_NOT_SUPPORTED_YET 42000
  eng "The hypergraph optimizer does not yet support '%s'"

ER_WARN_HYPERGRAPH_EXPERIMENTAL
  eng "The hypergraph optimizer is highly experimental and is meant for testing only. Do not enable it unless you are a MySQL developer."

ER_DA_NO_ERROR_LOG_PARSER_CONFIGURED
  eng "None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log."

ER_DA_ERROR_LOG_TABLE_DISABLED
  eng "None of the log-sinks selected in @@global.log_error_services supports writing to the performance schema. The server will not be able to make the current runs' error events available in performance_schema.error_log. To change this, add a log-sink that supports the performance schema to @@global.log_error_services."

ER_DA_ERROR_LOG_MULTIPLE_FILTERS
  eng "@@global.log_error_services lists more than one log-filter service. This is discouraged as it will make it hard to understand which rule in which filter affected a log-event."

ER_DA_CANT_OPEN_ERROR_LOG
  eng "Could not open file '%s' for error logging%s%s"

ER_USER_REFERENCED_AS_DEFINER
  eng "User %.256s is referenced as a definer account in %s."

ER_CANNOT_USER_REFERENCED_AS_DEFINER
  eng "Operation %s failed for %.256s as it is referenced as a definer account in %s."

ER_REGEX_NUMBER_TOO_BIG
  eng "Decimal number in regular expression is too large."

# When using this error message, use the ER_PARSE_ERROR message
ER_SPVAR_NONINTEGER_TYPE
  eng "The variable \"%s\" has a non-integer based type"

WARN_UNSUPPORTED_ACL_TABLES_READ
  eng "Reads with serializable isolation/SELECT FOR SHARE are not supported for ACL tables."

ER_BINLOG_UNSAFE_ACL_TABLE_READ_IN_DML_DDL
  eng "The statement is unsafe because it updates a table depending on ACL table read operation. As storage engine row locks are skipped for ACL table, it may not have same effect on source and replica."

ER_STOP_REPLICA_MONITOR_IO_THREAD_TIMEOUT
  eng "STOP REPLICA command execution is incomplete: Replica Monitor thread got the stop signal, thread is busy, Monitor thread will stop once the current task is complete."

ER_STARTING_REPLICA_MONITOR_IO_THREAD
  eng "The Replica Monitor thread failed to start."

ER_CANT_USE_ANONYMOUS_TO_GTID_WITH_GTID_MODE_NOT_ON
 eng "Replication cannot start%.192s with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> as this server uses @@GLOBAL.GTID_MODE <> ON."

ER_CANT_COMBINE_ANONYMOUS_TO_GTID_AND_AUTOPOSITION
  eng "The options ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> and SOURCE_AUTO_POSITION = 1 cannot be used together."

ER_ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS_REQUIRES_GTID_MODE_ON
  eng "CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID> cannot be executed because @@GLOBAL.GTID_MODE <> ON."

ER_SQL_REPLICA_SKIP_COUNTER_USED_WITH_GTID_MODE_ON
  eng "The value of sql_replica_skip_counter will only take effect for channels running with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS <> OFF."

ER_USING_ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS_AS_LOCAL_OR_UUID
  eng "Using ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS creates limitations on the replication topology - you cannot fail over between downstream and upstream servers. Only use this option if it is not possible to enable GTIDs on the source, for instance, because of lack of permissions. If possible, use the procedure for enabling GTID transactions online instead, as described in the documentation."

ER_CANT_SET_ANONYMOUS_TO_GTID_AND_WAIT_UNTIL_SQL_THD_AFTER_GTIDS
  eng "WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS cannot be used on a channel configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>"

ER_CANT_SET_SQL_AFTER_OR_BEFORE_GTIDS_WITH_ANONYMOUS_TO_GTID
  eng "The SQL_AFTER_GTIDS or SQL_BEFORE_GTIDS clauses for START REPLICA cannot be used when the replication channel is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>."

ER_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME
  eng "Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_group_name"

ER_CANT_USE_SAME_UUID_AS_GROUP_NAME
  eng "CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_group_name."

ER_GRP_RPL_RECOVERY_CHANNEL_STILL_RUNNING
  eng "The group_replication_recovery channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools."

ER_INNODB_INVALID_AUTOEXTEND_SIZE_VALUE
  eng "AUTOEXTEND_SIZE should be a multiple of %uM"

ER_INNODB_INCOMPATIBLE_WITH_TABLESPACE
  eng "InnoDB: \"%s\" not allowed with general tablespaces"

ER_INNODB_AUTOEXTEND_SIZE_OUT_OF_RANGE
  eng "AUTOEXTEND_SIZE value should be between %uM and %uM"

ER_CANNOT_USE_AUTOEXTEND_SIZE_CLAUSE
  eng "AUTOEXTEND_SIZE clause is not valid for %s tablespace."

ER_ROLE_GRANTED_TO_ITSELF
  eng "User account %s is directly or indirectly granted to the role %s. The GRANT would create a loop"

ER_TABLE_MUST_HAVE_A_VISIBLE_COLUMN
  eng "A table must have at least one visible column."

ER_INNODB_COMPRESSION_FAILURE
  eng "Compression failed with the following error : %s"

ER_WARN_ASYNC_CONN_FAILOVER_NETWORK_NAMESPACE
  eng "The parameter network_namespace is reserved for future use. Please use the CHANGE REPLICATION SOURCE command to set channel network_namespace parameter."

ER_CLIENT_INTERACTION_TIMEOUT
    eng "The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior."

ER_INVALID_CAST_TO_GEOMETRY 22S01
  eng "Invalid cast from %s to %s."

ER_INVALID_CAST_POLYGON_RING_DIRECTION 22S04
  eng "Invalid cast from %s to %s. A polygon ring is in the wrong direction."

ER_GIS_DIFFERENT_SRIDS_AGGREGATION 22S05
  eng "Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID."

ER_RELOAD_KEYRING_FAILURE
  eng "Keyring reload failed. Please check error log for more details."

ER_SDI_GET_KEYS_INVALID_TABLESPACE
  eng "Tablespace '%.192s' is invalid for SDI operations."

ER_CHANGE_RPL_SRC_WRONG_COMPRESSION_ALGORITHM_SIZE
  eng "Value too long setting SOURCE_COMPRESSION_ALGORITHMS option to a %d chars long string for channel '%.192s'."

OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL_CLI
  eng "A deprecated TLS version %s is enabled for channel %s. Please use TLSv1.2 or higher."

ER_CANT_USE_SAME_UUID_AS_VIEW_CHANGE_UUID
  eng "CHANGE REPLICATION SOURCE TO ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> cannot be executed because the UUID value is equal to the group_replication_view_change_uuid."

ER_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID
  eng "Replication '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = <UUID> where the UUID value is equal to the group_replication_view_change_uuid"

ER_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE
  eng "Unable to retrieve group_replication_view_change_uuid variable during server checks on replication operations."

ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS
  eng "Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignored"

ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE
  eng "audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller."

ER_KERBEROS_CREATE_USER
  eng "Create/Alter user has failed, Configured user realm as authentication string is empty, Please make sure to configure authentication string as user realm."

ER_INSTALL_PLUGIN_CONFLICT_CLIENT
  eng "Cannot install the %.192s plugin when the %.192s plugin is installed."

ER_DA_ERROR_LOG_COMPONENT_FLUSH_FAILED
  eng "%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation."

ER_WARN_SQL_AFTER_MTS_GAPS_GAP_NOT_CALCULATED
  eng "The until clause SQL_AFTER_MTS_GAPS is being used for channel '%.192s' when GTID_MODE = ON and SOURCE_AUTO_POSITION=1 meaning the server did not compute internally what gaps may exist in the relay log transaction execution. To close any execution gaps use either the SQL_BEFORE_GTIDS or SQL_AFTER_GTIDS until clause."

ER_INVALID_ASSIGNMENT_TARGET 42000
  eng "Invalid target for assignment in INSERT or UPDATE statement '%.192s'."

ER_OPERATION_NOT_ALLOWED_ON_GR_SECONDARY
   eng "This operation cannot be performed on a Group Replication secondary member, it must be done on the group primary."

ER_GRP_RPL_FAILOVER_CHANNEL_STATUS_PROPAGATION
  eng "Unable to propagate the SOURCE_CONNECTION_AUTO_FAILOVER value for channel '%s' to group replication members. Please retry the operation."

ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON
  eng "audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON."

ER_INVALID_MFA_PLUGIN_SPECIFIED
  eng "Invalid plugin \"%s\" specified as %d factor during \"%s\"."D

ER_IDENTIFIED_BY_UNSUPPORTED
  eng "IDENTIFIED BY clause during \"%s\" not supported for plugin \"%s\"."

ER_INVALID_PLUGIN_FOR_REGISTRATION
  eng "This operation is not supported for plugin \"%s\"."

ER_PLUGIN_REQUIRES_REGISTRATION
  eng "Authentication plugin requires registration. Please refer ALTER USER syntax or set --fido-register-factor command line option to do registration."

ER_MFA_METHOD_EXISTS
  eng "%d factor authentication method exists. Please do ALTER USER... DROP %d factor before doing this operation OR do ALTER USER... MODIFY %d factor... to modify existing %d factor authentication method."

ER_MFA_METHOD_NOT_EXISTS
  eng "%d factor authentication method doesn't exist. Please do ALTER USER... ADD %d factor... before doing this operation."

ER_AUTHENTICATION_POLICY_MISMATCH
  eng "%d factor authentication method does not match against authentication policy. Please refer @@authentication_policy system variable."

ER_PLUGIN_REGISTRATION_DONE
  eng "The registration for %d factor authentication method is already completed. You cannot perform registration multiple times."

ER_INVALID_USER_FOR_REGISTRATION
  eng "The registration operation is not allowed for user '%s'@'%s'. The operation can only be performed in user's own session."

ER_USER_REGISTRATION_FAILED
  eng "Authentication plugin's registration failed."

ER_MFA_METHODS_INVALID_ORDER
  eng "%d factor authentication method should be added before %d factor authentication method."

ER_MFA_METHODS_IDENTICAL
  eng "Authentication factor should be different."

ER_INVALID_MFA_OPERATIONS_FOR_PASSWORDLESS_USER
  eng "The operation \"%s\" cannot be performed for user '%s'@'%s' configured to connect without a password."

ER_CHANGE_REPLICATION_SOURCE_NO_OPTIONS_FOR_GTID_ONLY
  eng "GTID_ONLY cannot be enabled for replication channel '%.192s'. You need GTID_MODE = ON, SOURCE_AUTO_POSITION = 1 and REQUIRE_ROW_FORMAT = 1."

ER_CHANGE_REP_SOURCE_CANT_DISABLE_REQ_ROW_FORMAT_WITH_GTID_ONLY
  eng "REQUIRE_ROW_FORMAT cannot be disabled for replication channel '%.192s' when GTID_ONLY=1."

ER_CHANGE_REP_SOURCE_CANT_DISABLE_AUTO_POSITION_WITH_GTID_ONLY
  eng "SOURCE_AUTO_POSITION cannot be disabled for replication channel '%.192s' when GTID_ONLY=1."

ER_CHANGE_REP_SOURCE_CANT_DISABLE_GTID_ONLY_WITHOUT_POSITIONS
  eng "When disabling GTID_ONLY and SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid."

ER_CHANGE_REP_SOURCE_CANT_DISABLE_AUTO_POS_WITHOUT_POSITIONS
  eng "When disabling SOURCE_AUTO_POSITION FOR CHANNEL '%.192s' you must provide SOURCE_LOG_FILE and SOURCE_LOG_POS as source positions are invalid."

ER_CHANGE_REP_SOURCE_GR_CHANNEL_WITH_GTID_MODE_NOT_ON
  eng "When configuring a group replication channel you must do it when GTID_MODE = ON."

ER_CANT_USE_GTID_ONLY_WITH_GTID_MODE_NOT_ON
  eng "Replication cannot start%.192s with GTID_ONLY = 1 as this server uses @@GLOBAL.GTID_MODE <> ON."

ER_WARN_C_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS
  eng "The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values."

ER_DA_SSL_FIPS_MODE_ERROR
  eng "SSL fips mode error: %s"

ER_VALUE_OUT_OF_RANGE
  eng "%s=%llu is outside the valid range [%llu,%llu]. %llu will be used."

ER_FULLTEXT_WITH_ROLLUP
  eng "MATCH does not support ROLLUP columns."

ER_REGEXP_MISSING_RESOURCE
  eng "Missing locale resource in regular expression library."

ER_WARN_REGEXP_USING_DEFAULT
  eng "Regular expression library used default (root) locale."

ER_REGEXP_MISSING_FILE
  eng "Missing data file in regular expression library."

ER_WARN_DEPRECATED_COLLATION
  eng "'%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead."

ER_CONCURRENT_PROCEDURE_USAGE
  eng "The %s was called when there was already another concurrent call to this procedure. No action was taken. Wait for other calls to %s to finish before retrying."

ER_DA_GLOBAL_CONN_LIMIT
  eng "Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes."

ER_DA_CONN_LIMIT
  eng "Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes."

ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE_INSTANT
  eng "Need to rebuild the table to change column type"

ER_WARN_SF_UDF_NAME_COLLISION
  eng "This function '%-.192s' has the same name as a loadable function (UDF). To invoke the stored function, it is necessary to qualify it with the schema name."

ER_CANNOT_PURGE_BINLOG_WITH_BACKUP_LOCK
  eng "Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock."

ER_TOO_MANY_WINDOWS
  eng "Too many windows in SELECT: %d. Maximum allowed is %d. Use named windows to share windows between window functions."

ER_MYSQLBACKUP_CLIENT_MSG
  eng "%s"

ER_COMMENT_CONTAINS_INVALID_STRING
  eng "Comment for %s '%s' contains an invalid %s character string: '%.64s'."

ER_DEFINITION_CONTAINS_INVALID_STRING
  eng "Definition of %s '%-.192s.%-.192s' contains an invalid %s character string: '%.64s'."

ER_CANT_EXECUTE_COMMAND_WITH_ASSIGNED_GTID_NEXT
  eng "Can't execute the given command when @@SESSION.GTID_NEXT == 'UUID:NUMBER'."

ER_XA_TEMP_TABLE
  eng "XA: Temporary tables cannot be accessed inside XA transactions when xa_detach_on_prepare=ON"

ER_INNODB_MAX_ROW_VERSION
  eng "Maximum row versions reached for table %s. No more columns can be added or dropped instantly. Please use COPY/INPLACE."

OBSOLETE_ER_INNODB_INSTANT_ADD_NOT_SUPPORTED_MAX_SIZE
  eng "Column can't be added with ALGORITHM=INSTANT as after this max possible row size crosses max permissible row size. Try ALGORITHM=INPLACE/COPY."

ER_OPERATION_NOT_ALLOWED_WHILE_PRIMARY_CHANGE_IS_RUNNING
  eng "All queries have been blocked while function 'group_replication_set_as_primary()' is executing. Please refer timeout parameter of function 'group_replication_set_as_primary()'."

ER_WARN_DEPRECATED_DATETIME_DELIMITER
  eng "Delimiter '%s' in position %d in datetime value '%s' at row %d is deprecated. Prefer the standard '%c'."

ER_WARN_DEPRECATED_SUPERFLUOUS_DELIMITER
  eng "Delimiter '%s' in position %d in datetime value '%s' at row %d is superfluous and is deprecated. Please remove."

ER_CANNOT_PERSIST_SENSITIVE_VARIABLES
  eng "Cannot persist SENSITIVE system variable '%s' because keyring component support is unavailable."

ER_WARN_CANNOT_SECURELY_PERSIST_SENSITIVE_VARIABLES
  eng "SENSITIVE system variable '%s' was persisted without encryption. Consider restarting server with keyring component support to persist SENSITIVE variables securely."

ER_WARN_TRG_ALREADY_EXISTS
  eng "Trigger '%-.192s' already exists on the table '%-.192s'.'%-.192s'."

ER_IF_NOT_EXISTS_UNSUPPORTED_TRG_EXISTS_ON_DIFFERENT_TABLE
  eng "Trigger '%-.192s'.'%-.192s' already exists on a different table. The 'IF NOT EXISTS' clause is only supported for triggers associated with the same table."

ER_IF_NOT_EXISTS_UNSUPPORTED_UDF_NATIVE_FCT_NAME_COLLISION
  eng "This function '%-.192s' has the same name as a native function. The 'IF NOT EXISTS' clause is not supported while creating a loadable function with the same name as a native function."

ER_SET_PASSWORD_AUTH_PLUGIN_ERROR
  eng "SET PASSWORD has no significance for user '%s'@'%s' as the authentication method used doesn't store authentication data in the MySQL server. Please consider using ALTER USER instead if you want to change authentication parameters."

OBSOLETE_ER_REDUCED_DBLWR_FILE_CORRUPTED
  eng "Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted."

OBSOLETE_ER_REDUCED_DBLWR_PAGE_FOUND
  eng "Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode."

ER_SRS_INVALID_LATITUDE_OF_ORIGIN SR002
  eng "Latitude of origin must be within [-90, 90] degrees, specified in the SRS angular unit."

ER_SRS_INVALID_LONGITUDE_OF_ORIGIN SR002
  eng "Longitude of origin must be within (-180, 180] degrees, specified in the SRS angular unit."

ER_SRS_UNUSED_PROJ_PARAMETER_PRESENT SR002
  eng "The spatial reference system definition for SRID %u contains unused projection parameter \"%s\"."

ER_GIPK_COLUMN_EXISTS
  eng "Failed to generate invisible primary key. Column 'my_row_id' already exists."

ER_GIPK_FAILED_AUTOINC_COLUMN_EXISTS
  eng "Failed to generate invisible primary key. Auto-increment column already exists."

ER_GIPK_COLUMN_ALTER_NOT_ALLOWED
  eng "Altering generated invisible primary key column 'my_row_id' is not allowed."

ER_DROP_PK_COLUMN_TO_DROP_GIPK
  eng "Please drop primary key column to be able to drop generated invisible primary key."

ER_CREATE_SELECT_WITH_GIPK_DISALLOWED_IN_SBR
  eng "Generating an invisible primary key for a table created using CREATE TABLE ... SELECT ... is disallowed when binlog_format=STATEMENT. It cannot be guaranteed that the SELECT retrieves rows in the same order on source and replica. Therefore, it cannot be guaranteed that the value generated for the generated implicit primary key column will be the same on source and replica for all rows. Use binlog_format=ROW or MIXED to execute this statement."

ER_DA_EXPIRE_LOGS_DAYS_IGNORED
  eng "The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. To set one, first unset the other by setting it to 0."

ER_CTE_RECURSIVE_NOT_UNION
  eng "Recursive table reference in EXCEPT or INTERSECT operand is not allowed."

ER_COMMAND_BACKEND_FAILED_TO_FETCH_SECURITY_CTX
  eng "Error when trying to fetch information from security context object, when trying to connect the server."

ER_COMMAND_SERVICE_BACKEND_FAILED
  eng "Error in command service backend interface, because of : "%s""

ER_CLIENT_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS
  eng "The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER."

ER_GROUP_REPLICATION_FORCE_MEMBERS_COMMAND_FAILURE
  eng "The 'SET GLOBAL group_replication_force_members=%s' command encountered a failure. %s"

ER_WARN_DEPRECATED_IDENT
  eng "Using %s as unquoted identifier is deprecated, please use quotes or rename the identifier."

ER_INTERSECT_ALL_MAX_DUPLICATES_EXCEEDED
  eng "Max number of duplicate rows in INTERSECT ALL exceeded."

ER_TP_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT
  eng "Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per group"

ER_BAD_TIMESTAMP_FORMAT
  eng "Invalid timestamp format in %s udf"

ER_SHAPE_PRIDICTION_UDF
  eng "SHAPE_PREDICTION UDF %s got error because of %s."

ER_SRS_INVALID_HEIGHT SR002
  eng "Height parameter must be non negative."

ER_SRS_INVALID_SCALING SR002
  eng "Scaling parameter must be non negative."

ER_SRS_INVALID_ZONE_WIDTH SR002
  eng "Zone width parameter must be an integer between 1-60."

ER_SRS_INVALID_LATITUDE_POLAR_STERE_VAR_A SR002
  eng "Latitude of origin must be +-90 degrees, specified in the SRS angular unit, in Polar Stereographic (variant A) projection method (EPSG:9810)."

ER_WARN_DEPRECATED_CLIENT_NO_SCHEMA_OPTION
  eng "The client is using a deprecated CLIENT_NO_SCHEMA client option. CLIENT_NO_SCHEMA will be removed in a future release."

ER_TABLE_NOT_EMPTY
  eng "Table '%-.192s' is not empty."

ER_TABLE_NO_PRIMARY_KEY
  eng "Table '%-.192s' has no primary key."

ER_TABLE_IN_SHARED_TABLESPACE
  eng "Table '%-.192s' is in a shared tablespace."

ER_INDEX_OTHER_THAN_PK
  eng "Table '%-.192s' has indexes other than primary key."

ER_LOAD_BULK_DATA_UNSORTED
  eng "[IN PRIMARY KEY ORDER] specified but data not sorted: LOAD BULK DATA into table '%-.192s' failed: %s"

ER_BULK_EXECUTOR_ERROR
  eng "Bulk executor error: %s"

ER_BULK_READER_LIBCURL_INIT_FAILED
  eng "Bulk reader failed to initialize libcurl"

ER_BULK_READER_LIBCURL_ERROR
  eng "Bulk reader got libcurl error: %s"

ER_BULK_READER_SERVER_ERROR
  eng "Bulk reader got error response from server: %ld"

ER_BULK_READER_COMMUNICATION_ERROR
  eng "Bulk reader got error in communication with source server, check the error log for additional details."

ER_BULK_LOAD_DATA_FAILED
  eng "Bulk loader failed, mysql_load->load returned an error, check the error log for additional details."

ER_BULK_LOADER_COLUMN_TOO_BIG_FOR_LEFTOVER_BUFFER
  eng "CSV column too big for leftover buffer."

ER_BULK_LOADER_COMPONENT_ERROR
  eng "Bulk loader component error: %s"

ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE
  eng "The first file being loaded contained less lines than the ignore clause"

ER_BULK_PARSER_MISSING_ENCLOSED_BY
  eng "Missing ENCLOSED BY character at row %ld in file '%s'. Add OPTIONALLY to the ENCLOSED BY clause to allow this input."

ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED
  eng "The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'."

ER_BULK_PARSER_COPY_BUFFER_SIZE_EXCEEDED
  eng "The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'."

ER_BULK_PARSER_UNEXPECTED_END_OF_INPUT
  eng "Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing."

ER_BULK_PARSER_UNEXPECTED_ROW_TERMINATOR
  eng "Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing."

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY
  eng "Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'."

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE
  eng "Unexpected characters after NULL escape (\N) found at row %ld in file '%s'."

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR
  eng "Unexpected characters after column terminator found at row %ld in file '%s'."

ER_BULK_PARSER_INCOMPLETE_ESCAPE_SEQUENCE
  eng "Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence."

ER_LOAD_BULK_DATA_FAILED
  eng "LOAD BULK DATA into table '%-.192s' failed: %s"

ER_LOAD_BULK_DATA_WRONG_VALUE_FOR_FIELD
  eng "Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'"

ER_LOAD_BULK_DATA_WARN_NULL_TO_NOTNULL
  eng "NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'"

ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR
  eng "On a Group Replication channel, setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed."

ER_CANT_CHANGE_SYS_VAR_IN_READ_ONLY_MODE
  eng "Cannot change the '%s' system variable in read-only mode."

ER_INNODB_INSTANT_ADD_DROP_NOT_SUPPORTED_MAX_SIZE
  eng "Column can't be added or dropped with ALGORITHM=INSTANT as either max possible row size already crosses max permissible row size or may cross it after add. Try ALGORITHM=INPLACE/COPY."

ER_INNODB_INSTANT_ADD_NOT_SUPPORTED_MAX_FIELDS
  eng "Column can't be added to '%s' with ALGORITHM=INSTANT anymore. Please try ALGORITHM=INPLACE/COPY."

ER_CANT_SET_PERSISTED
  eng "Failed to set persisted options."

ER_INSTALL_COMPONENT_SET_NULL_VALUE
  eng "The value supplied for %s in the SET list cannot be null"

ER_INSTALL_COMPONENT_SET_UNUSED_VALUE
  eng "The assignment of %s in SET doesn't match any of the variables registered by the component(s)"

ER_WARN_DEPRECATED_USER_DEFINED_COLLATIONS
  eng "'%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead."

ER_USER_LOCK_OVERLONG_NAME  42000
  eng "User-level lock name '%-.192s' should not exceed %d characters."

ER_WARN_NO_SPACE_VERSION_COMMENT
  eng "Immediately starting the version comment after the version number is deprecated and may change behavior in a future release. Please insert a white-space character after the version number."

ER_VALIDATE_PASSWORD_INSUFFICIENT_CHANGED_CHARACTERS
  eng "The new password must have at least '%u' characters that are different from the old password. It has only '%u' character(s) different. For this comparison, uppercase letters and lowercase letters are considered to be equal."

ER_WARN_DEPRECATED_WITH_NOTE
  eng "'%s' is deprecated and will be removed in a future release. %s"

ER_CANT_RUN_COMMAND_SERVICES_RECURSIVELY
  eng "Running recursive calls to SQL execution service is not supported"

#
#  End of 8.0 error messages (server-to-client).
#  Do NOT add messages intended for the error log above!
#

################################################################################
# Error numbers 5000 to 5999 are reserved for X Plugin. Please do not use
# them for other error messages.
################################################################################

reserved-error-section 5000 5999

################################################################################
# DO NOT add messages for the error-log to this file;
# they go in messages_to_error_log.txt in the same
# directory as this file.
#
# This file is for messages the server sends to clients.
# This explicitly does NOT include messages compiled into
# the client-library (libmysql / C-API) itself.
#
# See the FAQ in errmsg_readme.txt in the
# same directory as this file for more
# information.
################################################################################
PK� �\����messages_to_error_log.txtnu�[���# Copyright (c) 2017, 2025, Oracle and/or its affiliates.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2.0,
# as published by the Free Software Foundation.
#
# This program is designed to work with certain software (including
# but not limited to OpenSSL) that is licensed under separate terms,
# as designated in a particular file or component or in included license
# documentation.  The authors of MySQL hereby grant you an additional
# permission to link the program and your derivative works with the
# separately licensed software that they have either included with
# the program or referenced in the documentation.
#
# Without limiting anything contained in the foregoing, this file,
# which is part of C Driver for MySQL (Connector/C), is also subject to the
# Universal FOSS Exception, version 1.0, a copy of which can be found at
# http://oss.oracle.com/licenses/universal-foss-exception.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License, version 2.0, for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA

################################################################################
# DO NOT add server-to-client messages here;
# they go in messages_to_clients.txt
# in the same directory as this file.
#
# This file is for messages intended for the error log only.
#
# See the FAQ in errmsg_readme.txt in the
# same directory as this file for more
# information.
################################################################################

# "languages" and "default-language" directives should not be set in this
# file; their values are carried over from messages_to_clients.txt.

################################################################################
#
# Start of 8.0 error messages (error log).
#
# The build process automatically starts with this offset
# for messages intended for the error-log. Setting it again
# here would be harmless; changing it would not as this
# offset is mentioned in the documentation and #defined in
# the source:
# start-error-number 10000

ER_PARSER_TRACE XX999
  eng "Parser saw: %s"

ER_BOOTSTRAP_CANT_THREAD
  eng "Can't create thread to handle bootstrap (errno: %d)"

ER_TRIGGER_INVALID_VALUE
  eng "Trigger for table '%s'.'%s': invalid %s value (%s)."

ER_OPT_WRONG_TREE
  eng "Wrong tree: %s"

ER_DD_FAILSAFE
  eng "Error: Invalid %s"

ER_DD_NO_WRITES_NO_REPOPULATION
  eng "Skip re-populating collations and character sets tables in %s%sread-only mode."

ER_DD_VERSION_FOUND
  eng "Using data dictionary with version '%d'."

ER_DD_VERSION_INSTALLED
  eng "Installed data dictionary with version %d"

ER_DD_VERSION_UNSUPPORTED
  eng "Data Dictionary version '%d' not supported."

OBSOLETE_ER_LOG_SYSLOG_FACILITY_FAIL
  eng "Failed to set syslog facility to \"%s\", setting to \"%s\" (%d) instead."

ER_LOG_SYSLOG_CANNOT_OPEN
  eng "Cannot open %s; check privileges, or remove syseventlog from --log-error-services!"

ER_LOG_SLOW_CANNOT_OPEN
  eng " either restart the query logging by using \"SET GLOBAL SLOW_QUERY_LOG=ON\" or"

ER_LOG_GENERAL_CANNOT_OPEN
  eng " either restart the query logging by using \"SET GLOBAL GENERAL_LOG=ON\" or"

ER_LOG_CANNOT_WRITE
  eng "Failed to write to %s: %s"

OBSOLETE_ER_RPL_ZOMBIE_ENCOUNTERED
  eng "While initializing dump thread for replica with %s <%s>, found a zombie dump thread with the same %s. Source is killing the zombie dump thread(%u)."

ER_RPL_GTID_TABLE_CANNOT_OPEN
  eng "Gtid table is not ready to be used. Table '%s.%s' cannot be opened."

ER_SYSTEM_SCHEMA_NOT_FOUND
  eng "System schema directory does not exist."

ER_DD_INIT_UPGRADE_FAILED
  eng "Error in initializing dictionary, upgrade will do a cleanup and exit"

ER_VIEW_UNKNOWN_CHARSET_OR_COLLATION
  eng "View '%s'.'%s': unknown charset name and/or collation name (client: '%s'; connection: '%s')."

ER_DD_VIEW_CANT_ALLOC_CHARSET
  eng "Error in allocating memory for character set name for view %s.%s."

ER_DD_INIT_FAILED
  eng "Data Dictionary initialization failed."

ER_DD_UPDATING_PLUGIN_MD_FAILED
  eng "Failed to update plugin metadata in dictionary tables."

ER_DD_POPULATING_TABLES_FAILED
  eng "Failed to Populate DD tables."

ER_DD_VIEW_CANT_CREATE
  eng "Error in Creating View %s.%s"

ER_DD_METADATA_NOT_FOUND
  eng "Unable to start server. Cannot find the meta data for data dictionary table '%s'."

ER_DD_CACHE_NOT_EMPTY_AT_SHUTDOWN
  eng "Dictionary cache not empty at shutdown."

ER_DD_OBJECT_REMAINS
  eng "Dictionary objects used but not released."

ER_DD_OBJECT_REMAINS_IN_RELEASER
  eng "Dictionary objects left in default releaser."

ER_DD_OBJECT_RELEASER_REMAINS
  eng "Dictionary object auto releaser not deleted"

ER_DD_CANT_GET_OBJECT_KEY
  eng "Error: Unable to create primary object key"

ER_DD_CANT_CREATE_OBJECT_KEY
  eng "Error: Unable to create object key"

ER_CANT_CREATE_HANDLE_MGR_THREAD
  eng "Can't create handle_manager thread (errno= %d)"

ER_RPL_REPO_HAS_GAPS
  eng "It is not possible to change the type of the relay log's repository because there are workers' repositories with gaps. Please, fix the gaps first before doing such change."

ER_INVALID_VALUE_FOR_ENFORCE_GTID_CONSISTENCY
  eng "option 'enforce-gtid-consistency': value '%s' was not recognized. Setting enforce-gtid-consistency to OFF."

ER_CHANGED_ENFORCE_GTID_CONSISTENCY
  eng "Changed ENFORCE_GTID_CONSISTENCY from %s to %s."

ER_CHANGED_GTID_MODE
 eng "Changed GTID_MODE from %s to %s."

ER_DISABLED_STORAGE_ENGINE_AS_DEFAULT
  eng "%s is set to a disabled storage engine %s."

ER_DEBUG_SYNC_HIT
  eng "Debug sync points hit:                   %22s"

ER_DEBUG_SYNC_EXECUTED
  eng "Debug sync points executed:              %22s"

ER_DEBUG_SYNC_THREAD_MAX
  eng "Debug sync points max active per thread: %22s"

ER_DEBUG_SYNC_OOM
  eng "Debug Sync Facility disabled due to lack of memory."

ER_CANT_INIT_TC_LOG
  eng "Can't init tc log"

ER_EVENT_CANT_INIT_QUEUE
  eng "Event Scheduler: Can't initialize the execution queue"

ER_EVENT_PURGING_QUEUE
  eng "Event Scheduler: Purging the queue. %u events"

ER_EVENT_LAST_EXECUTION
  eng "Event Scheduler: Last execution of %s.%s. %s"

ER_EVENT_MESSAGE_STACK
  eng "%*s"

ER_EVENT_EXECUTION_FAILED
  eng "Event Scheduler: [%s].[%s.%s] event execution failed."

ER_CANT_INIT_SCHEDULER_THREAD
  eng "Event Scheduler: Cannot initialize the scheduler thread"

ER_SCHEDULER_STOPPED
  eng "Event Scheduler: Stopped"

ER_CANT_CREATE_SCHEDULER_THREAD
  eng "Event scheduler: Failed to start scheduler, Can not create thread for event scheduler (errno=%d)"

ER_SCHEDULER_WAITING
  eng "Event Scheduler: Waiting for the scheduler thread to reply"

ER_SCHEDULER_STARTED
  eng "Event Scheduler: scheduler thread started with id %u"

ER_SCHEDULER_STOPPING_FAILED_TO_GET_EVENT
  eng "Event Scheduler: Serious error during getting next event to execute. Stopping"

ER_SCHEDULER_STOPPING_FAILED_TO_CREATE_WORKER
  eng "Event_scheduler::execute_top: Can not create event worker thread (errno=%d). Stopping event scheduler"

ER_SCHEDULER_KILLING
  eng "Event Scheduler: Killing the scheduler thread, thread id %u"

ER_UNABLE_TO_RESOLVE_IP
  eng "IP address '%s' could not be resolved: %s"

ER_UNABLE_TO_RESOLVE_HOSTNAME
  eng "Host name '%s' could not be resolved: %s"

ER_HOSTNAME_RESEMBLES_IPV4
  eng "IP address '%s' has been resolved to the host name '%s', which resembles IPv4-address itself."

ER_HOSTNAME_DOESNT_RESOLVE_TO
  eng "Hostname '%s' does not resolve to '%s'."

ER_ADDRESSES_FOR_HOSTNAME_HEADER
  eng "Hostname '%s' has the following IP addresses:"

ER_ADDRESSES_FOR_HOSTNAME_LIST_ITEM
  eng " - %s"

ER_TRG_WITHOUT_DEFINER
  eng "Definer clause is missing in Trigger of Table %s. Rebuild Trigger to fix definer."

ER_TRG_NO_CLIENT_CHARSET
  eng "Client character set is missing for trigger of table %s. Using default character set."

ER_PARSING_VIEW
  eng "Error in parsing view %s.%s"

ER_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP
  eng "Failed to bootstrap components infrastructure."

ER_COMPONENTS_INFRASTRUCTURE_SHUTDOWN
  eng "Failed to shutdown components infrastructure."

ER_COMPONENTS_PERSIST_LOADER_BOOTSTRAP
  eng "Failed to bootstrap persistent components loader."

ER_DEPART_WITH_GRACE
  eng "Giving %d client threads a chance to die gracefully"

ER_CA_SELF_SIGNED
  eng "CA certificate %s is self signed."

ER_SSL_LIBRARY_ERROR
   eng "Failed to set up SSL because of the following SSL library error: %s"

ER_NO_THD_NO_UUID
  eng "Failed to generate a server UUID because it is failed to allocate the THD."

ER_UUID_SALT
  eng "Salting uuid generator variables, current_pid: %lu, server_start_time: %lu, bytes_sent: %llu, "

ER_UUID_IS
  eng "Generated uuid: '%s', server_start_time: %lu, bytes_sent: %llu"

ER_UUID_INVALID
  eng "The server_uuid stored in auto.cnf file is not a valid UUID."

ER_UUID_SCRUB
  eng "Garbage characters found at the end of the server_uuid value in auto.cnf file. It should be of length '%d' (UUID_LENGTH). Clear it and restart the server. "

ER_CREATING_NEW_UUID
  eng "No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: %s."

ER_CANT_CREATE_UUID
  eng "Initialization of the server's UUID failed because it could not be read from the auto.cnf file. If this is a new server, the initialization failed because it was not possible to generate a new UUID."

ER_UNKNOWN_UNSUPPORTED_STORAGE_ENGINE
  eng "Unknown/unsupported storage engine: %s"

ER_SECURE_AUTH_VALUE_UNSUPPORTED
  eng "Unsupported value 0 for secure-auth"

ER_INVALID_INSTRUMENT
  eng "Invalid instrument name or value for performance_schema_instrument '%s'",

ER_INNODB_MANDATORY
  eng "The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored."

OBSOLETE_ER_INNODB_CANNOT_BE_IGNORED
  eng "ignore-builtin-innodb is ignored and will be removed in future releases."

OBSOLETE_ER_OLD_PASSWORDS_NO_MIDDLE_GROUND
  eng "Invalid old_passwords mode: 1. Valid values are 2 and 0"

ER_VERBOSE_REQUIRES_HELP
  eng "--verbose is for use with --help; did you mean --log-error-verbosity?"

ER_POINTLESS_WITHOUT_SLOWLOG
  eng "options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-replica-statements have no effect if --slow-query-log is not set"

ER_WASTEFUL_NET_BUFFER_SIZE
  eng "net_buffer_length (%lu) is set to be larger than max_allowed_packet (%lu). Please rectify."

ER_DEPRECATED_TIMESTAMP_IMPLICIT_DEFAULTS
  eng "TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details)."

ER_FT_BOOL_SYNTAX_INVALID
  eng "Invalid ft-boolean-syntax string: %s"

ER_CREDENTIALLESS_AUTO_USER_BAD
  eng "'NO_AUTO_CREATE_USER' sql mode was not set."

ER_CONNECTION_HANDLING_OOM
  eng "Could not allocate memory for connection handling"

ER_THREAD_HANDLING_OOM
  eng "Could not allocate memory for thread handling"

ER_CANT_CREATE_TEST_FILE
  eng "Can't create test file %s"

ER_CANT_CREATE_PID_FILE
  eng "Can't start server: can't create PID file: %s"

ER_CANT_REMOVE_PID_FILE
  eng "Unable to delete pid file: %s"

ER_CANT_CREATE_SHUTDOWN_THREAD
  eng "Can't create thread to handle shutdown requests (errno= %d)"

ER_SEC_FILE_PRIV_CANT_ACCESS_DIR
  eng "Failed to access directory for --secure-file-priv. Please make sure that directory exists and is accessible by MySQL Server. Supplied value : %s"

ER_SEC_FILE_PRIV_IGNORED
  eng "Ignoring --secure-file-priv value as server is running with --initialize(-insecure)."

ER_SEC_FILE_PRIV_EMPTY
  eng "Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path."

ER_SEC_FILE_PRIV_NULL
  eng "--secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled"

ER_SEC_FILE_PRIV_DIRECTORY_INSECURE
  eng "Insecure configuration for --secure-file-priv: %s is accessible through --secure-file-priv. Consider choosing a different directory."

ER_SEC_FILE_PRIV_CANT_STAT
  eng "Failed to get stat for directory pointed out by --secure-file-priv"

ER_SEC_FILE_PRIV_DIRECTORY_PERMISSIONS
  eng "Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory."

ER_SEC_FILE_PRIV_ARGUMENT_TOO_LONG
  eng "Value for --secure-file-priv is longer than maximum limit of %d"

ER_CANT_CREATE_NAMED_PIPES_THREAD
  eng "Can't create thread to handle named pipes (errno= %d)"

ER_CANT_CREATE_TCPIP_THREAD
  eng "Can't create thread to handle TCP/IP (errno= %d)"

ER_CANT_CREATE_SHM_THREAD
  eng "Can't create thread to handle shared memory (errno= %d)"

ER_CANT_CREATE_INTERRUPT_THREAD
  eng "Can't create interrupt-thread (error %d, errno: %d)"

ER_WRITABLE_CONFIG_REMOVED
  eng "World-writable config file '%s' has been removed."

ER_CORE_VALUES
  eng "setrlimit could not change the size of core files to 'infinity';  We may not be able to generate a core file on signals"

ER_WRONG_DATETIME_SPEC
  eng "Wrong date/time format specifier: %s"

ER_RPL_BINLOG_FILTERS_OOM
  eng "Could not allocate replication and binlog filters: %s"

ER_KEYCACHE_OOM
  eng "Cannot allocate the keycache"

ER_CONFIRMING_THE_FUTURE
  eng "Current time has got past year 2038. Validating current time with %d iterations before initiating the normal server shutdown process."

ER_BACK_IN_TIME
  eng "Iteration %d: Obtained valid current time from system"

ER_FUTURE_DATE
  eng "Iteration %d: Current time obtained from system is greater than 2038"

ER_UNSUPPORTED_DATE
  eng "This MySQL server doesn't support dates later then 2038"

ER_STARTING_AS
  eng "%s (mysqld %s) starting as process %lu"

ER_SHUTTING_DOWN_REPLICA_THREADS
  eng "Shutting down replica threads"

ER_DISCONNECTING_REMAINING_CLIENTS
  eng "Forcefully disconnecting %d remaining clients"

ER_ABORTING
  eng "Aborting"

ER_BINLOG_END
  eng "Binlog end"

ER_CALL_ME_LOCALHOST
  eng "gethostname failed, using '%s' as hostname"

ER_USER_REQUIRES_ROOT
  eng "One can only use the --user switch if running as root"

ER_REALLY_RUN_AS_ROOT
  eng "Fatal error: Please read \"Security\" section of the manual to find out how to run mysqld as root!"

ER_USER_WHAT_USER
  eng "Fatal error: Can't change to run as user '%s' ;  Please check that the user exists!"

ER_TRANSPORTS_WHAT_TRANSPORTS
  eng "Server is started with --require-secure-transport=ON but no secure transports (SSL or Shared Memory) are configured."

ER_FAIL_SETGID
  eng "setgid: %s"

ER_FAIL_SETUID
  eng "setuid: %s"

ER_FAIL_SETREGID
  eng "setregid: %s"

ER_FAIL_SETREUID
  eng "setreuid: %s"

ER_FAIL_CHROOT
  eng "chroot: %s"

ER_WIN_LISTEN_BUT_HOW
  eng "TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS"

ER_NOT_RIGHT_NOW
  eng "CTRL-C ignored during startup"

ER_FIXING_CLIENT_CHARSET
  eng "'%s' can not be used as client character set. '%s' will be used as default client character set."

ER_OOM
  eng "Out of memory"

ER_FAILED_TO_LOCK_MEM
  eng "Failed to lock memory. Errno: %d"

ER_MYINIT_FAILED
  eng "my_init() failed."

ER_BEG_INITFILE
  eng "Execution of init_file \'%s\' started."

ER_END_INITFILE
  eng "Execution of init_file \'%s\' ended."

ER_CHANGED_MAX_OPEN_FILES
  eng "Changed limits: max_open_files: %lu (requested %lu)"

ER_CANT_INCREASE_MAX_OPEN_FILES
  eng "Could not increase number of max_open_files to more than %lu (request: %lu)"

ER_CHANGED_MAX_CONNECTIONS
  eng "Changed limits: max_connections: %lu (requested %lu)"

ER_CHANGED_TABLE_OPEN_CACHE
  eng "Changed limits: table_open_cache: %lu (requested %lu)"

ER_THE_USER_ABIDES
  eng "Ignoring user change to '%s' because the user was set to '%s' earlier on the command line"

ER_RPL_CANT_ADD_DO_TABLE
  eng "Could not add do table rule '%s'!"

ER_RPL_CANT_ADD_IGNORE_TABLE
  eng "Could not add ignore table rule '%s'!"

ER_TRACK_VARIABLES_BOGUS
  eng "The variable session_track_system_variables either has duplicate values or invalid values."

ER_EXCESS_ARGUMENTS
  eng "Too many arguments (first extra is '%s')."

ER_VERBOSE_HINT
  eng "Use --verbose --help to get a list of available options!"

ER_CANT_READ_ERRMSGS
  eng "Unable to read errmsg.sys file"

ER_CANT_INIT_DBS
  eng "Can't init databases"

ER_LOG_OUTPUT_CONTRADICTORY
  eng "There were other values specified to log-output besides NONE. Disabling slow and general logs anyway."

ER_NO_CSV_NO_LOG_TABLES
  eng "CSV engine is not present, falling back to the log files"

ER_RPL_REWRITEDB_MISSING_ARROW
  eng "Bad syntax in replicate-rewrite-db - missing '->'!"

ER_RPL_REWRITEDB_EMPTY_FROM
  eng "Bad syntax in replicate-rewrite-db - empty FROM db!"

ER_RPL_REWRITEDB_EMPTY_TO
  eng "Bad syntax in replicate-rewrite-db - empty TO db!"

ER_LOG_FILES_GIVEN_LOG_OUTPUT_IS_TABLE
  eng "Although a path was specified for the %s, log tables are used. To enable logging to files use the --log-output=file option."

ER_LOG_FILE_INVALID
  eng "Invalid value for %s: %s"

ER_LOWER_CASE_TABLE_NAMES_CS_DD_ON_CI_FS_UNSUPPORTED
  eng "The server option 'lower_case_table_names' is configured to use case sensitive table names but the data directory is on a case-insensitive file system which is an unsupported combination. Please consider either using a case sensitive file system for your data directory or switching to a case-insensitive table name mode."

ER_LOWER_CASE_TABLE_NAMES_USING_2
  eng "Setting lower_case_table_names=2 because file system for %s is case insensitive"

ER_LOWER_CASE_TABLE_NAMES_USING_0
  eng "lower_case_table_names was set to 2, even though your the file system '%s' is case sensitive.  Now setting lower_case_table_names to 0 to avoid future problems."

ER_NEED_LOG_BIN
  eng "You need to use --log-bin to make %s work."

ER_NEED_FILE_INSTEAD_OF_DIR
  eng "Path '%s' is a directory name, please specify a file name for %s option"

# Unused since MySQL 8.0.3
ER_LOG_BIN_BETTER_WITH_NAME
  eng "No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a source and has his hostname changed!! Please use '--log-bin=%s' to avoid this problem."

ER_BINLOG_NEEDS_SERVERID
  eng "You have enabled the binary log, but you haven't provided the mandatory server-id. Please refer to the proper server start-up parameters documentation"

ER_RPL_CANT_MAKE_PATHS
  eng "Unable to create replication path names: out of memory or path names too long (path name exceeds %d or file name exceeds %d)."

ER_CANT_INITIALIZE_GTID
  eng "Failed to initialize GTID structures."

ER_CANT_INITIALIZE_EARLY_PLUGINS
  eng "Failed to initialize early plugins."

ER_CANT_INITIALIZE_BUILTIN_PLUGINS
  eng "Failed to initialize builtin plugins."

ER_CANT_INITIALIZE_DYNAMIC_PLUGINS
  eng "Failed to initialize dynamic plugins."

ER_PERFSCHEMA_INIT_FAILED
  eng "Performance schema disabled (reason: init failed)."

ER_STACKSIZE_UNEXPECTED
  eng "Asked for %lu thread stack, but got %ld"

OBSOLETE_ER_CANT_SET_DATADIR
  eng "failed to set datadir to %s"

ER_CANT_STAT_DATADIR
  eng "Can't read data directory's stats (%d): %s. Assuming that it's not owned by the same user/group"

ER_CANT_CHOWN_DATADIR
  eng "Can't change data directory owner to %s"

ER_CANT_SET_UP_PERSISTED_VALUES
  eng "Setting persistent options failed."

ER_CANT_SAVE_GTIDS
  eng "Failed to save the set of Global Transaction Identifiers of the last binary log into the mysql.gtid_executed table while the server was shutting down. The next server restart will make another attempt to save Global Transaction Identifiers into the table."

ER_AUTH_CANT_SET_DEFAULT_PLUGIN
  eng "Can't start server: Invalid value for --default-authentication-plugin"

ER_CANT_JOIN_SHUTDOWN_THREAD
  eng "Could not join %sthread. error:%d"

ER_CANT_HASH_DO_AND_IGNORE_RULES
  eng "An error occurred while building do_table and ignore_table rules to hashes for global replication filter."

ER_CANT_OPEN_CA
  eng "Error opening CA certificate file"

ER_CANT_ACCESS_CAPATH
  eng "Error accessing directory pointed by --ssl-capath"

ER_SSL_TRYING_DATADIR_DEFAULTS
  eng "Found %s, %s and %s in data directory. Trying to enable SSL support using them."

ER_AUTO_OPTIONS_FAILED
  eng "Failed to create %s(file: '%s', errno %d)"

ER_CANT_INIT_TIMER
  eng "Failed to initialize timer component (errno %d)."

ER_SERVERID_TOO_LARGE
  eng "server-id configured is too large to represent with server-id-bits configured."

ER_DEFAULT_SE_UNAVAILABLE
  eng "Default%s storage engine (%s) is not available"

ER_CANT_OPEN_ERROR_LOG
  eng "Could not open file '%s' for error logging%s%s"

ER_INVALID_ERROR_LOG_NAME
  eng "Invalid log file name after expanding symlinks: '%s'"

ER_RPL_INFINITY_DENIED
  eng "using --replicate-same-server-id in conjunction with --log-replica-updates is impossible, it would lead to infinite loops in this server."

ER_RPL_INFINITY_IGNORED
  eng "using --replicate-same-server-id in conjunction with --log-replica-updates would lead to infinite loops in this server. However this will be ignored as the --log-bin option is not defined or your server is running with global transaction identiers enabled."

OBSOLETE_ER_NDB_TABLES_NOT_READY
  eng "NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value"

# could use verbatim, but we want an error-code
ER_TABLE_CHECK_INTACT
  eng "%s"

ER_DD_TABLESPACE_NOT_FOUND
  eng "Unable to start server. The data dictionary tablespace '%s' does not exist."

ER_DD_TRG_CONNECTION_COLLATION_MISSING
  eng "Connection collation is missing for trigger of table %s. Using default connection collation."

ER_DD_TRG_DB_COLLATION_MISSING
  eng "Database collation is missing for trigger of table %s. Using Default character set."

ER_DD_TRG_DEFINER_OOM
  eng "Error in Memory allocation for Definer %s for Trigger."

# ER_TRG_CORRUPTED_FILE
ER_DD_TRG_FILE_UNREADABLE
  eng "Error in reading %s.TRG file."

ER_TRG_CANT_PARSE
  eng "Error in parsing Triggers from %s.TRG file."

ER_DD_TRG_CANT_ADD
  eng "Error in creating DD entry for Trigger %s.%s"

ER_DD_CANT_RESOLVE_VIEW
  eng "Resolving dependency for the view '%s.%s' failed. View is no more valid to use"

ER_DD_VIEW_WITHOUT_DEFINER
  eng "%s.%s has no definer (as per an old view format). Current user is used as definer. Please recreate the view."

ER_PLUGIN_INIT_FAILED
  eng "Plugin '%s' init function returned error."

ER_RPL_TRX_DELEGATES_INIT_FAILED
  eng "Initialization of transaction delegates failed. Please report a bug."

ER_RPL_BINLOG_STORAGE_DELEGATES_INIT_FAILED
  eng "Initialization binlog storage delegates failed. Please report a bug."

ER_RPL_BINLOG_TRANSMIT_DELEGATES_INIT_FAILED
  eng "Initialization of binlog transmit delegates failed. Please report a bug."

ER_RPL_BINLOG_RELAY_DELEGATES_INIT_FAILED
  eng "Initialization binlog relay IO delegates failed. Please report a bug."

ER_RPL_PLUGIN_FUNCTION_FAILED
  eng "Run function '...' in plugin '%s' failed"

ER_SQL_HA_READ_FAILED
  eng "mysql_ha_read: Got error %d when reading table '%s'"

ER_SR_BOGUS_VALUE
  eng "Stored routine '%s'.'%s': invalid value in column %s."

ER_SR_INVALID_CONTEXT
  eng "Invalid creation context '%s.%s'."

ER_READING_TABLE_FAILED
  eng "Got error %d when reading table '%s'"

ER_DES_FILE_WRONG_KEY
  eng "load_des_file:  Found wrong key_number: %c"

OBSOLETE_ER_CANT_SET_PERSISTED
  eng "Failed to set persisted options."

ER_JSON_PARSE_ERROR
  eng "Persisted config file is corrupt. Please ensure mysqld-auto.cnf file is valid JSON."

ER_CONFIG_OPTION_WITHOUT_GROUP
  eng "Found option without preceding group in config file"

ER_VALGRIND_DO_QUICK_LEAK_CHECK
  eng "VALGRIND_DO_QUICK_LEAK_CHECK"

ER_VALGRIND_COUNT_LEAKS
  eng "VALGRIND_COUNT_LEAKS reports %lu leaked bytes for query '%.*s'"

ER_LOAD_DATA_INFILE_FAILED_IN_UNEXPECTED_WAY
  eng "LOAD DATA INFILE in the replica SQL Thread can only read from --replica-load-tmpdir. Please, report a bug."

ER_UNKNOWN_ERROR_NUMBER
  eng "Got unknown error: %d"

ER_UDF_CANT_ALLOC_FOR_STRUCTURES
  eng "Can't allocate memory for udf structures"

ER_UDF_CANT_ALLOC_FOR_FUNCTION
  eng "Can't alloc memory for udf function: '%.64s'"

ER_UDF_INVALID_ROW_IN_FUNCTION_TABLE
  eng "Invalid row in mysql.func table for function '%.64s'"

ER_UDF_CANT_OPEN_FUNCTION_TABLE
  eng "Could not open the mysql.func table. Please perform the MySQL upgrade procedure."

ER_XA_RECOVER_FOUND_TRX_IN_SE
  eng "Found %d prepared transaction(s) in %s"

ER_XA_RECOVER_FOUND_XA_TRX
  eng "Found %d prepared XA transactions"

OBSOLETE_ER_XA_IGNORING_XID
  eng "ignore xid %s"

OBSOLETE_ER_XA_COMMITTING_XID
  eng "commit xid %s"

OBSOLETE_ER_XA_ROLLING_BACK_XID
  eng "rollback xid %s"

ER_XA_STARTING_RECOVERY
  eng "Starting XA crash recovery..."

ER_XA_NO_MULTI_2PC_HEURISTIC_RECOVER
  eng "--tc-heuristic-recover rollback strategy is not safe on systems with more than one 2-phase-commit-capable storage engine. Aborting crash recovery."

ER_XA_RECOVER_EXPLANATION
  eng "Found %d prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or %s file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions."

ER_XA_RECOVERY_DONE
  eng "XA crash recovery finished."

ER_TRX_GTID_COLLECT_REJECT
  eng "Failed to collect GTID to send in the response packet!"

ER_SQL_AUTHOR_DEFAULT_ROLES_FAIL
  eng "MYSQL.DEFAULT_ROLES couldn't be updated for authorization identifier %s"

ER_SQL_USER_TABLE_CREATE_WARNING
  eng "Following users were specified in CREATE USER IF NOT EXISTS but they already exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %s"

ER_SQL_USER_TABLE_ALTER_WARNING
  eng "Following users were specified in ALTER USER IF EXISTS but they do not exist. Corresponding entry in binary log used default authentication plugin '%s' to rewrite authentication information (if any) for them: %s"

ER_ROW_IN_WRONG_PARTITION_PLEASE_REPAIR
  eng "Table '%-192s' corrupted: row in wrong partition: %s -- Please REPAIR the table!"

ER_MYISAM_CRASHED_ERROR_IN_THREAD
  eng "Got an error from thread_id=%u, %s:%d"

ER_MYISAM_CRASHED_ERROR_IN
  eng "Got an error from unknown thread, %s:%d"

ER_TOO_MANY_STORAGE_ENGINES
  eng "Too many storage engines!"

ER_SE_TYPECODE_CONFLICT
  eng "Storage engine '%s' has conflicting typecode. Assigning value %d."

ER_TRX_WRITE_SET_OOM
  eng "Out of memory on transaction write set extraction"

ER_HANDLERTON_OOM
  eng "Unable to allocate memory for plugin '%s' handlerton."

ER_CONN_SHM_LISTENER
  eng "Shared memory setting up listener"

ER_CONN_SHM_CANT_CREATE_SERVICE
  eng "Can't create shared memory service: %s. : %s"

ER_CONN_SHM_CANT_CREATE_CONNECTION
  eng "Can't create shared memory connection: %s. : %s"

ER_CONN_PIP_CANT_CREATE_EVENT
  eng "Can't create event, last error=%u"

ER_CONN_PIP_CANT_CREATE_PIPE
  eng "Can't create new named pipe!: %s"

ER_CONN_PER_THREAD_NO_THREAD
  eng "Can't create thread to handle new connection(errno= %d)"

ER_CONN_TCP_NO_SOCKET
  eng "Failed to create a socket for %s '%s': errno: %d."

ER_CONN_TCP_CREATED
  eng "Server socket created on IP: '%s'."

ER_CONN_TCP_ADDRESS
  eng "Server hostname (bind-address): '%s'; port: %d"

ER_CONN_TCP_IPV6_AVAILABLE
  eng "IPv6 is available."

ER_CONN_TCP_IPV6_UNAVAILABLE
  eng "IPv6 is not available."

ER_CONN_TCP_ERROR_WITH_STRERROR
  eng "Can't create IP socket: %s"

ER_CONN_TCP_CANT_RESOLVE_HOSTNAME
  eng "Can't start server: cannot resolve hostname!"

ER_CONN_TCP_IS_THERE_ANOTHER_USING_PORT
  eng "Do you already have another mysqld server running on port: %d ?"

ER_CONN_UNIX_IS_THERE_ANOTHER_USING_SOCKET
  eng "Do you already have another mysqld server running on socket: %s ?"

ER_CONN_UNIX_PID_CLAIMED_SOCKET_FILE
  eng "Another process with pid %d is using unix socket file."

ER_CONN_TCP_CANT_RESET_V6ONLY
  eng "Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only."

ER_CONN_TCP_BIND_RETRY
  eng "Retrying bind on TCP/IP port %u"

ER_CONN_TCP_BIND_FAIL
  eng "Can't start server: Bind on TCP/IP port: %s"

ER_CONN_TCP_IP_NOT_LOGGED
  eng "Fails to print out IP-address."

ER_CONN_TCP_RESOLVE_INFO
  eng "  - '%s' resolves to '%s';"

ER_CONN_TCP_START_FAIL
  eng "Can't start server: listen() on TCP/IP port: %s"

ER_CONN_TCP_LISTEN_FAIL
  eng "listen() on TCP/IP failed with error %d"

ER_CONN_UNIX_PATH_TOO_LONG
  eng "The socket file path is too long (> %u): %s"

ER_CONN_UNIX_LOCK_FILE_FAIL
  eng "Unable to setup unix socket lock file."

ER_CONN_UNIX_NO_FD
  eng "Can't start server: UNIX Socket : %s"

ER_CONN_UNIX_NO_BIND_NO_START
  eng "Can't start server : Bind on unix socket: %s"

ER_CONN_UNIX_LISTEN_FAILED
  eng "listen() on Unix socket failed with error %d"

ER_CONN_UNIX_LOCK_FILE_GIVING_UP
  eng "Unable to create unix socket lock file %s after retries."

ER_CONN_UNIX_LOCK_FILE_CANT_CREATE
  eng "Could not create unix socket lock file %s."

ER_CONN_UNIX_LOCK_FILE_CANT_OPEN
  eng "Could not open unix socket lock file %s."

ER_CONN_UNIX_LOCK_FILE_CANT_READ
  eng "Could not read unix socket lock file %s."

ER_CONN_UNIX_LOCK_FILE_EMPTY
  eng "Unix socket lock file is empty %s."

ER_CONN_UNIX_LOCK_FILE_PIDLESS
  eng "Invalid pid in unix socket lock file %s."

ER_CONN_UNIX_LOCK_FILE_CANT_WRITE
  eng "Could not write unix socket lock file %s errno %d."

ER_CONN_UNIX_LOCK_FILE_CANT_DELETE
  eng "Could not remove unix socket lock file %s errno %d."

ER_CONN_UNIX_LOCK_FILE_CANT_SYNC
  eng "Could not sync unix socket lock file %s errno %d."

ER_CONN_UNIX_LOCK_FILE_CANT_CLOSE
  eng "Could not close unix socket lock file %s errno %d."

ER_CONN_SOCKET_SELECT_FAILED
  eng "mysqld: Got error %d from select"

ER_CONN_SOCKET_ACCEPT_FAILED
  eng "Error in accept: %s"

ER_AUTH_RSA_CANT_FIND
  eng "RSA %s key file not found: %s. Some authentication plugins will not work."

ER_AUTH_RSA_CANT_PARSE
  eng "Failure to parse RSA %s key (file exists): %s: %s"

ER_AUTH_RSA_CANT_READ
  eng "Failure to read key file: %s"

ER_AUTH_RSA_FILES_NOT_FOUND
  eng "RSA key files not found. Some authentication plugins will not work."

ER_CONN_ATTR_TRUNCATED
  eng "Connection attributes of length %lu were truncated (%d bytes lost) for connection %llu, user %s@%s (as %s), auth: %s"

ER_X509_CIPHERS_MISMATCH
  eng "X.509 ciphers mismatch: should be '%s' but is '%s'"

ER_X509_ISSUER_MISMATCH
  eng "X.509 issuer mismatch: should be '%s' but is '%s'"

ER_X509_SUBJECT_MISMATCH
  eng "X.509 subject mismatch: should be '%s' but is '%s'"

ER_AUTH_CANT_ACTIVATE_ROLE
  eng "Failed to activate default role %s for %s"

ER_X509_NEEDS_RSA_PRIVKEY
  eng "Could not generate RSA private key required for X.509 certificate."

ER_X509_CANT_WRITE_KEY
  eng "Could not write key file: %s"

ER_X509_CANT_CHMOD_KEY
  eng "Could not set file permission for %s"

ER_X509_CANT_READ_CA_KEY
  eng "Could not read CA key file: %s"

ER_X509_CANT_READ_CA_CERT
  eng "Could not read CA certificate file: %s"

ER_X509_CANT_CREATE_CERT
  eng "Could not generate X.509 certificate."

ER_X509_CANT_WRITE_CERT
  eng "Could not write certificate file: %s"

ER_AUTH_CANT_CREATE_RSA_PAIR
  eng "Could not generate RSA Private/Public key pair"

ER_AUTH_CANT_WRITE_PRIVKEY
  eng "Could not write private key file: %s"

ER_AUTH_CANT_WRITE_PUBKEY
  eng "Could not write public key file: %s"

ER_AUTH_SSL_CONF_PREVENTS_CERT_GENERATION
  eng "Skipping generation of SSL certificates as options related to SSL are specified."

ER_AUTH_USING_EXISTING_CERTS
  eng "Skipping generation of SSL certificates as certificate files are present in data directory."

ER_AUTH_CERTS_SAVED_TO_DATADIR
  eng "Auto generated SSL certificates are placed in data directory."

ER_AUTH_CERT_GENERATION_DISABLED
  eng "Skipping generation of SSL certificates as --auto_generate_certs is set to OFF."

ER_AUTH_RSA_CONF_PREVENTS_KEY_GENERATION
  eng "Skipping generation of RSA key pair through %s as options related to RSA keys are specified."

ER_AUTH_KEY_GENERATION_SKIPPED_PAIR_PRESENT
  eng "Skipping generation of RSA key pair through %s as key files are present in data directory."

ER_AUTH_KEYS_SAVED_TO_DATADIR
  eng "Auto generated RSA key files through %s are placed in data directory."

ER_AUTH_KEY_GENERATION_DISABLED
  eng "Skipping generation of RSA key pair as %s is set to OFF."

ER_AUTHCACHE_PROXIES_PRIV_SKIPPED_NEEDS_RESOLVE
  eng "'proxies_priv' entry '%s@%s %s@%s' ignored in --skip-name-resolve mode."

ER_AUTHCACHE_PLUGIN_MISSING
  eng "The plugin '%.*s' used to authenticate user '%s'@'%.*s' is not loaded. Nobody can currently login using this account."

ER_AUTHCACHE_PLUGIN_CONFIG
  eng "The plugin '%s' is used to authenticate user '%s'@'%.*s', %s configured. Nobody can currently login using this account."

OBSOLETE_ER_AUTHCACHE_ROLE_TABLES_DODGY
  eng "Could not load mysql.role_edges and mysql.default_roles tables. ACL DDLs will not work unless the MySQL upgrade procedure is performed."

ER_AUTHCACHE_USER_SKIPPED_NEEDS_RESOLVE
  eng "'user' entry '%s@%s' ignored in --skip-name-resolve mode."

ER_AUTHCACHE_USER_TABLE_DODGY
  eng "Fatal error: Could not read the column 'authentication_string' from table 'mysql.user'. Please perform the MySQL upgrade procedure."

ER_AUTHCACHE_USER_IGNORED_DEPRECATED_PASSWORD
  eng "User entry '%s'@'%s' has a deprecated pre-4.1 password. The user will be ignored and no one can login with this user anymore."

ER_AUTHCACHE_USER_IGNORED_NEEDS_PLUGIN
  eng "User entry '%s'@'%s' has an empty plugin value. The user will be ignored and no one can login with this user anymore."

ER_AUTHCACHE_USER_IGNORED_INVALID_PASSWORD
  eng "Found invalid password for user: '%s@%s'; Ignoring user"

ER_AUTHCACHE_EXPIRED_PASSWORD_UNSUPPORTED
  eng "'user' entry '%s@%s' has the password ignore flag raised, but its authentication plugin doesn't support password expiration. The user id will be ignored."

ER_NO_SUPER_WITHOUT_USER_PLUGIN
  eng "Some of the user accounts with SUPER privileges were disabled because of empty mysql.user.plugin value. If you are upgrading from MySQL 5.6 to MySQL 5.7 it means that substitution for the empty plugin column was not possible. Probably because of pre 4.1 password hash. If your account is disabled you will need to perform the MySQL upgrade procedure. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual."

ER_AUTHCACHE_DB_IGNORED_EMPTY_NAME
  eng "Found an entry in the 'db' table with empty database name; Skipped"

ER_AUTHCACHE_DB_SKIPPED_NEEDS_RESOLVE
  eng "'db' entry '%s %s@%s' ignored in --skip-name-resolve mode."

ER_AUTHCACHE_DB_ENTRY_LOWERCASED_REVOKE_WILL_FAIL
  eng "'db' entry '%s %s@%s' had database in mixed case that has been forced to lowercase because lower_case_table_names is set. It will not be possible to remove this privilege using REVOKE."

ER_AUTHCACHE_TABLE_PROXIES_PRIV_MISSING
  eng "The system table mysql.proxies_priv is missing. Please perform the MySQL upgrade procedure."

ER_AUTHCACHE_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
  eng "Fatal error: Can't open and lock privilege tables: %s"

ER_AUTHCACHE_CANT_INIT_GRANT_SUBSYSTEM
  eng "Fatal: can't initialize grant subsystem - '%s'"

ER_AUTHCACHE_PROCS_PRIV_SKIPPED_NEEDS_RESOLVE
  eng "'procs_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode."

ER_AUTHCACHE_PROCS_PRIV_ENTRY_IGNORED_BAD_ROUTINE_TYPE
  eng "'procs_priv' entry '%s' ignored, bad routine type"

ER_AUTHCACHE_TABLES_PRIV_SKIPPED_NEEDS_RESOLVE
  eng "'tables_priv' entry '%s %s@%s' ignored in --skip-name-resolve mode."

ER_USER_NOT_IN_EXTRA_USERS_BINLOG_POSSIBLY_INCOMPLETE
  eng "Failed to add %s in extra_users. Binary log entry may miss some of the users."

ER_DD_SCHEMA_NOT_FOUND
  eng "Unable to start server. The data dictionary schema '%s' does not exist."

ER_DD_TABLE_NOT_FOUND
  eng "Unable to start server. The data dictionary table '%s' does not exist."

ER_DD_SE_INIT_FAILED
  eng "Failed to initialize DD Storage Engine"

ER_DD_ABORTING_PARTIAL_UPGRADE
  eng "Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again."

ER_DD_FRM_EXISTS_FOR_TABLE
  eng "Found .frm file with same name as one of the Dictionary Tables."

ER_DD_CREATED_FOR_UPGRADE
  eng "Created Data Dictionary for upgrade"

ER_ERRMSG_CANT_FIND_FILE
  eng "Can't find error-message file '%s'. Check error-message file location and 'lc-messages-dir' configuration directive."

ER_ERRMSG_LOADING_55_STYLE
  eng "Using pre 5.5 semantics to load error messages from %s. If this is not intended, refer to the documentation for valid usage of --lc-messages-dir and --language parameters."

ER_ERRMSG_MISSING_IN_FILE
  eng "Error message file '%s' had only %d error messages, but it should contain at least %d error messages. Check that the above file is the right version for this program!"

ER_ERRMSG_OOM
  eng "Not enough memory for messagefile '%s'"

ER_ERRMSG_CANT_READ
  eng "Can't read from messagefile '%s'"

ER_TABLE_INCOMPATIBLE_DECIMAL_FIELD
  eng "Found incompatible DECIMAL field '%s' in %s; Please do \"ALTER TABLE `%s` FORCE\" to fix it!"

ER_TABLE_INCOMPATIBLE_YEAR_FIELD
  eng "Found incompatible YEAR(x) field '%s' in %s; Please do \"ALTER TABLE `%s` FORCE\" to fix it!"

ER_INVALID_CHARSET_AND_DEFAULT_IS_MB
  eng "'%s' had no or invalid character set, and default character set is multi-byte, so character column sizes may have changed"

ER_TABLE_WRONG_KEY_DEFINITION
  eng "Found wrong key definition in %s; Please do \"ALTER TABLE `%s` FORCE \" to fix it!"

ER_CANT_OPEN_FRM_FILE
  eng "Unable to open file %s"

ER_CANT_READ_FRM_FILE
  eng "Error in reading file %s"

ER_TABLE_CREATED_WITH_DIFFERENT_VERSION
  eng "Table '%s' was created with a different version of MySQL and cannot be read"

ER_VIEW_UNPARSABLE
  eng "Unable to read view %s"

ER_FILE_TYPE_UNKNOWN
  eng "File %s has unknown type in its header."

ER_INVALID_INFO_IN_FRM
  eng "Incorrect information in file %s"

ER_CANT_OPEN_AND_LOCK_PRIVILEGE_TABLES
  eng "Can't open and lock privilege tables: %s"

ER_AUDIT_PLUGIN_DOES_NOT_SUPPORT_AUDIT_AUTH_EVENTS
  eng "Plugin '%s' cannot subscribe to MYSQL_AUDIT_AUTHORIZATION events. Currently not supported."

ER_AUDIT_PLUGIN_HAS_INVALID_DATA
  eng "Plugin '%s' has invalid data."

ER_TZ_OOM_INITIALIZING_TIME_ZONES
  eng "Fatal error: OOM while initializing time zones"

ER_TZ_CANT_OPEN_AND_LOCK_TIME_ZONE_TABLE
  eng "Can't open and lock time zone table: %s trying to live without them"

ER_TZ_OOM_LOADING_LEAP_SECOND_TABLE
  eng "Fatal error: Out of memory while loading mysql.time_zone_leap_second table"

ER_TZ_TOO_MANY_LEAPS_IN_LEAP_SECOND_TABLE
  eng "Fatal error: While loading mysql.time_zone_leap_second table: too much leaps"

ER_TZ_ERROR_LOADING_LEAP_SECOND_TABLE
  eng "Fatal error: Error while loading mysql.time_zone_leap_second table"

ER_TZ_UNKNOWN_OR_ILLEGAL_DEFAULT_TIME_ZONE
  eng "Fatal error: Illegal or unknown default time zone '%s'"

ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE
  eng "Can't find description of time zone '%.*s'"

ER_TZ_CANT_FIND_DESCRIPTION_FOR_TIME_ZONE_ID
  eng "Can't find description of time zone '%u'"

ER_TZ_TRANSITION_TYPE_TABLE_TYPE_TOO_LARGE
  eng "Error while loading time zone description from mysql.time_zone_transition_type table: too big transition type id"

ER_TZ_TRANSITION_TYPE_TABLE_ABBREVIATIONS_EXCEED_SPACE
  eng "Error while loading time zone description from mysql.time_zone_transition_type table: not enough room for abbreviations"

ER_TZ_TRANSITION_TYPE_TABLE_LOAD_ERROR
  eng "Error while loading time zone description from mysql.time_zone_transition_type table"

ER_TZ_TRANSITION_TABLE_TOO_MANY_TRANSITIONS
  eng "Error while loading time zone description from mysql.time_zone_transition table: too much transitions"

ER_TZ_TRANSITION_TABLE_BAD_TRANSITION_TYPE
  eng "Error while loading time zone description from mysql.time_zone_transition table: bad transition type id"

ER_TZ_TRANSITION_TABLE_LOAD_ERROR
  eng "Error while loading time zone description from mysql.time_zone_transition table"

ER_TZ_NO_TRANSITION_TYPES_IN_TIME_ZONE
  eng "loading time zone without transition types"

ER_TZ_OOM_LOADING_TIME_ZONE_DESCRIPTION
  eng "Out of memory while loading time zone description"

ER_TZ_CANT_BUILD_MKTIME_MAP
  eng "Unable to build mktime map for time zone"

ER_TZ_OOM_WHILE_LOADING_TIME_ZONE
  eng "Out of memory while loading time zone"

ER_TZ_OOM_WHILE_SETTING_TIME_ZONE
  eng "Fatal error: Out of memory while setting new time zone"

ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_CONDITION_BAD
  eng "Replica SQL thread is stopped because UNTIL condition is bad(%s:%llu)."

ER_REPLICA_SQL_THREAD_STOPPED_UNTIL_POSITION_REACHED
  eng "Replica SQL thread stopped because it reached its UNTIL position %llu"

ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_ALREADY_APPLIED
  eng "Replica SQL thread stopped because UNTIL SQL_BEFORE_GTIDS %s is already applied"

ER_REPLICA_SQL_THREAD_STOPPED_BEFORE_GTIDS_REACHED
  eng "Replica SQL thread stopped because it reached UNTIL SQL_BEFORE_GTIDS %s"

ER_REPLICA_SQL_THREAD_STOPPED_AFTER_GTIDS_REACHED
  eng "Replica SQL thread stopped because it reached UNTIL SQL_AFTER_GTIDS %s"

ER_REPLICA_SQL_THREAD_STOPPED_GAP_TRX_PROCESSED
  eng "Replica SQL thread stopped according to UNTIL SQL_AFTER_MTS_GAPS as it has processed all gap transactions left from the previous replica session."

ER_GROUP_REPLICATION_PLUGIN_NOT_INSTALLED
  eng "Group Replication plugin is not installed."

ER_GTID_ALREADY_ADDED_BY_USER
  eng "The transaction owned GTID is already in the %s table, which is caused by an explicit modifying from user client."

ER_FAILED_TO_DELETE_FROM_GTID_EXECUTED_TABLE
  eng "Failed to delete the row: '%s' from the gtid_executed table."

ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE
  eng "Failed to compress the gtid_executed table."

ER_FAILED_TO_COMPRESS_GTID_EXECUTED_TABLE_OOM
  eng "Failed to compress the gtid_executed table, because it is failed to allocate the THD."

ER_FAILED_TO_INIT_THREAD_ATTR_FOR_GTID_TABLE_COMPRESSION
  eng "Failed to initialize thread attribute when creating compression thread."

ER_FAILED_TO_CREATE_GTID_TABLE_COMPRESSION_THREAD
  eng "Can not create thread to compress gtid_executed table (errno= %d)"

ER_FAILED_TO_JOIN_GTID_TABLE_COMPRESSION_THREAD
  eng "Could not join gtid_executed table compression thread. error:%d"

ER_NPIPE_FAILED_TO_INIT_SECURITY_DESCRIPTOR
  eng "Can't start server : Initialize security descriptor: %s"

ER_NPIPE_FAILED_TO_SET_SECURITY_DESCRIPTOR
  eng "Can't start server : Set security descriptor: %s"

ER_NPIPE_PIPE_ALREADY_IN_USE
  eng "Can't start server : Named Pipe \"%s\" already in use."

OBSOLETE_ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS_ON_START
  eng "NDB Replica : At SQL thread start applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu.  Check replica positioning."

OBSOLETE_ER_NDB_SLAVE_SAW_EPOCH_LOWER_THAN_PREVIOUS
  eng "NDB Replica : SQL thread stopped as applying epoch %llu/%llu (%llu) from Source ServerId %u which is lower than previously applied epoch %llu/%llu (%llu).  Group Source Log : %s  Group Source Log Pos : %llu"

OBSOLETE_ER_NDB_SLAVE_SAW_ALREADY_COMMITTED_EPOCH
  eng "NDB Replica : SQL thread stopped as attempted to reapply already committed epoch %llu/%llu (%llu) from server id %u.  Group Source Log : %s  Group Source Log Pos : %llu."

OBSOLETE_ER_NDB_SLAVE_PREVIOUS_EPOCH_NOT_COMMITTED
  eng "NDB Replica : SQL thread stopped as attempting to apply new epoch %llu/%llu (%llu) while lower received epoch %llu/%llu (%llu) has not been committed.  Source server id : %u.  Group Source Log : %s  Group Source Log Pos : %llu."

OBSOLETE_ER_NDB_SLAVE_MISSING_DATA_FOR_TIMESTAMP_COLUMN
  eng "NDB Replica: missing data for %s timestamp column %u."

OBSOLETE_ER_NDB_SLAVE_LOGGING_EXCEPTIONS_TO
  eng "NDB Replica: Table %s.%s logging exceptions to %s.%s"

OBSOLETE_ER_NDB_SLAVE_LOW_EPOCH_RESOLUTION
  eng "NDB Replica: Table %s.%s : %s, low epoch resolution"

OBSOLETE_ER_NDB_INFO_FOUND_UNEXPECTED_FIELD_TYPE
  eng "Found unexpected field type %u"

OBSOLETE_ER_NDB_INFO_FAILED_TO_CREATE_NDBINFO
  eng "Failed to create NdbInfo"

OBSOLETE_ER_NDB_INFO_FAILED_TO_INIT_NDBINFO
  eng "Failed to init NdbInfo"

OBSOLETE_ER_NDB_CLUSTER_WRONG_NUMBER_OF_FUNCTION_ARGUMENTS
  eng "ndb_serialize_cond: Unexpected mismatch of found and expected number of function arguments %u"

OBSOLETE_ER_NDB_CLUSTER_SCHEMA_INFO
  eng "%s - %s.%s"

OBSOLETE_ER_NDB_CLUSTER_GENERIC_MESSAGE
  eng "%s"

ER_RPL_CANT_OPEN_INFO_TABLE
  eng "Info table is not ready to be used. Table '%s.%s' cannot be opened."

ER_RPL_CANT_SCAN_INFO_TABLE
  eng "Info table is not ready to be used. Table '%s.%s' cannot be scanned."

ER_RPL_CORRUPTED_INFO_TABLE
  eng "Corrupted table %s.%s. Check out table definition."

ER_RPL_CORRUPTED_KEYS_IN_INFO_TABLE
  eng "Info table has a problem with its key field(s). Table '%s.%s' expected field #%u to be '%s' but found '%s' instead."

ER_RPL_WORKER_ID_IS
  eng "Choosing worker id %lu, the following is going to be %lu"

ER_RPL_INCONSISTENT_TIMESTAMPS_IN_TRX
  eng "Transaction is tagged with inconsistent logical timestamps: sequence_number (%lld) <= last_committed (%lld)"

ER_RPL_INCONSISTENT_SEQUENCE_NO_IN_TRX
  eng "Transaction's sequence number is inconsistent with that of a preceding one: sequence_number (%lld) <= previous sequence_number (%lld)"

ER_RPL_CHANNELS_REQUIRE_TABLES_AS_INFO_REPOSITORIES
  eng "For the creation of replication channels the connection metadata and applier metadata repositories must be set to TABLE"

ER_RPL_CHANNELS_REQUIRE_NON_ZERO_SERVER_ID
  eng "For the creation of replication channels the server id must be different from 0"

ER_RPL_REPO_SHOULD_BE_TABLE
  eng "Replica: Wrong repository. Repository should be TABLE"

ER_RPL_ERROR_CREATING_CONNECTION_METADATA
  eng "Error creating connection metadata: %s."

ER_RPL_ERROR_CHANGING_CONNECTION_METADATA_REPO_TYPE
  eng "Error changing the type of connection metadata's repository: %s."

ER_RPL_CHANGING_APPLIER_METADATA_REPO_TYPE_FAILED_DUE_TO_GAPS
  eng "It is not possible to change the type of the relay log repository because there are workers repositories with possible execution gaps. The value of --relay_log_info_repository is altered to one of the found Worker repositories. The gaps have to be sorted out before resuming with the type change."

ER_RPL_ERROR_CREATING_APPLIER_METADATA
  eng "Error creating applier metadata: %s."

ER_RPL_ERROR_CHANGING_APPLIER_METADATA_REPO_TYPE
  eng "Error changing the type of applier metadata's repository: %s."

ER_RPL_FAILED_TO_DELETE_FROM_REPLICA_WORKERS_INFO_REPOSITORY
  eng "Could not delete from Replica Workers info repository."

ER_RPL_FAILED_TO_RESET_STATE_IN_REPLICA_INFO_REPOSITORY
  eng "Could not store the reset Replica Worker state into the replica info repository."

ER_RPL_ERROR_CHECKING_REPOSITORY
  eng "Error in checking %s repository info type of %s."

ER_RPL_REPLICA_GENERIC_MESSAGE
  eng "Replica: %s"

ER_RPL_REPLICA_COULD_NOT_CREATE_CHANNEL_LIST
  eng "Replica: Could not create channel list"

ER_RPL_MULTISOURCE_REQUIRES_TABLE_TYPE_REPOSITORIES
  eng "Replica: This replica was a multisourced replica previously which is supported only by both TABLE based connection metadata and applier metadata repositories. Found one or both of the info repos to be type FILE. Set both repos to type TABLE."

ER_RPL_REPLICA_FAILED_TO_INIT_A_CONNECTION_METADATA_STRUCTURE
  eng "Replica: Failed to initialize the connection metadata structure for channel '%s'; its record may still be present in the applier metadata repository, consider deleting it."

ER_RPL_REPLICA_FAILED_TO_INIT_CONNECTION_METADATA_STRUCTURE
  eng "Failed to initialize the connection metadata structure%s"

ER_RPL_REPLICA_FAILED_TO_CREATE_CHANNEL_FROM_CONNECTION_METADATA
  eng "Replica: Failed to create a channel from connection metadata repository."

ER_RPL_FAILED_TO_CREATE_NEW_INFO_FILE
  eng "Failed to create a new info file (file '%s', errno %d)"

ER_RPL_FAILED_TO_CREATE_CACHE_FOR_INFO_FILE
  eng "Failed to create a cache on info file (file '%s')"

ER_RPL_FAILED_TO_OPEN_INFO_FILE
  eng "Failed to open the existing info file (file '%s', errno %d)"

ER_RPL_GTID_MEMORY_FINALLY_AVAILABLE
  eng "Server overcomes the temporary 'out of memory' in '%d' tries while allocating a new chunk of intervals for storing GTIDs."

ER_SERVER_COST_UNKNOWN_COST_CONSTANT
  eng "Unknown cost constant \"%s\" in mysql.server_cost table"

ER_SERVER_COST_INVALID_COST_CONSTANT
  eng "Invalid value for cost constant \"%s\" in mysql.server_cost table: %.1f"

ER_ENGINE_COST_UNKNOWN_COST_CONSTANT
  eng "Unknown cost constant \"%s\" in mysql.engine_cost table"

ER_ENGINE_COST_UNKNOWN_STORAGE_ENGINE
  eng "Unknown storage engine \"%s\" in mysql.engine_cost table"

ER_ENGINE_COST_INVALID_DEVICE_TYPE_FOR_SE
  eng "Invalid device type %d for \"%s\" storage engine for cost constant \"%s\" in mysql.engine_cost table"

ER_ENGINE_COST_INVALID_CONST_CONSTANT_FOR_SE_AND_DEVICE
  eng "Invalid value for cost constant \"%s\" for \"%s\" storage engine and device type %d in mysql.engine_cost table: %.1f"

ER_SERVER_COST_FAILED_TO_READ
  eng "Error while reading from mysql.server_cost table."

ER_ENGINE_COST_FAILED_TO_READ
  eng "Error while reading from mysql.engine_cost table."

ER_FAILED_TO_OPEN_COST_CONSTANT_TABLES
  eng "Failed to open optimizer cost constant tables"

ER_RPL_UNSUPPORTED_UNIGNORABLE_EVENT_IN_STREAM
  eng "Unsupported non-ignorable event fed into the event stream."

ER_RPL_GTID_LOG_EVENT_IN_STREAM
  eng "GTID_LOG_EVENT or ANONYMOUS_GTID_LOG_EVENT is not expected in an event stream %s."

ER_RPL_UNEXPECTED_BEGIN_IN_STREAM
  eng "QUERY(BEGIN) is not expected in an event stream in the middle of a %s."

ER_RPL_UNEXPECTED_COMMIT_ROLLBACK_OR_XID_LOG_EVENT_IN_STREAM
  eng "QUERY(COMMIT or ROLLBACK) or XID_LOG_EVENT is not expected in an event stream %s."

ER_RPL_UNEXPECTED_XA_ROLLBACK_IN_STREAM
  eng "QUERY(XA ROLLBACK) is not expected in an event stream %s."

ER_EVENT_EXECUTION_FAILED_CANT_AUTHENTICATE_USER
  eng "Event Scheduler: [%s].[%s.%s] execution failed, failed to authenticate the user."

ER_EVENT_EXECUTION_FAILED_USER_LOST_EVEN_PRIVILEGE
  eng "Event Scheduler: [%s].[%s.%s] execution failed, user no longer has EVENT privilege."

ER_EVENT_ERROR_DURING_COMPILATION
  eng "Event Scheduler: %serror during compilation of %s.%s"

ER_EVENT_DROPPING
  eng "Event Scheduler: Dropping %s.%s"

OBSOLETE_ER_NDB_SCHEMA_GENERIC_MESSAGE
  eng "Ndb schema[%s.%s]: %s"

ER_RPL_INCOMPATIBLE_DECIMAL_IN_RBR
  eng "In RBR mode, Replica received incompatible DECIMAL field (old-style decimal field) from Source while creating conversion table. Please consider changing datatype on Source to new style decimal by executing ALTER command for column Name: %s.%s.%s."

ER_INIT_ROOT_WITHOUT_PASSWORD
  eng "root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option."

ER_INIT_GENERATING_TEMP_PASSWORD_FOR_ROOT
  eng "A temporary password is generated for root@localhost: %s"

ER_INIT_CANT_OPEN_BOOTSTRAP_FILE
  eng "Failed to open the bootstrap file %s"

ER_INIT_BOOTSTRAP_COMPLETE
  eng "Bootstrapping complete"

ER_INIT_DATADIR_NOT_EMPTY_WONT_INITIALIZE
  eng "--initialize specified but the data directory has files in it. Aborting."

ER_INIT_DATADIR_EXISTS_WONT_INITIALIZE
  eng "--initialize specified on an existing data directory."

ER_INIT_DATADIR_EXISTS_AND_PATH_TOO_LONG_WONT_INITIALIZE
  eng "--initialize specified but the data directory exists and the path is too long. Aborting."

ER_INIT_DATADIR_EXISTS_AND_NOT_WRITABLE_WONT_INITIALIZE
  eng "--initialize specified but the data directory exists and is not writable. Aborting."

ER_INIT_CREATING_DD
  eng "Creating the data directory %s"

ER_RPL_BINLOG_STARTING_DUMP
  eng "Start binlog_dump to source_thread_id(%u) replica_server(%u), pos(%s, %llu)"

ER_RPL_BINLOG_SOURCE_SENDS_HEARTBEAT
  eng "source sends heartbeat message"

ER_RPL_BINLOG_SKIPPING_REMAINING_HEARTBEAT_INFO
  eng "the rest of heartbeat info skipped ..."

ER_RPL_BINLOG_SOURCE_USES_CHECKSUM_AND_REPLICA_CANT
  eng "Source is configured to log replication events with checksum, but will not send such events to replicas that cannot process them"

OBSOLETE_ER_NDB_QUERY_FAILED
  eng "NDB: Query '%s' failed, error: %d: %s"

ER_KILLING_THREAD
  eng "Killing thread %lu"

ER_DETACHING_SESSION_LEFT_BY_PLUGIN
  eng "Plugin %s is deinitializing a thread but left a session attached. Detaching it forcefully."

ER_CANT_DETACH_SESSION_LEFT_BY_PLUGIN
  eng "Failed to detach the session."

ER_DETACHED_SESSIONS_LEFT_BY_PLUGIN
  eng "Closed forcefully %u session%s left opened by plugin %s"

ER_FAILED_TO_DECREMENT_NUMBER_OF_THREADS
  eng "Failed to decrement the number of threads"

ER_PLUGIN_DID_NOT_DEINITIALIZE_THREADS
  eng "Plugin %s did not deinitialize %u threads"

ER_KILLED_THREADS_OF_PLUGIN
  eng "Killed %u threads of plugin %s"

OBSOLETE_ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_UNKNOWN
  eng "NDB Replica : Could not determine maximum replicated epoch from %s.%s at Replica start, error %u %s"

OBSOLETE_ER_NDB_SLAVE_MAX_REPLICATED_EPOCH_SET_TO
  eng "NDB Replica : MaxReplicatedEpoch set to %llu (%u/%u) at Replica start"

OBSOLETE_ER_NDB_NODE_ID_AND_MANAGEMENT_SERVER_INFO
  eng "NDB: NodeID is %lu, management server '%s:%lu'"

OBSOLETE_ER_NDB_DISCONNECT_INFO
  eng "tid %u: node[%u] transaction_hint=%u, transaction_no_hint=%u"

OBSOLETE_ER_NDB_COLUMN_DEFAULTS_DIFFER
  eng "NDB Internal error: Default values differ for column %u, ndb_default: %d"

OBSOLETE_ER_NDB_COLUMN_SHOULD_NOT_HAVE_NATIVE_DEFAULT
  eng "NDB Internal error: Column %u has native default, but shouldn't. Flags=%u, type=%u"

OBSOLETE_ER_NDB_FIELD_INFO
  eng "field[ name: '%s', type: %u, real_type: %u, flags: 0x%x, is_null: %d]"

OBSOLETE_ER_NDB_COLUMN_INFO
  eng "ndbCol[name: '%s', type: %u, column_no: %d, nullable: %d]"

OBSOLETE_ER_NDB_OOM_IN_FIX_UNIQUE_INDEX_ATTR_ORDER
  eng "fix_unique_index_attr_order: my_malloc(%u) failure"

OBSOLETE_ER_NDB_SLAVE_MALFORMED_EVENT_RECEIVED_ON_TABLE
  eng "NDB Replica : Malformed event received on table %s cannot parse.  Stopping Replica."

OBSOLETE_ER_NDB_SLAVE_CONFLICT_FUNCTION_REQUIRES_ROLE
  eng "NDB Replica : Conflict function %s defined on table %s requires ndb_replica_conflict_role variable to be set.  Stopping replica."

OBSOLETE_ER_NDB_SLAVE_CONFLICT_TRANSACTION_IDS
  eng "NDB Replica : Transactional conflict detection defined on table %s, but events received without transaction ids.  Check --ndb-log-transaction-id setting on upstream Cluster."

OBSOLETE_ER_NDB_SLAVE_BINLOG_MISSING_INFO_FOR_CONFLICT_DETECTION
  eng "NDB Replica : Binlog event on table %s missing info necessary for conflict detection.  Check binlog format options on upstream cluster."

OBSOLETE_ER_NDB_ERROR_IN_READAUTOINCREMENTVALUE
  eng "Error %lu in readAutoIncrementValue(): %s"

OBSOLETE_ER_NDB_FOUND_UNCOMMITTED_AUTOCOMMIT
  eng "found uncommitted autocommit+rbwr transaction, commit status: %d"

OBSOLETE_ER_NDB_SLAVE_TOO_MANY_RETRIES
  eng "Ndb replica retried transaction %u time(s) in vain.  Giving up."

OBSOLETE_ER_NDB_SLAVE_ERROR_IN_UPDATE_CREATE_INFO
  eng "Error %lu in ::update_create_info(): %s"

OBSOLETE_ER_NDB_SLAVE_CANT_ALLOCATE_TABLE_SHARE
  eng "NDB: allocating table share for %s failed"

OBSOLETE_ER_NDB_BINLOG_ERROR_INFO_FROM_DA
  eng "NDB Binlog: (%d)%s"

OBSOLETE_ER_NDB_BINLOG_CREATE_TABLE_EVENT
  eng "NDB Binlog: CREATE TABLE Event: %s"

OBSOLETE_ER_NDB_BINLOG_FAILED_CREATE_TABLE_EVENT_OPERATIONS
  eng "NDB Binlog: FAILED CREATE TABLE event operations. Event: %s"

OBSOLETE_ER_NDB_BINLOG_RENAME_EVENT
  eng "NDB Binlog: RENAME Event: %s"

OBSOLETE_ER_NDB_BINLOG_FAILED_CREATE_DURING_RENAME
  eng "NDB Binlog: FAILED create event operations during RENAME. Event %s"

OBSOLETE_ER_NDB_UNEXPECTED_RENAME_TYPE
  eng "Unexpected rename case detected, sql_command: %d"

OBSOLETE_ER_NDB_ERROR_IN_GET_AUTO_INCREMENT
  eng "Error %lu in ::get_auto_increment(): %s"

OBSOLETE_ER_NDB_CREATING_SHARE_IN_OPEN
  eng "Calling ndbcluster_create_binlog_setup(%s) in ::open"

OBSOLETE_ER_NDB_TABLE_OPENED_READ_ONLY
  eng "table '%s' opened read only"

OBSOLETE_ER_NDB_INITIALIZE_GIVEN_CLUSTER_PLUGIN_DISABLED
  eng "NDB: '--initialize' -> ndbcluster plugin disabled"

OBSOLETE_ER_NDB_BINLOG_FORMAT_CHANGED_FROM_STMT_TO_MIXED
  eng "NDB: Changed global value of binlog_format from STATEMENT to MIXED"

OBSOLETE_ER_NDB_TRAILING_SHARE_RELEASED_BY_CLOSE_CACHED_TABLES
  eng "NDB_SHARE: trailing share %s, released by close_cached_tables"

OBSOLETE_ER_NDB_SHARE_ALREADY_EXISTS
  eng "NDB_SHARE: %s already exists use_count=%d. Moving away for safety, but possible memleak."

OBSOLETE_ER_NDB_HANDLE_TRAILING_SHARE_INFO
  eng "handle_trailing_share: %s use_count: %u"

OBSOLETE_ER_NDB_CLUSTER_GET_SHARE_INFO
  eng "ndbcluster_get_share: %s use_count: %u"

OBSOLETE_ER_NDB_CLUSTER_REAL_FREE_SHARE_INFO
  eng "ndbcluster_real_free_share: %s use_count: %u"

OBSOLETE_ER_NDB_CLUSTER_REAL_FREE_SHARE_DROP_FAILED
  eng "ndbcluster_real_free_share: %s, still open - ignored 'free' (leaked?)"

OBSOLETE_ER_NDB_CLUSTER_FREE_SHARE_INFO
  eng "ndbcluster_free_share: %s use_count: %u"

OBSOLETE_ER_NDB_CLUSTER_MARK_SHARE_DROPPED_INFO
  eng "ndbcluster_mark_share_dropped: %s use_count: %u"

OBSOLETE_ER_NDB_CLUSTER_MARK_SHARE_DROPPED_DESTROYING_SHARE
  eng "ndbcluster_mark_share_dropped: destroys share %s"

OBSOLETE_ER_NDB_CLUSTER_OOM_THD_NDB
  eng "Could not allocate Thd_ndb object"

OBSOLETE_ER_NDB_BINLOG_NDB_TABLES_INITIALLY_READ_ONLY
  eng "NDB Binlog: Ndb tables initially read only."

OBSOLETE_ER_NDB_UTIL_THREAD_OOM
  eng "ndb util thread: malloc failure, query cache not maintained properly"

OBSOLETE_ER_NDB_ILLEGAL_VALUE_FOR_NDB_RECV_THREAD_CPU_MASK
  eng "Trying to set ndb_recv_thread_cpu_mask to illegal value = %s, ignored"

OBSOLETE_ER_NDB_TOO_MANY_CPUS_IN_NDB_RECV_THREAD_CPU_MASK
  eng "Trying to set too many CPU's in ndb_recv_thread_cpu_mask, ignored this variable, erroneus value = %s"

ER_DBUG_CHECK_SHARES_OPEN
  eng "dbug_check_shares open:"

ER_DBUG_CHECK_SHARES_INFO
  eng "  %s.%s: state: %s(%u) use_count: %u"

ER_DBUG_CHECK_SHARES_DROPPED
  eng "dbug_check_shares dropped:"

ER_INVALID_OR_OLD_TABLE_OR_DB_NAME
  eng "Invalid (old?) table or database name '%s'"

ER_TC_RECOVERING_AFTER_CRASH_USING
  eng "Recovering after a crash using %s"

ER_TC_CANT_AUTO_RECOVER_WITH_TC_HEURISTIC_RECOVER
  eng "Cannot perform automatic crash recovery when --tc-heuristic-recover is used"

ER_TC_BAD_MAGIC_IN_TC_LOG
  eng "Bad magic header in tc log"

ER_TC_NEED_N_SE_SUPPORTING_2PC_FOR_RECOVERY
  eng "Recovery failed! You must enable exactly %d storage engines that support two-phase commit protocol"

ER_TC_RECOVERY_FAILED_THESE_ARE_YOUR_OPTIONS
  eng "Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}"

ER_TC_HEURISTIC_RECOVERY_MODE
  eng "Heuristic crash recovery mode"

ER_TC_HEURISTIC_RECOVERY_FAILED
  eng "Heuristic crash recovery failed"

ER_TC_RESTART_WITHOUT_TC_HEURISTIC_RECOVER
  eng "Please restart mysqld without --tc-heuristic-recover"

ER_RPL_REPLICA_FAILED_TO_CREATE_OR_RECOVER_INFO_REPOSITORIES
  eng "Failed to create or recover replication info repositories."

ER_RPL_REPLICA_AUTO_POSITION_IS_1_AND_GTID_MODE_IS_OFF
  eng "Detected misconfiguration: replication channel '%.192s' was configured with AUTO_POSITION = 1, but the server was started with --gtid-mode=off. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0 FOR CHANNEL '%.192s', or change GTID_MODE to some value other than OFF, before starting the replica receiver thread."

ER_RPL_REPLICA_CANT_START_REPLICA_FOR_CHANNEL
  eng "Replica: Could not start replica for channel '%s'. operation discontinued"

ER_RPL_REPLICA_CANT_STOP_REPLICA_FOR_CHANNEL
  eng "Replica: Could not stop replica for channel '%s' operation discontinued"

ER_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE
  eng "Error during --relay-log-recovery: Could not locate rotate event from the source."

ER_RPL_RECOVERY_ERROR_READ_RELAY_LOG
  eng "Error during --relay-log-recovery: Error reading events from relay log: %d"

OBSOLETE_ER_RPL_RECOVERY_ERROR_FREEING_IO_CACHE
  eng "Error during --relay-log-recovery: Error while freeing IO_CACHE object"

ER_RPL_RECOVERY_SKIPPED_GROUP_REPLICATION_CHANNEL
  eng "Relay log recovery skipped for group replication channel."

ER_RPL_RECOVERY_ERROR
  eng "Error during --relay-log-recovery: %s"

ER_RPL_RECOVERY_IO_ERROR_READING_RELAY_LOG_INDEX
  eng "Error during --relay-log-recovery: Could not read relay log index file due to an IO error."

ER_RPL_RECOVERY_FILE_SOURCE_POS_INFO
  eng "Recovery from source pos %ld and file %s%s. Previous relay log pos and relay log file had been set to %lld, %s respectively."

ER_RPL_RECOVERY_REPLICATE_SAME_SERVER_ID_REQUIRES_POSITION
  eng "Error during --relay-log-recovery: replicate_same_server_id is in use and sql thread's positions are not initialized, hence relay log recovery cannot happen."

ER_RPL_MTA_RECOVERY_STARTING_COORDINATOR
  eng "MTA recovery: starting coordinator thread to fill MTA gaps."

ER_RPL_MTA_RECOVERY_FAILED_TO_START_COORDINATOR
  eng "MTA recovery: failed to start the coordinator thread. Check the error log for additional details."

ER_RPL_MTA_AUTOMATIC_RECOVERY_FAILED
  eng "MTA recovery: automatic recovery failed. Either the replica server had stopped due to an error during an earlier session or relay logs are corrupted.Fix the cause of the replica side error and restart the replica server or consider using RESET REPLICA."

ER_RPL_MTA_RECOVERY_CANT_OPEN_RELAY_LOG
  eng "Failed to open the relay log '%s' (relay_log_pos %s)."

ER_RPL_MTA_RECOVERY_SUCCESSFUL
  eng "MTA recovery: completed successfully."

ER_RPL_SERVER_ID_MISSING
  eng "Server id not set, will not start replica%s"

ER_RPL_CANT_CREATE_REPLICA_THREAD
  eng "Can't create replica thread%s."

ER_RPL_REPLICA_IO_THREAD_WAS_KILLED
  eng "The replica IO thread%s was killed while executing initialization query '%s'"

OBSOLETE_ER_RPL_REPLICA_SOURCE_UUID_HAS_CHANGED
  eng "The source's UUID has changed, although this should not happen unless you have changed it manually. The old UUID was %s."

ER_RPL_REPLICA_USES_CHECKSUM_AND_SOURCE_PRE_50
  eng "Found a source with MySQL server version older than 5.0. With checksums enabled on the replica, replication might not work correctly. To ensure correct replication, restart the replica server with --replica_sql_verify_checksum=0."

ER_RPL_REPLICA_SECONDS_BEHIND_SOURCE_DUBIOUS
  eng "\"SELECT UNIX_TIMESTAMP()\" failed on source, do not trust column Seconds_Behind_Source of SHOW REPLICA STATUS. Error: %s (%d)"

ER_RPL_REPLICA_CANT_FLUSH_CONNECTION_METADATA_REPOS
  eng "Failed to flush connection metadata repository."

ER_RPL_REPLICA_REPORT_HOST_TOO_LONG
  eng "The length of report_host is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s."

ER_RPL_REPLICA_REPORT_USER_TOO_LONG
  eng "The length of report_user is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s."

ER_RPL_REPLICA_REPORT_PASSWORD_TOO_LONG
  eng "The length of report_password is %zu. It is larger than the max length(%d), so this replica cannot be registered to the source%s."

ER_RPL_REPLICA_ERROR_RETRYING
  eng "Error on %s: %d  %s, will retry in %d secs"

ER_RPL_REPLICA_ERROR_READING_FROM_SERVER
  eng "Error reading packet from server%s: %s (server_errno=%d)"

ER_RPL_REPLICA_DUMP_THREAD_KILLED_BY_SOURCE
  eng "Replica%s: received end packet from server due to dump thread being killed on source. Dump threads are killed for example during source shutdown, explicitly by a user, or when the source receives a binlog send request from a duplicate server UUID <%s> : Error %s"

ER_RPL_MTA_STATISTICS
  eng "Multi-threaded replica statistics%s: seconds elapsed = %lu; events assigned = %llu; worker queues filled over overrun level = %lu; waited due a Worker queue full = %lu; waited due the total size = %lu; waited at clock conflicts = %llu waited (count) when Workers occupied = %lu waited when Workers occupied = %llu"

ER_RPL_MTA_RECOVERY_COMPLETE
  eng "Replica%s: MTA Recovery has completed at relay log %s, position %llu source log %s, position %llu."

ER_RPL_REPLICA_CANT_INIT_RELAY_LOG_POSITION
  eng "Error initializing relay log position%s: %s"

OBSOLETE_ER_RPL_REPLICA_CONNECTED_TO_SOURCE_REPLICATION_STARTED
  eng "Replica I/O thread%s: connected to source '%s@%s:%d',replication started in log '%s' at position %s"

ER_RPL_REPLICA_IO_THREAD_KILLED
  eng "Replica I/O thread%s killed while connecting to source"

ER_RPL_REPLICA_IO_THREAD_CANT_REGISTER_ON_SOURCE
  eng "Replica I/O thread couldn't register on source"

ER_RPL_REPLICA_FORCING_TO_RECONNECT_IO_THREAD
  eng "Forcing to reconnect replica I/O thread%s"

ER_RPL_REPLICA_ERROR_REQUESTING_BINLOG_DUMP
  eng "Failed on request_dump()%s"

ER_RPL_LOG_ENTRY_EXCEEDS_REPLICA_MAX_ALLOWED_PACKET
  eng "Log entry on source is longer than replica_max_allowed_packet (%lu) on replica. If the entry is correct, restart the server with a higher value of replica_max_allowed_packet"

ER_RPL_REPLICA_STOPPING_AS_SOURCE_OOM
  eng "Stopping replica I/O thread due to out-of-memory error from source"

ER_RPL_REPLICA_IO_THREAD_ABORTED_WAITING_FOR_RELAY_LOG_SPACE
  eng "Replica I/O thread aborted while waiting for relay log space"

ER_RPL_REPLICA_IO_THREAD_EXITING
  eng "Replica I/O thread exiting%s, read up to log '%s', position %s"

ER_RPL_REPLICA_CANT_INITIALIZE_REPLICA_WORKER
  eng "Failed during replica worker initialization%s"

ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA_FOR_WORKER
  eng "Replica: MTA group recovery applier metadata based on Worker-Id %lu, group_relay_log_name %s, group_relay_log_pos %llu group_source_log_name %s, group_source_log_pos %llu"

ER_RPL_ERROR_LOOKING_FOR_LOG
  eng "Error looking for %s."

ER_RPL_MTA_GROUP_RECOVERY_APPLIER_METADATA
  eng "Replica: MTA group recovery applier metadata group_source_log_name %s, event_source_log_pos %llu."

ER_RPL_CANT_FIND_FOLLOWUP_FILE
  eng "Error looking for file after %s."

ER_RPL_MTA_CHECKPOINT_PERIOD_DIFFERS_FROM_CNT
  eng "This an error cnt != mta_checkpoint_period"

ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED
  eng "Failed during replica worker thread creation%s"

ER_RPL_REPLICA_WORKER_THREAD_CREATION_FAILED_WITH_ERRNO
  eng "Failed during replica worker thread creation%s (errno= %d)"

ER_RPL_REPLICA_FAILED_TO_INIT_PARTITIONS_HASH
  eng "Failed to init partitions hash"

OBSOLETE_ER_RPL_SLAVE_NDB_TABLES_NOT_AVAILABLE
  eng "Replica SQL thread : NDB : Tables not available after %lu seconds. Consider increasing --ndb-wait-setup value"

ER_RPL_REPLICA_SQL_THREAD_STARTING
  eng "Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s"

ER_RPL_REPLICA_SKIP_COUNTER_EXECUTED
  eng "'SQL_REPLICA_SKIP_COUNTER=%ld' executed at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' and new position at relay_log_file='%s', relay_log_pos='%ld', source_log_name='%s', source_log_pos='%ld' "

ER_RPL_REPLICA_ADDITIONAL_ERROR_INFO_FROM_DA
  eng "Replica (additional info): %s Error_code: MY-%06d"

ER_RPL_REPLICA_ERROR_INFO_FROM_DA
  eng "Replica: %s Error_code: MY-%06d"

ER_RPL_REPLICA_ERROR_LOADING_USER_DEFINED_LIBRARY
  eng "Error loading user-defined library, replica SQL thread aborted. Install the missing library, and restart the replica SQL thread with \"START REPLICA\". We stopped at log '%s' position %s"

ER_RPL_REPLICA_ERROR_RUNNING_QUERY
  eng "Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with \"START REPLICA\". We stopped at log '%s' position %s"

ER_RPL_REPLICA_SQL_THREAD_EXITING
  eng "Replica SQL thread%s exiting, replication stopped in log '%s' at position %s"

ER_RPL_REPLICA_READ_INVALID_EVENT_FROM_SOURCE
  eng "Read invalid event from source: '%s', source could be corrupt but a more likely cause of this is a bug"

ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_CONFIGURATION
  eng "The queue event failed for channel '%s' as its configuration is invalid."

ER_RPL_REPLICA_IO_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE
  eng "An unexpected event sequence was detected by the IO thread while queuing the event received from source '%s' binary log file, at position %llu."

ER_RPL_REPLICA_CANT_USE_CHARSET
  eng "'%s' can not be used as client character set. '%s' will be used as default client character set while connecting to source."

ER_RPL_REPLICA_CONNECTED_TO_SOURCE_REPLICATION_RESUMED
  eng "Replica%s: connected to source '%s@%s:%d',replication resumed in log '%s' at position %s"

ER_RPL_REPLICA_NEXT_LOG_IS_ACTIVE
  eng "next log '%s' is active"

ER_RPL_REPLICA_NEXT_LOG_IS_INACTIVE
  eng "next log '%s' is not active"

ER_RPL_REPLICA_SQL_THREAD_IO_ERROR_READING_EVENT
  eng "Replica SQL thread%s: I/O error reading event (errno: %d  cur_log->error: %d)"

ER_RPL_REPLICA_ERROR_READING_RELAY_LOG_EVENTS
  eng "Error reading relay log event%s: %s"

ER_REPLICA_CHANGE_SOURCE_TO_EXECUTED
  eng "'CHANGE REPLICATION SOURCE TO%s executed'. Previous state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'. New state source_host='%s', source_port= %u, source_log_file='%s', source_log_pos= %ld, source_bind='%s'."

ER_RPL_REPLICA_NEW_C_M_NEEDS_REPOS_TYPE_OTHER_THAN_FILE
  eng "Replica: Cannot create new connection metadata structure when repositories are of type FILE. Convert replica repositories to TABLE to replicate from multiple sources."

ER_RPL_FAILED_TO_STAT_LOG_IN_INDEX
  eng "log %s listed in the index, but failed to stat."

ER_RPL_LOG_NOT_FOUND_WHILE_COUNTING_RELAY_LOG_SPACE
  eng "Could not find first log while counting relay log space."

ER_REPLICA_CANT_USE_TEMPDIR
  eng "Unable to use replica's temporary directory '%s'."

ER_RPL_RELAY_LOG_NEEDS_FILE_NOT_DIRECTORY
  eng "Path '%s' is a directory name, please specify a file name for --relay-log option."

ER_RPL_RELAY_LOG_INDEX_NEEDS_FILE_NOT_DIRECTORY
  eng "Path '%s' is a directory name, please specify a file name for --relay-log-index option."

ER_RPL_PLEASE_USE_OPTION_RELAY_LOG
  eng "Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a replica and has his hostname changed!! Please use '--relay-log=%s' to avoid this problem."

ER_RPL_OPEN_INDEX_FILE_FAILED
  eng "Failed in open_index_file() called from Relay_log_info::rli_init_info()."

ER_RPL_CANT_INITIALIZE_GTID_SETS_IN_AM_INIT_INFO
  eng "Failed in init_gtid_sets() called from Relay_log_info::rli_init_info()."

ER_RPL_CANT_OPEN_LOG_IN_AM_INIT_INFO
  eng "Failed in open_log() called from Relay_log_info::rli_init_info()."

ER_RPL_ERROR_WRITING_RELAY_LOG_CONFIGURATION
  eng "Error writing relay log configuration."

OBSOLETE_ER_NDB_OOM_GET_NDB_BLOBS_VALUE
  eng "get_ndb_blobs_value: my_malloc(%u) failed"

OBSOLETE_ER_NDB_THREAD_TIMED_OUT
  eng "NDB: Thread id %u timed out (30s) waiting for epoch %u/%u to be handled.  Progress : %u/%u -> %u/%u."

OBSOLETE_ER_NDB_TABLE_IS_NOT_DISTRIBUTED
  eng "NDB: Inconsistency detected in distributed privilege tables. Table '%s.%s' is not distributed"

OBSOLETE_ER_NDB_CREATING_TABLE
  eng "NDB: Creating %s.%s"

OBSOLETE_ER_NDB_FLUSHING_TABLE_INFO
  eng "NDB: Flushing %s.%s"

OBSOLETE_ER_NDB_CLEANING_STRAY_TABLES
  eng "NDB: Cleaning stray tables from database '%s'"

OBSOLETE_ER_NDB_DISCOVERED_MISSING_DB
  eng "NDB: Discovered missing database '%s'"

OBSOLETE_ER_NDB_DISCOVERED_REMAINING_DB
  eng "NDB: Discovered remaining database '%s'"

OBSOLETE_ER_NDB_CLUSTER_FIND_ALL_DBS_RETRY
  eng "NDB: ndbcluster_find_all_databases retry: %u - %s"

OBSOLETE_ER_NDB_CLUSTER_FIND_ALL_DBS_FAIL
  eng "NDB: ndbcluster_find_all_databases fail: %u - %s"

OBSOLETE_ER_NDB_SKIPPING_SETUP_TABLE
  eng "NDB: skipping setup table %s.%s, in state %d"

OBSOLETE_ER_NDB_FAILED_TO_SET_UP_TABLE
  eng "NDB: failed to setup table %s.%s, error: %d, %s"

OBSOLETE_ER_NDB_MISSING_FRM_DISCOVERING
  eng "NDB: missing frm for %s.%s, discovering..."

OBSOLETE_ER_NDB_MISMATCH_IN_FRM_DISCOVERING
  eng "NDB: mismatch in frm for %s.%s, discovering..."

OBSOLETE_ER_NDB_BINLOG_CLEANING_UP_SETUP_LEFTOVERS
  eng "ndb_binlog_setup: Clean up leftovers"

OBSOLETE_ER_NDB_WAITING_INFO
  eng "NDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s"

OBSOLETE_ER_NDB_WAITING_INFO_WITH_MAP
  eng "NDB %s: waiting max %u sec for %s %s.  epochs: (%u/%u,%u/%u,%u/%u)  injector proc_info: %s map: %x%08x"

OBSOLETE_ER_NDB_TIMEOUT_WHILE_DISTRIBUTING
  eng "NDB %s: distributing %s timed out. Ignoring..."

OBSOLETE_ER_NDB_NOT_WAITING_FOR_DISTRIBUTING
  eng "NDB %s: not waiting for distributing %s"

OBSOLETE_ER_NDB_DISTRIBUTED_INFO
  eng "NDB: distributed %s.%s(%u/%u) type: %s(%u) query: \'%s\' to %x%08x"

OBSOLETE_ER_NDB_DISTRIBUTION_COMPLETE
  eng "NDB: distribution of %s.%s(%u/%u) type: %s(%u) query: \'%s\' - complete!"

OBSOLETE_ER_NDB_SCHEMA_DISTRIBUTION_FAILED
  eng "NDB Schema dist: Data node: %d failed, subscriber bitmask %x%08x"

OBSOLETE_ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_SUBSCRIBE
  eng "NDB Schema dist: Data node: %d reports subscribe from node %d, subscriber bitmask %x%08x"

OBSOLETE_ER_NDB_SCHEMA_DISTRIBUTION_REPORTS_UNSUBSCRIBE
  eng "NDB Schema dist: Data node: %d reports unsubscribe from node %d, subscriber bitmask %x%08x"

OBSOLETE_ER_NDB_BINLOG_CANT_DISCOVER_TABLE_FROM_SCHEMA_EVENT
  eng "NDB Binlog: Could not discover table '%s.%s' from binlog schema event '%s' from node %d. my_errno: %d"

OBSOLETE_ER_NDB_BINLOG_SIGNALLING_UNKNOWN_VALUE
  eng "NDB: unknown value for binlog signalling 0x%X, %s not logged"

OBSOLETE_ER_NDB_BINLOG_REPLY_TO
  eng "NDB: reply to %s.%s(%u/%u) from %s to %x%08x"

OBSOLETE_ER_NDB_BINLOG_CANT_RELEASE_SLOCK
  eng "NDB: Could not release slock on '%s.%s', Error code: %d Message: %s"

OBSOLETE_ER_NDB_CANT_FIND_TABLE
  eng "NDB schema: Could not find table '%s.%s' in NDB"

OBSOLETE_ER_NDB_DISCARDING_EVENT_NO_OBJ
  eng "NDB: Discarding event...no obj: %s (%u/%u)"

OBSOLETE_ER_NDB_DISCARDING_EVENT_ID_VERSION_MISMATCH
  eng "NDB: Discarding event...key: %s non matching id/version [%u/%u] != [%u/%u]"

OBSOLETE_ER_NDB_CLEAR_SLOCK_INFO
  eng "NDB: CLEAR_SLOCK key: %s(%u/%u) %x%08x, from %s to %x%08x"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_LOCAL_TABLE
  eng "NDB Binlog: Skipping locally defined table '%s.%s' from binlog schema event '%s' from node %d."

OBSOLETE_ER_NDB_BINLOG_ONLINE_ALTER_RENAME
  eng "NDB Binlog: handling online alter/rename"

OBSOLETE_ER_NDB_BINLOG_CANT_REOPEN_SHADOW_TABLE
  eng "NDB Binlog: Failed to re-open shadow table %s.%s"

OBSOLETE_ER_NDB_BINLOG_ONLINE_ALTER_RENAME_COMPLETE
  eng "NDB Binlog: handling online alter/rename done"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_DROP_OF_LOCAL_TABLE
  eng "NDB Binlog: Skipping drop of locally defined table '%s.%s' from binlog schema event '%s' from node %d. "

OBSOLETE_ER_NDB_BINLOG_SKIPPING_RENAME_OF_LOCAL_TABLE
  eng "NDB Binlog: Skipping renaming locally defined table '%s.%s' from binlog schema event '%s' from node %d. "

OBSOLETE_ER_NDB_BINLOG_SKIPPING_DROP_OF_TABLES
  eng "NDB Binlog: Skipping drop database '%s' since it contained local tables binlog schema event '%s' from node %d. "

OBSOLETE_ER_NDB_BINLOG_GOT_DIST_PRIV_EVENT_FLUSHING_PRIVILEGES
  eng "Got dist_priv event: %s, flushing privileges"

OBSOLETE_ER_NDB_BINLOG_GOT_SCHEMA_EVENT
  eng "NDB: got schema event on %s.%s(%u/%u) query: '%s' type: %s(%d) node: %u slock: %x%08x"

OBSOLETE_ER_NDB_BINLOG_SKIPPING_OLD_SCHEMA_OPERATION
  eng "NDB schema: Skipping old schema operation(RENAME_TABLE_NEW) on %s.%s"

OBSOLETE_ER_NDB_CLUSTER_FAILURE
  eng "NDB Schema dist: cluster failure at epoch %u/%u."

OBSOLETE_ER_NDB_TABLES_INITIALLY_READ_ONLY_ON_RECONNECT
  eng "NDB Binlog: ndb tables initially read only on reconnect."

OBSOLETE_ER_NDB_IGNORING_UNKNOWN_EVENT
  eng "NDB Schema dist: unknown event %u, ignoring..."

OBSOLETE_ER_NDB_BINLOG_OPENING_INDEX
  eng "NDB Binlog: Opening ndb_binlog_index: %d, '%s'"

OBSOLETE_ER_NDB_BINLOG_CANT_LOCK_NDB_BINLOG_INDEX
  eng "NDB Binlog: Unable to lock table ndb_binlog_index"

OBSOLETE_ER_NDB_BINLOG_INJECTING_RANDOM_WRITE_FAILURE
  eng "NDB Binlog: Injecting random write failure"

OBSOLETE_ER_NDB_BINLOG_CANT_WRITE_TO_NDB_BINLOG_INDEX
  eng "NDB Binlog: Failed writing to ndb_binlog_index for epoch %u/%u  orig_server_id %u orig_epoch %u/%u with error %d."

OBSOLETE_ER_NDB_BINLOG_WRITING_TO_NDB_BINLOG_INDEX
  eng "NDB Binlog: Writing row (%s) to ndb_binlog_index - %s"

OBSOLETE_ER_NDB_BINLOG_CANT_COMMIT_TO_NDB_BINLOG_INDEX
  eng "NDB Binlog: Failed committing transaction to ndb_binlog_index with error %d."

OBSOLETE_ER_NDB_BINLOG_WRITE_INDEX_FAILED_AFTER_KILL
  eng "NDB Binlog: Failed writing to ndb_binlog_index table while retrying after kill during shutdown"

OBSOLETE_ER_NDB_BINLOG_USING_SERVER_ID_0_SLAVES_WILL_NOT
  eng "NDB: server id set to zero - changes logged to bin log with server id zero will be logged with another server id by replica mysqlds"

OBSOLETE_ER_NDB_SERVER_ID_RESERVED_OR_TOO_LARGE
  eng "NDB: server id provided is too large to be represented in opt_server_id_bits or is reserved"

OBSOLETE_ER_NDB_BINLOG_REQUIRES_V2_ROW_EVENTS
  eng "NDB: --ndb-log-transaction-id requires v2 Binlog row events but server is using v1."

OBSOLETE_ER_NDB_BINLOG_STATUS_FORCING_FULL_USE_WRITE
  eng "NDB: ndb-log-apply-status forcing %s.%s to FULL USE_WRITE"

OBSOLETE_ER_NDB_BINLOG_GENERIC_MESSAGE
  eng "NDB Binlog: %s"

OBSOLETE_ER_NDB_CONFLICT_GENERIC_MESSAGE
  eng "%s"

OBSOLETE_ER_NDB_TRANS_DEPENDENCY_TRACKER_ERROR
  eng "%s"

OBSOLETE_ER_NDB_CONFLICT_FN_PARSE_ERROR
  eng "NDB Replica: Table %s.%s : Parse error on conflict fn : %s"

OBSOLETE_ER_NDB_CONFLICT_FN_SETUP_ERROR
  eng "NDB Replica: Table %s.%s : %s"

OBSOLETE_ER_NDB_BINLOG_FAILED_TO_GET_TABLE
  eng "NDB Binlog: Failed to get table %s from ndb: %s, %d"

OBSOLETE_ER_NDB_BINLOG_NOT_LOGGING
  eng "NDB Binlog: NOT logging %s"

OBSOLETE_ER_NDB_BINLOG_CREATE_TABLE_EVENT_FAILED
  eng "NDB Binlog: FAILED CREATE (DISCOVER) TABLE Event: %s"

OBSOLETE_ER_NDB_BINLOG_CREATE_TABLE_EVENT_INFO
  eng "NDB Binlog: CREATE (DISCOVER) TABLE Event: %s"

OBSOLETE_ER_NDB_BINLOG_DISCOVER_TABLE_EVENT_INFO
  eng "NDB Binlog: DISCOVER TABLE Event: %s"

OBSOLETE_ER_NDB_BINLOG_BLOB_REQUIRES_PK
  eng "NDB Binlog: logging of table %s with BLOB attribute and no PK is not supported"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB
  eng "NDB Binlog: Unable to create event in database. Event: %s  Error Code: %d  Message: %s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_AND_CANT_DROP
  eng "NDB Binlog: Unable to create event in database.  Attempt to correct with drop failed. Event: %s Error Code: %d Message: %s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_EVENT_IN_DB_DROPPED
  eng "NDB Binlog: Unable to create event in database.  Attempt to correct with drop ok, but create failed. Event: %s Error Code: %d Message: %s"

OBSOLETE_ER_NDB_BINLOG_DISCOVER_REUSING_OLD_EVENT_OPS
  eng "NDB Binlog: discover reusing old ev op"

OBSOLETE_ER_NDB_BINLOG_CREATING_NDBEVENTOPERATION_FAILED
  eng "NDB Binlog: Creating NdbEventOperation failed for %s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_BLOB
  eng "NDB Binlog: Creating NdbEventOperation blob field %u handles failed (code=%d) for %s"

OBSOLETE_ER_NDB_BINLOG_NDBEVENT_EXECUTE_FAILED
  eng "NDB Binlog: ndbevent->execute failed for %s; %d %s"

OBSOLETE_ER_NDB_CREATE_EVENT_OPS_LOGGING_INFO
  eng "NDB Binlog: logging %s (%s,%s)"

OBSOLETE_ER_NDB_BINLOG_CANT_DROP_EVENT_FROM_DB
  eng "NDB Binlog: Unable to drop event in database. Event: %s Error Code: %d Message: %s"

OBSOLETE_ER_NDB_TIMED_OUT_IN_DROP_TABLE
  eng "NDB %s: %s timed out. Ignoring..."

OBSOLETE_ER_NDB_BINLOG_UNHANDLED_ERROR_FOR_TABLE
  eng "NDB Binlog: unhandled error %d for table %s"

OBSOLETE_ER_NDB_BINLOG_CLUSTER_FAILURE
  eng "NDB Binlog: cluster failure for %s at epoch %u/%u."

OBSOLETE_ER_NDB_BINLOG_UNKNOWN_NON_DATA_EVENT
  eng "NDB Binlog: unknown non data event %d for %s. Ignoring..."

OBSOLETE_ER_NDB_BINLOG_INJECTOR_DISCARDING_ROW_EVENT_METADATA
  eng "NDB: Binlog Injector discarding row event meta data as server is using v1 row events. (%u %x)"

OBSOLETE_ER_NDB_REMAINING_OPEN_TABLES
  eng "remove_all_event_operations: Remaining open tables: "

OBSOLETE_ER_NDB_REMAINING_OPEN_TABLE_INFO
  eng "  %s.%s, use_count: %u"

OBSOLETE_ER_NDB_COULD_NOT_GET_APPLY_STATUS_SHARE
  eng "NDB: Could not get apply status share"

OBSOLETE_ER_NDB_BINLOG_SERVER_SHUTDOWN_DURING_NDB_CLUSTER_START
  eng "NDB Binlog: Server shutdown detected while waiting for ndbcluster to start..."

OBSOLETE_ER_NDB_BINLOG_CLUSTER_RESTARTED_RESET_MASTER_SUGGESTED
  eng "NDB Binlog: cluster has been restarted --initial or with older filesystem. ndb_latest_handled_binlog_epoch: %u/%u, while current epoch: %u/%u. RESET SOURCE should be issued. Resetting ndb_latest_handled_binlog_epoch."

OBSOLETE_ER_NDB_BINLOG_CLUSTER_HAS_RECONNECTED
  eng "NDB Binlog: cluster has reconnected. Changes to the database that occurred while disconnected will not be in the binlog"

OBSOLETE_ER_NDB_BINLOG_STARTING_LOG_AT_EPOCH
  eng "NDB Binlog: starting log at epoch %u/%u"

OBSOLETE_ER_NDB_BINLOG_NDB_TABLES_WRITABLE
  eng "NDB Binlog: ndb tables writable"

OBSOLETE_ER_NDB_BINLOG_SHUTDOWN_DETECTED
  eng "NDB Binlog: Server shutdown detected..."

OBSOLETE_ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_WAITING
  eng "NDB Binlog: Just lost schema connection, hanging around"

OBSOLETE_ER_NDB_BINLOG_LOST_SCHEMA_CONNECTION_CONTINUING
  eng "NDB Binlog: ...and on our way"

OBSOLETE_ER_NDB_BINLOG_ERROR_HANDLING_SCHEMA_EVENT
  eng "NDB: error %lu (%s) on handling binlog schema event"

OBSOLETE_ER_NDB_BINLOG_CANT_INJECT_APPLY_STATUS_WRITE_ROW
  eng "NDB Binlog: Failed to inject apply status write row"

OBSOLETE_ER_NDB_BINLOG_ERROR_DURING_GCI_ROLLBACK
  eng "NDB Binlog: Error during ROLLBACK of GCI %u/%u. Error: %d"

OBSOLETE_ER_NDB_BINLOG_ERROR_DURING_GCI_COMMIT
  eng "NDB Binlog: Error during COMMIT of GCI. Error: %d"

OBSOLETE_ER_NDB_BINLOG_LATEST_TRX_IN_EPOCH_NOT_IN_BINLOG
  eng "NDB Binlog: latest transaction in epoch %u/%u not in binlog as latest handled epoch is %u/%u"

OBSOLETE_ER_NDB_BINLOG_RELEASING_EXTRA_SHARE_REFERENCES
  eng "NDB Binlog: Release extra share references"

OBSOLETE_ER_NDB_BINLOG_REMAINING_OPEN_TABLES
  eng "NDB Binlog: remaining open tables: "

OBSOLETE_ER_NDB_BINLOG_REMAINING_OPEN_TABLE_INFO
  eng "  %s.%s state: %u use_count: %u"

ER_TREE_CORRUPT_PARENT_SHOULD_POINT_AT_PARENT
  eng "Wrong tree: Parent doesn't point at parent"

ER_TREE_CORRUPT_ROOT_SHOULD_BE_BLACK
  eng "Wrong tree: Root should be black"

ER_TREE_CORRUPT_2_CONSECUTIVE_REDS
  eng "Wrong tree: Found two red in a row"

ER_TREE_CORRUPT_RIGHT_IS_LEFT
  eng "Wrong tree: Found right == left"

ER_TREE_CORRUPT_INCORRECT_BLACK_COUNT
  eng "Wrong tree: Incorrect black-count: %d - %d"

ER_WRONG_COUNT_FOR_ORIGIN
  eng "Use_count: Wrong count %lu for origin %p"

ER_WRONG_COUNT_FOR_KEY
  eng "Use_count: Wrong count for key at %p, %lu should be %lu"

ER_WRONG_COUNT_OF_ELEMENTS
  eng "Wrong number of elements: %u (should be %u) for tree at %p"

ER_RPL_ERROR_READING_REPLICA_WORKER_CONFIGURATION
  eng "Error reading replica worker configuration"

OBSOLETE_ER_RPL_ERROR_WRITING_SLAVE_WORKER_CONFIGURATION
  eng "Error writing replica worker configuration"

ER_RPL_FAILED_TO_OPEN_RELAY_LOG
  eng "Failed to open relay log %s, error: %s"

ER_RPL_WORKER_CANT_READ_RELAY_LOG
  eng "Error when worker read relay log events,relay log name %s, position %llu"

ER_RPL_WORKER_CANT_FIND_NEXT_RELAY_LOG
  eng "Failed to find next relay log when retrying the transaction, current relay log is %s"

ER_RPL_MTA_REPLICA_COORDINATOR_HAS_WAITED
  eng "Multi-threaded replica: Coordinator has waited %lu times hitting replica_pending_jobs_size_max; current event size = %zu."

ER_BINLOG_FAILED_TO_WRITE_DROP_FOR_TEMP_TABLES
  eng "Failed to write the DROP statement for temporary tables to binary log"

ER_BINLOG_OOM_WRITING_DELETE_WHILE_OPENING_HEAP_TABLE
  eng "When opening HEAP table, could not allocate memory to write 'DELETE FROM `%s`.`%s`' to the binary log"

ER_FAILED_TO_REPAIR_TABLE
  eng "Couldn't repair table: %s.%s"

ER_FAILED_TO_REMOVE_TEMP_TABLE
  eng "Could not remove temporary table: '%s', error: %d"

ER_SYSTEM_TABLE_NOT_TRANSACTIONAL
  eng "System table '%.*s' is expected to be transactional."

ER_RPL_ERROR_WRITING_SOURCE_CONFIGURATION
  eng "Error writing source configuration."

ER_RPL_ERROR_READING_SOURCE_CONFIGURATION
  eng "Error reading source configuration."

ER_RPL_SSL_INFO_IN_CONNECTION_METADATA_IGNORED
  eng "SSL information in the connection metadata repository are ignored because this MySQL replica was compiled without SSL support."

ER_PLUGIN_FAILED_DEINITIALIZATION
  eng "Plugin '%s' of type %s failed deinitialization"

ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_DEINITIALIZATION
  eng "Plugin '%s' has ref_count=%d after deinitialization."

ER_PLUGIN_SHUTTING_DOWN_PLUGIN
  eng "Shutting down plugin '%s'"

ER_PLUGIN_REGISTRATION_FAILED
  eng "Plugin '%s' registration as a %s failed."

ER_PLUGIN_CANT_OPEN_PLUGIN_TABLE
  eng "Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure."

ER_PLUGIN_CANT_LOAD
  eng "Couldn't load plugin named '%s' with soname '%s'."

ER_PLUGIN_LOAD_PARAMETER_TOO_LONG
  eng "plugin-load parameter too long"

ER_PLUGIN_FORCING_SHUTDOWN
  eng "Plugin '%s' will be forced to shutdown"

ER_PLUGIN_HAS_NONZERO_REFCOUNT_AFTER_SHUTDOWN
  eng "Plugin '%s' has ref_count=%d after shutdown."

ER_PLUGIN_UNKNOWN_VARIABLE_TYPE
  eng "Unknown variable type code 0x%x in plugin '%s'."

ER_PLUGIN_VARIABLE_SET_READ_ONLY
  eng "Server variable %s of plugin %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag"

ER_PLUGIN_VARIABLE_MISSING_NAME
  eng "Missing variable name in plugin '%s'."

ER_PLUGIN_VARIABLE_NOT_ALLOCATED_THREAD_LOCAL
  eng "Thread local variable '%s' not allocated in plugin '%s'."

ER_PLUGIN_OOM
  eng "Out of memory for plugin '%s'."

ER_PLUGIN_BAD_OPTIONS
  eng "Bad options for plugin '%s'."

ER_PLUGIN_PARSING_OPTIONS_FAILED
  eng "Parsing options for plugin '%s' failed."

ER_PLUGIN_DISABLED
  eng "Plugin '%s' is disabled."

ER_PLUGIN_HAS_CONFLICTING_SYSTEM_VARIABLES
  eng "Plugin '%s' has conflicting system variables"

ER_PLUGIN_CANT_SET_PERSISTENT_OPTIONS
  eng "Setting persistent options for plugin '%s' failed."

ER_MY_NET_WRITE_FAILED_FALLING_BACK_ON_STDERR
  eng "Failed on my_net_write, writing to stderr instead: %s"

ER_RETRYING_REPAIR_WITHOUT_QUICK
  eng "Retrying repair of: '%s' without quick"

ER_RETRYING_REPAIR_WITH_KEYCACHE
  eng "Retrying repair of: '%s' with keycache"

ER_FOUND_ROWS_WHILE_REPAIRING
  eng "Found %s of %s rows when repairing '%s'"

ER_ERROR_DURING_OPTIMIZE_TABLE
  eng "Warning: Optimize table got errno %d on %s.%s, retrying"

ER_ERROR_ENABLING_KEYS
  eng "Warning: Enabling keys got errno %d on %s.%s, retrying"

ER_CHECKING_TABLE
  eng "Checking table:   '%s'"

ER_RECOVERING_TABLE
  eng "Recovering table: '%s'"

ER_CANT_CREATE_TABLE_SHARE_FROM_FRM
  eng "Error in creating TABLE_SHARE from %s.frm file."

ER_CANT_LOCK_TABLE
  eng "Unable to acquire lock on %s.%s"

ER_CANT_ALLOC_TABLE_OBJECT
  eng "Error in allocation memory for TABLE object."

ER_CANT_CREATE_HANDLER_OBJECT_FOR_TABLE
  eng "Error in creating handler object for table %s.%s"

ER_CANT_SET_HANDLER_REFERENCE_FOR_TABLE
  eng "Error in setting handler reference for table %s.%s"

ER_CANT_LOCK_TABLESPACE
  eng "Unable to acquire lock on tablespace name %s"

ER_CANT_UPGRADE_GENERATED_COLUMNS_TO_DD
  eng "Error in processing generated columns for table %s.%s"

ER_DD_ERROR_CREATING_ENTRY
  eng "Error in Creating DD entry for %s.%s"

ER_DD_CANT_FETCH_TABLE_DATA
  eng "Error in fetching %s.%s table data from dictionary"

ER_DD_CANT_FIX_SE_DATA
  eng "Error in fixing SE data for %s.%s"

ER_DD_CANT_CREATE_SP
  eng "Error in creating stored program '%s.%s'"

ER_CANT_OPEN_DB_OPT_USING_DEFAULT_CHARSET
  eng "Unable to open db.opt file %s. Using default Character set."

ER_CANT_CREATE_CACHE_FOR_DB_OPT
  eng "Unable to intialize IO cache to open db.opt file %s. "

ER_CANT_IDENTIFY_CHARSET_USING_DEFAULT
  eng "Unable to identify the charset in %s. Using default character set."

ER_DB_OPT_NOT_FOUND_USING_DEFAULT_CHARSET
  eng "db.opt file not found for %s database. Using default Character set."

ER_EVENT_CANT_GET_TIMEZONE_FROM_FIELD
  eng "Event '%s'.'%s': invalid value in column mysql.event.time_zone."

ER_EVENT_CANT_FIND_TIMEZONE
  eng "Event '%s'.'%s': has invalid time zone value "

ER_EVENT_CANT_GET_CHARSET
  eng "Event '%s'.'%s': invalid value in column mysql.event.character_set_client."

ER_EVENT_CANT_GET_COLLATION
  eng "Event '%s'.'%s': invalid value in column mysql.event.collation_connection."

ER_EVENT_CANT_OPEN_TABLE_MYSQL_EVENT
  eng "Failed to open mysql.event Table."

ER_CANT_PARSE_STORED_ROUTINE_BODY
  eng "Parsing '%s.%s' routine body failed.%s"

ER_CANT_OPEN_TABLE_MYSQL_PROC
  eng "Failed to open mysql.proc Table."

ER_CANT_READ_TABLE_MYSQL_PROC
  eng "Failed to read mysql.proc table."

ER_FILE_EXISTS_DURING_UPGRADE
  eng "Found %s file in mysql schema. DD will create .ibd file with same name. Please rename table and start upgrade process again."

ER_CANT_OPEN_DATADIR_AFTER_UPGRADE_FAILURE
  eng "Unable to open the data directory %s during clean up after upgrade failed"

ER_CANT_SET_PATH_FOR
  eng "Failed to set path %s"

ER_CANT_OPEN_DIR
  eng "Failed to open dir %s"

OBSOLETE_ER_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Found empty nodeid specified in --ndb-cluster-connection-pool-nodeids='%s'."

OBSOLETE_ER_NDB_CANT_PARSE_NDB_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Could not parse '%s' in --ndb-cluster-connection-pool-nodeids='%s'."

OBSOLETE_ER_NDB_INVALID_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Invalid nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'."

OBSOLETE_ER_NDB_DUPLICATE_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: Found duplicate nodeid %d in --ndb-cluster-connection-pool-nodeids='%s'."

OBSOLETE_ER_NDB_POOL_SIZE_CLUSTER_CONNECTION_POOL_NODEIDS
  eng "NDB: The size of the cluster connection pool must be equal to the number of nodeids in --ndb-cluster-connection-pool-nodeids='%s'."

OBSOLETE_ER_NDB_NODEID_NOT_FIRST_CONNECTION_POOL_NODEIDS
  eng "NDB: The nodeid specified by --ndb-nodeid must be equal to the first nodeid in --ndb-cluster-connection-pool-nodeids='%s'."

OBSOLETE_ER_NDB_USING_NODEID
  eng "NDB: using nodeid %u"

OBSOLETE_ER_NDB_CANT_ALLOC_GLOBAL_NDB_CLUSTER_CONNECTION
  eng "NDB: failed to allocate global ndb cluster connection"

OBSOLETE_ER_NDB_CANT_ALLOC_GLOBAL_NDB_OBJECT
  eng "NDB: failed to allocate global ndb object"

OBSOLETE_ER_NDB_USING_NODEID_LIST
  eng "NDB[%u]: using nodeid %u"

OBSOLETE_ER_NDB_CANT_ALLOC_NDB_CLUSTER_CONNECTION
  eng "NDB[%u]: failed to allocate cluster connect object"

OBSOLETE_ER_NDB_STARTING_CONNECT_THREAD
  eng "NDB[%u]: starting connect thread"

OBSOLETE_ER_NDB_NODE_INFO
  eng "NDB[%u]: NodeID: %d, %s"

OBSOLETE_ER_NDB_CANT_START_CONNECT_THREAD
  eng "NDB[%u]: failed to start connect thread"

OBSOLETE_ER_NDB_GENERIC_ERROR
  eng "NDB: error (%u) %s"

OBSOLETE_ER_NDB_CPU_MASK_TOO_SHORT
  eng "Ignored receive thread CPU mask, mask too short, %u CPUs needed in mask, only %u CPUs provided"

ER_EVENT_ERROR_CREATING_QUERY_TO_WRITE_TO_BINLOG
  eng "Event Error: An error occurred while creating query string, before writing it into binary log."

ER_EVENT_SCHEDULER_ERROR_LOADING_FROM_DB
  eng "Event Scheduler: Error while loading from disk."

ER_EVENT_SCHEDULER_ERROR_GETTING_EVENT_OBJECT
  eng "Event Scheduler: Error getting event object."

ER_EVENT_SCHEDULER_GOT_BAD_DATA_FROM_TABLE
  eng "Event Scheduler: Error while loading events from mysql.events.The table probably contains bad data or is corrupted"

ER_EVENT_CANT_GET_LOCK_FOR_DROPPING_EVENT
  eng "Unable to obtain lock for dropping event %s from schema %s"

ER_EVENT_UNABLE_TO_DROP_EVENT
  eng "Unable to drop event %s from schema %s"

OBSOLETE_ER_BINLOG_ATTACHING_THREAD_MEMORY_FINALLY_AVAILABLE
  eng "Server overcomes the temporary 'out of memory' in '%d' tries while attaching to session thread during the group commit phase."

ER_BINLOG_CANT_RESIZE_CACHE
  eng "Unable to resize binlog IOCACHE auxiliary file"

ER_BINLOG_FILE_BEING_READ_NOT_PURGED
  eng "file %s was not purged because it was being read by thread number %u"

ER_BINLOG_IO_ERROR_READING_HEADER
  eng "I/O error reading the header from the binary log, errno=%d, io cache code=%d"

OBSOLETE_ER_BINLOG_CANT_OPEN_LOG
  eng "Failed to open log (file '%s', errno %d)"

OBSOLETE_ER_BINLOG_CANT_CREATE_CACHE_FOR_LOG
  eng "Failed to create a cache on log (file '%s')"

ER_BINLOG_FILE_EXTENSION_NUMBER_EXHAUSTED
  eng "Log filename extension number exhausted: %06lu. Please fix this by archiving old logs and updating the index files."

ER_BINLOG_FILE_NAME_TOO_LONG
  eng "Log filename too large: %s%s (%zu). Please fix this by archiving old logs and updating the index files."

ER_BINLOG_FILE_EXTENSION_NUMBER_RUNNING_LOW
  eng "Next log extension: %lu. Remaining log filename extensions: %lu. Please consider archiving some logs."

ER_BINLOG_CANT_OPEN_FOR_LOGGING
  eng "Could not open %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it."

ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE
  eng "MYSQL_BIN_LOG::open_index_file failed to sync the index file."

ER_BINLOG_ERROR_READING_GTIDS_FROM_RELAY_LOG
  eng "Error reading GTIDs from relaylog: %d"

ER_BINLOG_EVENTS_READ_FROM_APPLIER_METADATA
  eng "%lu events read in relaylog file '%s' for updating Retrieved_Gtid_Set and/or IO thread transaction parser state."

ER_BINLOG_ERROR_READING_GTIDS_FROM_BINARY_LOG
  eng "Error reading GTIDs from binary log: %d"

ER_BINLOG_EVENTS_READ_FROM_BINLOG_INFO
  eng "Read %lu events from binary log file '%s' to determine the GTIDs purged from binary logs."

ER_BINLOG_CANT_GENERATE_NEW_FILE_NAME
  eng "MYSQL_BIN_LOG::open failed to generate new file name."

ER_BINLOG_FAILED_TO_SYNC_INDEX_FILE_IN_OPEN
  eng "MYSQL_BIN_LOG::open failed to sync the index file."

ER_BINLOG_CANT_USE_FOR_LOGGING
  eng "Could not use %s for logging (error %d). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it."

ER_BINLOG_FAILED_TO_CLOSE_INDEX_FILE_WHILE_REBUILDING
  eng "While rebuilding index file %s: Failed to close the index file."

ER_BINLOG_FAILED_TO_DELETE_INDEX_FILE_WHILE_REBUILDING
  eng "While rebuilding index file %s: Failed to delete the existing index file. It could be that file is being used by some other process."

ER_BINLOG_FAILED_TO_RENAME_INDEX_FILE_WHILE_REBUILDING
  eng "While rebuilding index file %s: Failed to rename the new index file to the existing index file."

ER_BINLOG_FAILED_TO_OPEN_INDEX_FILE_AFTER_REBUILDING
  eng "After rebuilding the index file %s: Failed to open the index file."

ER_BINLOG_CANT_APPEND_LOG_TO_TMP_INDEX
  eng "MYSQL_BIN_LOG::add_log_to_index failed to append log file name: %s, to crash safe index file."

ER_BINLOG_CANT_LOCATE_OLD_BINLOG_OR_RELAY_LOG_FILES
  eng "Failed to locate old binlog or relay log files"

ER_BINLOG_CANT_DELETE_FILE
  eng "Failed to delete file '%s'"

ER_BINLOG_CANT_SET_TMP_INDEX_NAME
  eng "MYSQL_BIN_LOG::set_crash_safe_index_file_name failed to set file name."

ER_BINLOG_FAILED_TO_OPEN_TEMPORARY_INDEX_FILE
  eng "MYSQL_BIN_LOG::open_crash_safe_index_file failed to open temporary index file."

OBSOLETE_ER_BINLOG_ERROR_GETTING_NEXT_LOG_FROM_INDEX
  eng "next log error: %d  offset: %s  log: %s included: %d"

ER_BINLOG_CANT_OPEN_TMP_INDEX
  eng "%s failed to open the crash safe index file."

ER_BINLOG_CANT_COPY_INDEX_TO_TMP
  eng "%s failed to copy index file to crash safe index file."

ER_BINLOG_CANT_CLOSE_TMP_INDEX
  eng "%s failed to close the crash safe index file."

ER_BINLOG_CANT_MOVE_TMP_TO_INDEX
  eng "%s failed to move crash safe index file to index file."

ER_BINLOG_PURGE_LOGS_CALLED_WITH_FILE_NOT_IN_INDEX
  eng "MYSQL_BIN_LOG::purge_logs was called with file %s not listed in the index."

ER_BINLOG_PURGE_LOGS_CANT_SYNC_INDEX_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to sync the index file."

ER_BINLOG_PURGE_LOGS_CANT_COPY_TO_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to copy %s to register file."

ER_BINLOG_PURGE_LOGS_CANT_FLUSH_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to flush register file."

ER_BINLOG_PURGE_LOGS_CANT_UPDATE_INDEX_FILE
  eng "MYSQL_BIN_LOG::purge_logs failed to update the index file"

ER_BINLOG_PURGE_LOGS_FAILED_TO_PURGE_LOG
  eng "MYSQL_BIN_LOG::purge_logs failed to process registered files that would be purged."

ER_BINLOG_FAILED_TO_SET_PURGE_INDEX_FILE_NAME
  eng "MYSQL_BIN_LOG::set_purge_index_file_name failed to set file name."

ER_BINLOG_FAILED_TO_OPEN_REGISTER_FILE
  eng "MYSQL_BIN_LOG::open_purge_index_file failed to open register file."

ER_BINLOG_FAILED_TO_REINIT_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_index_entry failed to reinit register file for read"

ER_BINLOG_FAILED_TO_READ_REGISTER_FILE
  eng "MYSQL_BIN_LOG::purge_index_entry error %d reading from register file."

ER_CANT_STAT_FILE
  eng "Failed to execute mysql_file_stat on file '%s'"

ER_BINLOG_CANT_DELETE_LOG_FILE_DOES_INDEX_MATCH_FILES
  eng "Failed to delete log file '%s'; consider examining correspondence of your binlog index file to the actual binlog files"

ER_BINLOG_CANT_DELETE_FILE_AND_READ_BINLOG_INDEX
  eng "Failed to delete file '%s' and read the binlog index file"

ER_BINLOG_FAILED_TO_DELETE_LOG_FILE
  eng "Failed to delete log file '%s'"

ER_BINLOG_LOGGING_INCIDENT_TO_STOP_REPLICAS
  eng "%s An incident event has been written to the binary log which will stop the replicas."

ER_BINLOG_CANT_FIND_LOG_IN_INDEX
  eng "find_log_pos() failed (error: %d)"

ER_BINLOG_RECOVERING_AFTER_CRASH_USING
  eng "Recovering after a crash using %s"

ER_BINLOG_CANT_OPEN_CRASHED_BINLOG
  eng "Failed to open the crashed binlog file when source server is recovering it."

ER_BINLOG_CANT_TRIM_CRASHED_BINLOG
  eng "Failed to trim the crashed binlog file when source server is recovering it."

ER_BINLOG_CRASHED_BINLOG_TRIMMED
  eng "Crashed binlog file %s size is %llu, but recovered up to %llu. Binlog trimmed to %llu bytes."

ER_BINLOG_CANT_CLEAR_IN_USE_FLAG_FOR_CRASHED_BINLOG
  eng "Failed to clear LOG_EVENT_BINLOG_IN_USE_F for the crashed binlog file when source server is recovering it."

ER_BINLOG_FAILED_TO_RUN_AFTER_SYNC_HOOK
  eng "Failed to run 'after_sync' hooks"

ER_TURNING_LOGGING_OFF_FOR_THE_DURATION
  eng "%s Hence turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it."

ER_BINLOG_FAILED_TO_RUN_AFTER_FLUSH_HOOK
  eng "Failed to run 'after_flush' hooks"

OBSOLETE_ER_BINLOG_CRASH_RECOVERY_FAILED
  eng "Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete (or rename) binary log and start mysqld with --tc-heuristic-recover={commit|rollback}"

ER_BINLOG_WARNING_SUPPRESSED
  eng "The following warning was suppressed %d times during the last %d seconds in the error log"

ER_NDB_LOG_ENTRY
  eng "NDB: %s"

ER_NDB_LOG_ENTRY_WITH_PREFIX
  eng "NDB %s: %s"

OBSOLETE_ER_NDB_BINLOG_CANT_CREATE_PURGE_THD
  eng "NDB: Unable to purge %s.%s File=%s (failed to setup thd)"

ER_INNODB_UNKNOWN_COLLATION
  eng "Unknown collation #%lu."

ER_INNODB_INVALID_LOG_GROUP_HOME_DIR
  eng "syntax error in innodb_log_group_home_dir"

ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY
  eng "syntax error in innodb_undo_directory"

ER_INNODB_ILLEGAL_COLON_IN_POOL
  eng "InnoDB: innodb_buffer_pool_filename cannot have colon (:) in the file name."

ER_INNODB_INVALID_PAGE_SIZE
  eng "InnoDB: Invalid page size=%lu."

ER_INNODB_DIRTY_WATER_MARK_NOT_LOW
  eng "InnoDB: innodb_max_dirty_pages_pct_lwm cannot be set higher than innodb_max_dirty_pages_pct. Setting innodb_max_dirty_pages_pct_lwm to %lf"

ER_INNODB_IO_CAPACITY_EXCEEDS_MAX
  eng "InnoDB: innodb_io_capacity cannot be set higher than innodb_io_capacity_max. Setting innodb_io_capacity to %lu"

ER_INNODB_FILES_SAME
  eng "%s and %s file names seem to be the same."

ER_INNODB_UNREGISTERED_TRX_ACTIVE
  eng "Transaction not registered for MySQL 2PC, but transaction is active"

ER_INNODB_CLOSING_CONNECTION_ROLLS_BACK
  eng "MySQL is closing a connection that has an active InnoDB transaction. %llu row modifications will roll back."

ER_INNODB_TRX_XLATION_TABLE_OOM
  eng "InnoDB: fail to allocate memory for index translation table. Number of Index:%lu, array size:%lu"

ER_INNODB_CANT_FIND_INDEX_IN_INNODB_DD
  eng "Cannot find index %s in InnoDB index dictionary."

ER_INNODB_INDEX_COLUMN_INFO_UNLIKE_MYSQLS
  eng "Found index %s whose column info does not match that of MySQL."

OBSOLETE_ER_INNODB_CANT_OPEN_TABLE
  eng "Failed to open table %s."

ER_INNODB_CANT_BUILD_INDEX_XLATION_TABLE_FOR
  eng "Build InnoDB index translation table for Table %s failed"

ER_INNODB_PK_NOT_IN_MYSQL
  eng "Table %s has a primary key in InnoDB data dictionary, but not in MySQL!"

ER_INNODB_PK_ONLY_IN_MYSQL
  eng "Table %s has no primary key in InnoDB data dictionary, but has one in MySQL! If you created the table with a MySQL version < 3.23.54 and did not define a primary key, but defined a unique key with all non-NULL columns, then MySQL internally treats that key as the primary key. You can fix this error by dump + DROP + CREATE + reimport of the table."

ER_INNODB_CLUSTERED_INDEX_PRIVATE
  eng "Table %s key_used_on_scan is %lu even though there is no primary key inside InnoDB."

OBSOLETE_ER_INNODB_PARTITION_TABLE_LOWERCASED
  eng "Partition table %s opened after converting to lower case. The table may have been moved from a case-insensitive file system. Please recreate the table in the current file system."

ER_ERRMSG_REPLACEMENT_DODGY
  eng "Cannot replace error message (%s,%s,%s) \"%s\" with \"%s\"; wrong number or type of %% subsitutions."

ER_ERRMSG_REPLACEMENTS_FAILED
  eng "Table for error message replacements could not be found or read, or one or more replacements could not be applied."

ER_NPIPE_CANT_CREATE
  eng "%s: %s"

ER_PARTITION_MOVE_CREATED_DUPLICATE_ROW_PLEASE_FIX
  eng "Table '%-192s': Delete from part %d failed with error %d. But it was already inserted into part %d, when moving the misplaced row! Please manually fix the duplicate row: %s"

ER_AUDIT_CANT_ABORT_COMMAND
  eng "Command '%s' cannot be aborted. The trigger error was (%d) [%s]: %s"

ER_AUDIT_CANT_ABORT_EVENT
  eng "Event '%s' cannot be aborted. The trigger error was (%d) [%s]: %s"

ER_AUDIT_WARNING
  eng "%s. The trigger error was (%d) [%s]: %s"

OBSOLETE_ER_NDB_NUMBER_OF_CHANNELS
  eng "Replica SQL: Configuration with number of replication sources = %u' is not supported when applying to Ndb"

OBSOLETE_ER_NDB_REPLICA_PARALLEL_WORKERS
  eng "Replica SQL: Configuration 'replica_parallel_workers = %lu' is not supported when applying to Ndb"

OBSOLETE_ER_NDB_DISTRIBUTING_ERR
  eng "NDB %s: distributing %s err: %u"

ER_RPL_REPLICA_INSECURE_CHANGE_SOURCE
  eng "Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information."

OBSOLETE_ER_RPL_SLAVE_FLUSH_RELAY_LOGS_NOT_ALLOWED
  eng "FLUSH RELAY LOGS cannot be performed on channel '%-.192s'."

ER_RPL_REPLICA_INCORRECT_CHANNEL
  eng "Replica channel '%s' does not exist."

ER_FAILED_TO_FIND_DL_ENTRY
  eng "Can't find symbol '%-.128s' in library."

ER_FAILED_TO_OPEN_SHARED_LIBRARY
  eng "Can't open shared library '%-.192s' (errno: %d %-.128s)."

ER_THREAD_PRIORITY_IGNORED
  eng "Thread priority attribute setting in Resource Group SQL shall be ignored due to unsupported platform or insufficient privilege."

ER_BINLOG_CACHE_SIZE_TOO_LARGE
  eng "Option binlog_cache_size (%lu) is greater than max_binlog_cache_size (%lu); setting binlog_cache_size equal to max_binlog_cache_size."

ER_BINLOG_STMT_CACHE_SIZE_TOO_LARGE
  eng "Option binlog_stmt_cache_size (%lu) is greater than max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size equal to max_binlog_stmt_cache_size."

ER_FAILED_TO_GENERATE_UNIQUE_LOGFILE
  eng "Can't generate a unique log-filename %-.200s.(1-999)."

ER_FAILED_TO_READ_FILE
  eng "Error reading file '%-.200s' (errno: %d - %s)"

ER_FAILED_TO_WRITE_TO_FILE
  eng "Error writing file '%-.200s' (errno: %d - %s)"

ER_BINLOG_UNSAFE_MESSAGE_AND_STATEMENT
  eng "%s Statement: %s"

ER_FORCE_CLOSE_THREAD
  eng "%s: Forcing close of thread %ld  user: '%-.48s'."

ER_SERVER_SHUTDOWN_COMPLETE
  eng "%s: Shutdown complete (mysqld %s)  %s."

ER_RPL_CANT_HAVE_SAME_BASENAME
  eng "Cannot have same base name '%s' for both binary and relay logs. Please check %s (default '%s' if --log-bin option is not used, default '%s' if --log-bin option is used without argument) and %s (default '%s') options to ensure they do not conflict."

ER_RPL_GTID_MODE_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON
  eng "GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON."

ER_WARN_NO_SERVERID_SPECIFIED
  eng "You have not provided a mandatory server-id. Servers in a replication topology must have unique server-ids. Please refer to the proper server start-up parameters documentation."

ER_ABORTING_USER_CONNECTION
  eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)."

ER_SQL_MODE_MERGED_WITH_STRICT_MODE
  eng "'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release."

ER_GTID_PURGED_WAS_UPDATED
  eng "@@GLOBAL.GTID_PURGED was changed from '%s' to '%s'."

ER_GTID_EXECUTED_WAS_UPDATED
  eng "@@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'."

ER_DEPRECATE_MSG_WITH_REPLACEMENT
  eng "'%s' is deprecated and will be removed in a future release. Please use %s instead."

ER_TRG_CREATION_CTX_NOT_SET
  eng "Triggers for table `%-.64s`.`%-.64s` have no creation context"

ER_FILE_HAS_OLD_FORMAT
  eng "'%-.192s' has an old format, you should re-create the '%s' object(s)"

ER_VIEW_CREATION_CTX_NOT_SET
  eng "View `%-.64s`.`%-.64s` has no creation context"

OBSOLETE_ER_TABLE_NAME_CAUSES_TOO_LONG_PATH
  eng "Long database name and identifier for object resulted in a path length too long for table '%s'. Please check the path limit for your OS."

ER_TABLE_UPGRADE_REQUIRED
  eng "Table upgrade required. Please do \"REPAIR TABLE `%-.64s`\" or dump/reload to fix it!"

ER_GET_ERRNO_FROM_STORAGE_ENGINE
  eng "Got error %d - '%-.192s' from storage engine."

ER_ACCESS_DENIED_ERROR_WITHOUT_PASSWORD
  eng "Access denied for user '%-.48s'@'%-.64s'"

ER_ACCESS_DENIED_ERROR_WITH_PASSWORD
  eng "Access denied for user '%-.48s'@'%-.64s' (using password: %s)"

ER_ACCESS_DENIED_FOR_USER_ACCOUNT_LOCKED
  eng "Access denied for user '%-.48s'@'%-.64s'. Account is locked."

OBSOLETE_ER_MUST_CHANGE_EXPIRED_PASSWORD
  eng "Your password has expired. To log in you must change it using a client that supports expired passwords."

ER_SYSTEM_TABLES_NOT_SUPPORTED_BY_STORAGE_ENGINE
  eng "Storage engine '%s' does not support system tables. [%s.%s]."

OBSOLETE_ER_FILESORT_TERMINATED
  eng "Sort aborted"

ER_SERVER_STARTUP_MSG
  eng "%s: ready for connections. Version: '%s'  socket: '%s'  port: %d  %s."

ER_FAILED_TO_FIND_LOCALE_NAME
  eng "Unknown locale: '%-.64s'."

ER_FAILED_TO_FIND_COLLATION_NAME
  eng "Unknown collation: '%-.64s'."

ER_SERVER_OUT_OF_RESOURCES
  eng "Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space"

ER_SERVER_OUTOFMEMORY
  eng "Out of memory; restart server and try again (needed %d bytes)"

ER_INVALID_COLLATION_FOR_CHARSET
  eng "COLLATION '%s' is not valid for CHARACTER SET '%s'"

ER_CANT_START_ERROR_LOG_SERVICE
  eng "Failed to set %s at or around \"%s\" -- service is valid, but can not be initialized; please check its configuration and make sure it can read its input(s) and write to its output(s)."

ER_CREATING_NEW_UUID_FIRST_START
  eng "Generating a new UUID: %s."

ER_FAILED_TO_GET_ABSOLUTE_PATH
  eng "Failed to get absolute path of program executable %s"

ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_BOOTSTRAP
  eng "Failed to bootstrap performance schema components infrastructure."

ER_PERFSCHEMA_COMPONENTS_INFRASTRUCTURE_SHUTDOWN
  eng "Failed to deinit performance schema components infrastructure."

ER_DUP_FD_OPEN_FAILED
  eng "Could not open duplicate fd for %s: %s."

ER_SYSTEM_VIEW_INIT_FAILED
  eng "System views initialization failed."

ER_RESOURCE_GROUP_POST_INIT_FAILED
  eng "Resource group post initialization failed."

ER_RESOURCE_GROUP_SUBSYSTEM_INIT_FAILED
  eng "Resource Group subsystem initialization failed."

ER_FAILED_START_MYSQLD_DAEMON
  eng "Failed to start mysqld daemon. Check mysqld error log."

ER_CANNOT_CHANGE_TO_ROOT_DIR
  eng "Cannot change to root directory: %s."

ER_PERSISTENT_PRIVILEGES_BOOTSTRAP
  eng "Failed to bootstrap persistent privileges."

ER_BASEDIR_SET_TO
  eng "Basedir set to %s."

ER_RPL_FILTER_ADD_WILD_DO_TABLE_FAILED
  eng "Could not add wild do table rule '%s'!"

ER_RPL_FILTER_ADD_WILD_IGNORE_TABLE_FAILED
  eng "Could not add wild ignore table rule '%s'!"

ER_PRIVILEGE_SYSTEM_INIT_FAILED
  eng "The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual."

ER_CANNOT_SET_LOG_ERROR_SERVICES
  eng "Cannot set services \"%s\" requested in --log-error-services, using defaults."

ER_PERFSCHEMA_TABLES_INIT_FAILED
  eng "Performance schema tables initialization failed."

ER_TX_EXTRACTION_ALGORITHM_FOR_BINLOG_TX_DEPEDENCY_TRACKING
  eng "The transaction_write_set_extraction must be set to %s when binlog_transaction_dependency_tracking is %s."

OBSOLETE_ER_INVALID_REPLICATION_TIMESTAMPS
  eng "Invalid replication timestamps: original commit timestamp is more recent than the immediate commit timestamp. This may be an issue if delayed replication is active. Make sure that servers have their clocks set to the correct time. No further message will be emitted until after timestamps become valid again."

OBSOLETE_ER_RPL_TIMESTAMPS_RETURNED_TO_NORMAL
  eng "The replication timestamps have returned to normal values."

ER_BINLOG_FILE_OPEN_FAILED
  eng "%s."

ER_BINLOG_EVENT_WRITE_TO_STMT_CACHE_FAILED
  eng "Failed to write an incident event into stmt_cache."

ER_REPLICA_RELAY_LOG_TRUNCATE_INFO
  eng "Relaylog file %s size was %llu, but was truncated at %llu."

ER_REPLICA_RELAY_LOG_PURGE_FAILED
  eng "Unable to purge relay log files. %s:%s."

ER_RPL_REPLICA_FILTER_CREATE_FAILED
  eng "Replica: failed in creating filter for channel '%s'."

ER_RPL_REPLICA_GLOBAL_FILTERS_COPY_FAILED
  eng "Replica: failed in copying the global filters to its own per-channel filters on configuration for channel '%s'."

ER_RPL_REPLICA_RESET_FILTER_OPTIONS
  eng "There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded."

ER_MISSING_GRANT_SYSTEM_TABLE
  eng "The system table mysql.global_grants is missing. Please perform the MySQL upgrade procedure."

ER_MISSING_ACL_SYSTEM_TABLE
  eng "ACL table mysql.%.*s missing. Some operations may fail."

ER_ANONYMOUS_AUTH_ID_NOT_ALLOWED_IN_MANDATORY_ROLES
  eng "Can't set mandatory_role %s@%s: Anonymous authorization IDs are not allowed as roles."

ER_UNKNOWN_AUTH_ID_IN_MANDATORY_ROLE
  eng "Can't set mandatory_role: There's no such authorization ID %s@%s."

ER_WRITE_ROW_TO_PARTITION_FAILED
  eng "Table '%-192s' failed to move/insert a row from part %d into part %d: %s."

ER_RESOURCE_GROUP_METADATA_UPDATE_SKIPPED
  eng "Skipped updating resource group metadata in InnoDB read only mode."

ER_FAILED_TO_PERSIST_RESOURCE_GROUP_METADATA
  eng "Failed to persist resource group %s to Data Dictionary."

ER_FAILED_TO_DESERIALIZE_RESOURCE_GROUP
  eng "Failed to deserialize resource group %s."

ER_FAILED_TO_UPDATE_RESOURCE_GROUP
  eng "Update of resource group %s failed."

ER_RESOURCE_GROUP_VALIDATION_FAILED
  eng "Validation of resource group %s failed. Resource group is disabled."

ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP
  eng "Unable to allocate memory for Resource Group %s."

ER_FAILED_TO_ALLOCATE_MEMORY_FOR_RESOURCE_GROUP_HASH
  eng "Failed to allocate memory for resource group hash."

ER_FAILED_TO_ADD_RESOURCE_GROUP_TO_MAP
  eng "Failed to add resource group %s to resource group map."

ER_RESOURCE_GROUP_IS_DISABLED
  eng "Resource group feature is disabled. (Server is compiled with DISABLE_PSI_THREAD)."

ER_FAILED_TO_APPLY_RESOURCE_GROUP_CONTROLLER
  eng "Unable to apply resource group controller %s."

ER_FAILED_TO_ACQUIRE_LOCK_ON_RESOURCE_GROUP
  eng "Unable to acquire lock on the resource group %s. Hint to switch resource group shall be ignored."

ER_PFS_NOTIFICATION_FUNCTION_REGISTER_FAILED
  eng "PFS %s notification function registration failed."

ER_RES_GRP_SET_THR_AFFINITY_FAILED
  eng "Unable to bind thread id %llu to cpu id %u (error code %d - %-.192s)."

ER_RES_GRP_SET_THR_AFFINITY_TO_CPUS_FAILED
  eng "Unable to bind thread id %llu to cpu ids (error code %d - %-.192s)."

ER_RES_GRP_THD_UNBIND_FROM_CPU_FAILED
  eng "Unbind thread id %llu failed. (error code %d - %-.192s)."

ER_RES_GRP_SET_THREAD_PRIORITY_FAILED
  eng "Setting thread priority %d to thread id %llu failed. (error code %d - %-.192s)."

ER_RES_GRP_FAILED_TO_DETERMINE_NICE_CAPABILITY
  eng "Unable to determine CAP_SYS_NICE capability."

ER_RES_GRP_FAILED_TO_GET_THREAD_HANDLE
  eng "%s failed: Failed to get handle for thread %llu."

ER_RES_GRP_GET_THREAD_PRIO_NOT_SUPPORTED
  eng "Retrieval of thread priority unsupported on %s."

ER_RES_GRP_FAILED_DETERMINE_CPU_COUNT
  eng "Unable to determine the number of CPUs."

ER_RES_GRP_FEATURE_NOT_AVAILABLE
  eng "Resource group feature shall not be available. Incompatible thread handling option."

ER_RES_GRP_INVALID_THREAD_PRIORITY
  eng "Invalid thread priority %d for a %s resource group. Allowed range is [%d, %d]."

ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_CPUID_FAILED
  eng "bind_to_cpu failed: processor_bind for cpuid %u failed (error code %d - %-.192s)."

ER_RES_GRP_SOLARIS_PROCESSOR_BIND_TO_THREAD_FAILED
  eng "bind_to_cpu failed: processor_bind for thread %%llx with cpu id %u (error code %d - %-.192s)."

ER_RES_GRP_SOLARIS_PROCESSOR_AFFINITY_FAILED
  eng "%s failed: processor_affinity failed (error code %d - %-.192s)."

ER_DD_UPGRADE_RENAME_IDX_STATS_FILE_FAILED
  eng "Error in renaming mysql_index_stats.ibd."

ER_DD_UPGRADE_DD_OPEN_FAILED
  eng "Error in opening data directory %s."

ER_DD_UPGRADE_FAILED_TO_FETCH_TABLESPACES
  eng "Error in fetching list of tablespaces."

ER_DD_UPGRADE_FAILED_TO_ACQUIRE_TABLESPACE
  eng "Error in acquiring Tablespace for SDI insertion %s."

ER_DD_UPGRADE_FAILED_TO_RESOLVE_TABLESPACE_ENGINE
  eng "Error in resolving Engine name for tablespace %s with engine %s."

ER_FAILED_TO_CREATE_SDI_FOR_TABLESPACE
  eng "Error in creating SDI for %s tablespace."

ER_FAILED_TO_STORE_SDI_FOR_TABLESPACE
  eng "Error in storing SDI for %s tablespace."

ER_DD_UPGRADE_FAILED_TO_FETCH_TABLES
  eng "Error in fetching list of tables."

ER_DD_UPGRADE_DD_POPULATED
  eng "Finished populating Data Dictionary tables with data."

ER_DD_UPGRADE_INFO_FILE_OPEN_FAILED
  eng "Could not open the upgrade info file '%s' in the MySQL servers datadir, errno: %d."

ER_DD_UPGRADE_INFO_FILE_CLOSE_FAILED
  eng "Could not close the upgrade info file '%s' in the MySQL servers datadir, errno: %d."

ER_DD_UPGRADE_TABLESPACE_MIGRATION_FAILED
  eng "Got error %d from SE while migrating tablespaces."

ER_DD_UPGRADE_FAILED_TO_CREATE_TABLE_STATS
  eng "Error in creating TABLE statistics entry. Fix statistics data by using ANALYZE command."

ER_DD_UPGRADE_TABLE_STATS_MIGRATE_COMPLETED
  eng "Finished migrating TABLE statistics data."

ER_DD_UPGRADE_FAILED_TO_CREATE_INDEX_STATS
  eng "Error in creating Index statistics entry. Fix statistics data by using ANALYZE command."

ER_DD_UPGRADE_INDEX_STATS_MIGRATE_COMPLETED
  eng "Finished migrating INDEX statistics data."

ER_DD_UPGRADE_FAILED_FIND_VALID_DATA_DIR
  eng "Failed to find valid data directory."

ER_DD_UPGRADE_START
  eng "Starting upgrade of data directory."

ER_DD_UPGRADE_FAILED_INIT_DD_SE
  eng "Failed to initialize DD Storage Engine."

ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_ABORT
  eng "Found partially upgraded DD. Aborting upgrade and deleting all DD tables. Start the upgrade process again."

ER_DD_UPGRADE_FOUND_PARTIALLY_UPGRADED_DD_CONTINUE
  eng "Found partially upgraded DD. Upgrade will continue and start the server."

ER_DD_UPGRADE_SE_LOGS_FAILED
  eng "Error in upgrading engine logs."

ER_DD_UPGRADE_SDI_INFO_UPDATE_FAILED
  eng "Error in updating SDI information."

ER_SKIP_UPDATING_METADATA_IN_SE_RO_MODE
  eng "Skip updating %s metadata in InnoDB read-only mode."

ER_CREATED_SYSTEM_WITH_VERSION
  eng "Created system views with I_S version %d."

ER_UNKNOWN_ERROR_DETECTED_IN_SE
  eng "Unknown error detected %d in handler."

ER_READ_LOG_EVENT_FAILED
  eng "Error in Log_event::read_log_event(): '%s', data_len: %lu, event_type: %d."

ER_ROW_DATA_TOO_BIG_TO_WRITE_IN_BINLOG
  eng "The row data is greater than 4GB, which is too big to write to the binary log."

ER_FAILED_TO_CONSTRUCT_DROP_EVENT_QUERY
  eng "Unable to construct DROP EVENT SQL query string."

ER_FAILED_TO_BINLOG_DROP_EVENT
  eng "Unable to binlog drop event %s.%s."

ER_FAILED_TO_START_REPLICA_THREAD
  eng "Failed to start replica threads for channel '%s'."

ER_RPL_IO_THREAD_KILLED
  eng "%s%s."

ER_REPLICA_RECONNECT_FAILED
  eng "Failed registering on source, reconnecting to try again, log '%s' at position %s. %s."

ER_REPLICA_KILLED_AFTER_RECONNECT
  eng "Replica I/O thread killed during or after reconnect."

ER_REPLICA_NOT_STARTED_ON_SOME_CHANNELS
  eng "Some of the channels are not created/initialized properly. Check for additional messages above. You will not be able to start replication on those channels until the issue is resolved and the server restarted."

ER_FAILED_TO_ADD_RPL_FILTER
  eng "Failed to add a replication filter into filter map for channel '%.192s'."

ER_PER_CHANNEL_RPL_FILTER_CONF_FOR_GRP_RPL
  eng "There are per-channel replication filter(s) configured for group replication channel '%.192s' which is disallowed. The filter(s) have been discarded."

ER_RPL_FILTERS_NOT_ATTACHED_TO_CHANNEL
  eng "There are per-channel replication filter(s) configured for channel '%.192s' which does not exist. The filter(s) have been discarded."

ER_FAILED_TO_BUILD_DO_AND_IGNORE_TABLE_HASHES
  eng "An error occurred while building do_table and ignore_table rules to hashes for per-channel filter."

ER_CLONE_PLUGIN_NOT_LOADED_TRACE
  eng "Clone plugin cannot be loaded."

ER_CLONE_HANDLER_EXIST_TRACE
  eng "Clone Handler exists."

ER_CLONE_CREATE_HANDLER_FAIL_TRACE
  eng "Could not create Clone Handler."

ER_CYCLE_TIMER_IS_NOT_AVAILABLE
  eng "The CYCLE timer is not available. WAIT events in the performance_schema will not be timed."

ER_NANOSECOND_TIMER_IS_NOT_AVAILABLE
  eng "The NANOSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed."

ER_MICROSECOND_TIMER_IS_NOT_AVAILABLE
  eng "The MICROSECOND timer is not available. IDLE/STAGE/STATEMENT/TRANSACTION events in the performance_schema will not be timed."

ER_PFS_MALLOC_ARRAY_OVERFLOW
  eng "Failed to allocate memory for %zu chunks each of size %zu for buffer '%s' due to overflow."

ER_PFS_MALLOC_ARRAY_OOM
  eng "Failed to allocate %zu bytes for buffer '%s' due to out-of-memory."

ER_INNODB_FAILED_TO_FIND_IDX_WITH_KEY_NO
  eng "InnoDB could not find index %s key no %u for table %s through its index translation table."

ER_INNODB_FAILED_TO_FIND_IDX
  eng "Cannot find index %s in InnoDB index translation table."

ER_INNODB_FAILED_TO_FIND_IDX_FROM_DICT_CACHE
  eng "InnoDB could not find key no %u with name %s from dict cache for table %s."

ER_INNODB_ACTIVE_INDEX_CHANGE_FAILED
  eng "InnoDB: change_active_index(%u) failed."

ER_INNODB_DIFF_IN_REF_LEN
  eng "Stored ref len is %lu, but table ref len is %lu."

ER_WRONG_TYPE_FOR_COLUMN_PREFIX_IDX_FLD
  eng "MySQL is trying to create a column prefix index field, on an inappropriate data type. Table name %s, column name %s."

ER_INNODB_CANNOT_CREATE_TABLE
  eng "Cannot create table %s."

ER_INNODB_INTERNAL_INDEX
  eng "Found index %s in InnoDB index list but not its MySQL index number. It could be an InnoDB internal index."

ER_INNODB_IDX_CNT_MORE_THAN_DEFINED_IN_MYSQL
  eng "InnoDB: Table %s contains %lu indexes inside InnoDB, which is different from the number of indexes %u defined in MySQL."

ER_INNODB_IDX_CNT_FEWER_THAN_DEFINED_IN_MYSQL
  eng "Table %s contains fewer indexes inside InnoDB than are defined in the MySQL. Have you mixed up with data dictionary from different installation?"

ER_INNODB_IDX_COLUMN_CNT_DIFF
  eng "Index %s of %s has %lu columns unique inside InnoDB, but MySQL is asking statistics for %lu columns. Have you mixed data dictionary from different installation?"

ER_INNODB_USE_MONITOR_GROUP_NAME
  eng "Monitor counter '%s' cannot be turned on/off individually. Please use its module name to turn on/off the counters in the module as a group."

ER_INNODB_MONITOR_DEFAULT_VALUE_NOT_DEFINED
  eng "Default value is not defined for this set option. Please specify correct counter or module name."

ER_INNODB_MONITOR_IS_ENABLED
  eng "InnoDB: Monitor %s is already enabled."

ER_INNODB_INVALID_MONITOR_COUNTER_NAME
  eng "Invalid monitor counter : %s."

ER_WIN_LOAD_LIBRARY_FAILED
  eng "LoadLibrary(\"%s\") failed: GetLastError returns %lu."

ER_PARTITION_HANDLER_ADMIN_MSG
  eng "%s."

ER_RPL_AM_INIT_INFO_MSG
  eng "%s."

ER_DD_UPGRADE_TABLE_INTACT_ERROR
  eng "%s."

ER_SERVER_INIT_COMPILED_IN_COMMANDS
  eng "%s."

ER_MYISAM_CHECK_METHOD_ERROR
  eng "%s."

ER_MYISAM_CRASHED_ERROR
  eng "%s."

ER_WAITPID_FAILED
  eng "Unable to wait for process %lld."

ER_FAILED_TO_FIND_MYSQLD_STATUS
  eng "Unable to determine if daemon is running: %s (rc=%d)."

ER_INNODB_ERROR_LOGGER_MSG
  eng "%s"

ER_INNODB_ERROR_LOGGER_FATAL_MSG
  eng "[FATAL] InnoDB: %s"

ER_DEPRECATED_SYNTAX_WITH_REPLACEMENT
  eng "The syntax '%s' is deprecated and will be removed in a future release. Please use %s instead."

ER_DEPRECATED_SYNTAX_NO_REPLACEMENT
  eng "The syntax '%s' is deprecated and will be removed in a future release."

ER_DEPRECATE_MSG_NO_REPLACEMENT
  eng "'%s' is deprecated and will be removed in a future release."

ER_LOG_PRINTF_MSG
  eng "%s"

ER_BINLOG_LOGGING_NOT_POSSIBLE
  eng "Binary logging not possible. Message: %s."

ER_FAILED_TO_SET_PERSISTED_OPTIONS
  eng "Failed to set persisted options."

ER_COMPONENTS_FAILED_TO_ACQUIRE_SERVICE_IMPLEMENTATION
  eng "Cannot acquire specified service implementation: '%.192s'."

ER_RES_GRP_INVALID_VCPU_RANGE
  eng "Invalid VCPU range %u-%u."

ER_RES_GRP_INVALID_VCPU_ID
  eng "Invalid cpu id %u."

ER_ERROR_DURING_FLUSH_LOG_COMMIT_PHASE
  eng "Got error %d during FLUSH_LOGS."

ER_DROP_DATABASE_FAILED_RMDIR_MANUALLY
  eng "Problem while dropping database. Can't remove database directory (%s). Please remove it manually."

ER_EXPIRE_LOGS_DAYS_IGNORED
  eng "The option expire_logs_days cannot be used together with option binlog_expire_logs_seconds. Therefore, value of expire_logs_days is ignored."

ER_BINLOG_MALFORMED_OR_OLD_RELAY_LOG
  eng "malformed or very old relay log which does not have FormatDescriptor."

ER_DD_UPGRADE_VIEW_COLUMN_NAME_TOO_LONG
  eng "Upgrade of view '%s.%s' failed. Re-create the view with the explicit column name lesser than 64 characters."

ER_TABLE_NEEDS_DUMP_UPGRADE
  eng "Table upgrade required for `%-.64s`.`%-.64s`. Please dump/reload table to fix it!"

ER_DD_UPGRADE_FAILED_TO_UPDATE_VER_NO_IN_TABLESPACE
  eng "Error in updating version number in %s tablespace."

ER_KEYRING_MIGRATION_FAILED
  eng "Keyring migration failed."

ER_KEYRING_MIGRATION_SUCCESSFUL
  eng "Keyring migration successful."

ER_RESTART_RECEIVED_INFO
  eng "Received RESTART from user %s.  Restarting mysqld (Version: %s)."

ER_LCTN_CHANGED
  eng "Different lower_case_table_names settings for server ('%u') and data dictionary ('%u')."

ER_DD_INITIALIZE
  eng "Data dictionary initializing version '%u'."

ER_DD_RESTART
  eng "Data dictionary restarting version '%u'."

ER_DD_UPGRADE
  eng "Data dictionary upgrading from version '%u' to '%u'."

ER_DD_UPGRADE_OFF
  eng "Data dictionary upgrade prohibited by the command line option '--no_dd_upgrade'."

ER_DD_UPGRADE_VERSION_NOT_SUPPORTED
  eng "Upgrading the data dictionary from dictionary version '%u' is not supported."

ER_DD_UPGRADE_SCHEMA_UNAVAILABLE
  eng "Upgrading the data dictionary failed, temporary schema name '%-.192s' not available."

ER_DD_MINOR_DOWNGRADE
  eng "Data dictionary minor downgrade from version '%u' to '%u'."

ER_DD_MINOR_DOWNGRADE_VERSION_NOT_SUPPORTED
  eng "Minor downgrade of the Data dictionary from dictionary version '%u' is not supported."

ER_DD_NO_VERSION_FOUND
  eng "No data dictionary version number found."

ER_THREAD_POOL_NOT_SUPPORTED_ON_PLATFORM
  eng "Thread pool not supported, requires a minimum of %s."

ER_THREAD_POOL_SIZE_TOO_LOW
  eng "thread_pool_size=0 means thread pool disabled, Allowed range of thread_pool_size is %d-%d."

ER_THREAD_POOL_SIZE_TOO_HIGH
  eng "thread_pool_size=%lu is too high, %d is maximum, thread pool is disabled. Allowed range of thread_pool_size is %d-%d."

ER_THREAD_POOL_ALGORITHM_INVALID
  eng "thread_pool_algorithm can be set to 0 and 1, 0 indicates the default low concurrency algorithm, 1 means a high concurrency algorithm."

ER_THREAD_POOL_INVALID_STALL_LIMIT
  eng "thread_pool_stall_limit can be %d at minimum and %d at maximum, smaller values would render the thread pool fairly useless and higher values could make it possible to have undetected deadlock issues in the MySQL Server."

ER_THREAD_POOL_INVALID_PRIO_KICKUP_TIMER
  eng "Invalid value of thread_pool_prio_kickup_timer specified. Value of thread_pool_prio_kickup_timer should be in range 0-4294967294."

ER_THREAD_POOL_MAX_UNUSED_THREADS_INVALID
  eng "thread_pool_max_unused_threads cannot be set higher than %d."

ER_THREAD_POOL_CON_HANDLER_INIT_FAILED
  eng "Failed to instantiate the connection handler object."

ER_THREAD_POOL_INIT_FAILED
  eng "Failed to initialize thread pool plugin."

OBSOLETE_ER_THREAD_POOL_PLUGIN_STARTED
  eng "Thread pool plugin started successfully with parameters: thread_pool_size = %lu, thread_pool_algorithm = %s, thread_pool_stall_limit = %u, thread_pool_prio_kickup_timer = %u, thread_pool_max_unused_threads = %u, thread_pool_high_priority_connection = %d."

ER_THREAD_POOL_CANNOT_SET_THREAD_SPECIFIC_DATA
  eng "Can't setup connection teardown thread-specific data."

ER_THREAD_POOL_FAILED_TO_CREATE_CONNECT_HANDLER_THD
  eng "Creation of connect handler thread failed."

ER_THREAD_POOL_FAILED_TO_CREATE_THD_AND_AUTH_CONN
  eng "Failed to create thd and authenticate connection."

ER_THREAD_POOL_FAILED_PROCESS_CONNECT_EVENT
  eng "Failed to process connection event."

ER_THREAD_POOL_FAILED_TO_CREATE_POOL
  eng "Can't create pool thread (error %d, errno: %d)."

ER_THREAD_POOL_RATE_LIMITED_ERROR_MSGS
  eng "%.*s."

ER_TRHEAD_POOL_LOW_LEVEL_INIT_FAILED
  eng "tp_group_low_level_init() failed."

ER_THREAD_POOL_LOW_LEVEL_REARM_FAILED
  eng "Rearm failed even after 30 seconds, can't continue without notify socket."

ER_THREAD_POOL_BUFFER_TOO_SMALL
  eng "%s: %s buffer is too small"

ER_MECAB_NOT_SUPPORTED
  eng "Mecab v%s is not supported, the lowest version supported is v%s."

ER_MECAB_NOT_VERIFIED
  eng "Mecab v%s is not verified, the highest version supported is v%s."

ER_MECAB_CREATING_MODEL
  eng "Mecab: Trying createModel(%s)."

ER_MECAB_FAILED_TO_CREATE_MODEL
  eng "Mecab: createModel() failed: %s."

ER_MECAB_FAILED_TO_CREATE_TRIGGER
  eng "Mecab: createTagger() failed: %s."

ER_MECAB_UNSUPPORTED_CHARSET
  eng "Mecab: Unsupported dictionary charset %s."

ER_MECAB_CHARSET_LOADED
  eng "Mecab: Loaded dictionary charset is %s."

ER_MECAB_PARSE_FAILED
  eng "Mecab: parse() failed: %s."

ER_MECAB_OOM_WHILE_PARSING_TEXT
  eng "Mecab: parse() failed: out of memory."

ER_MECAB_CREATE_LATTICE_FAILED
  eng "Mecab: createLattice() failed: %s."

ER_SEMISYNC_TRACE_ENTER_FUNC
  eng "---> %s enter."

ER_SEMISYNC_TRACE_EXIT_WITH_INT_EXIT_CODE
  eng "<--- %s exit (%d)."

ER_SEMISYNC_TRACE_EXIT_WITH_BOOL_EXIT_CODE
  eng "<--- %s exit (%s)."

ER_SEMISYNC_TRACE_EXIT
  eng "<--- %s exit."

ER_SEMISYNC_RPL_INIT_FOR_TRX
  eng "Semi-sync replication initialized for transactions."

ER_SEMISYNC_FAILED_TO_ALLOCATE_TRX_NODE
  eng "%s: transaction node allocation failed for: (%s, %lu)."

ER_SEMISYNC_BINLOG_WRITE_OUT_OF_ORDER
  eng "%s: binlog write out-of-order, tail (%s, %lu), new node (%s, %lu)."

ER_SEMISYNC_INSERT_LOG_INFO_IN_ENTRY
  eng "%s: insert (%s, %lu) in entry(%u)."

ER_SEMISYNC_PROBE_LOG_INFO_IN_ENTRY
  eng "%s: probe (%s, %lu) in entry(%u)."

ER_SEMISYNC_CLEARED_ALL_ACTIVE_TRANSACTION_NODES
  eng "%s: cleared all nodes."

ER_SEMISYNC_CLEARED_ACTIVE_TRANSACTION_TILL_POS
  eng "%s: cleared %d nodes back until pos (%s, %lu)."

ER_SEMISYNC_REPLY_MAGIC_NO_ERROR
  eng "Read semi-sync reply magic number error."

ER_SEMISYNC_REPLY_PKT_LENGTH_TOO_SMALL
  eng "Read semi-sync reply length error: packet is too small."

ER_SEMISYNC_REPLY_BINLOG_FILE_TOO_LARGE
  eng "Read semi-sync reply binlog file length too large."

ER_SEMISYNC_SERVER_REPLY
  eng "%s: Got reply(%s, %lu) from server %u."

ER_SEMISYNC_FUNCTION_CALLED_TWICE
  eng "%s called twice."

ER_SEMISYNC_RPL_ENABLED_ON_SOURCE
  eng "Semi-sync replication enabled on the source."

ER_SEMISYNC_SOURCE_OOM
  eng "Cannot allocate memory to enable semi-sync on the source."

ER_SEMISYNC_DISABLED_ON_SOURCE
  eng "Semi-sync replication disabled on the source."

ER_SEMISYNC_FORCED_SHUTDOWN
  eng "SEMISYNC: Forced shutdown. Some updates might not be replicated."

ER_SEMISYNC_SOURCE_GOT_REPLY_AT_POS
  eng "%s: Got reply at (%s, %lu)."

ER_SEMISYNC_SOURCE_SIGNAL_ALL_WAITING_THREADS
  eng "%s: signal all waiting threads."

ER_SEMISYNC_SOURCE_TRX_WAIT_POS
  eng "%s: wait pos (%s, %lu), repl(%d)."

ER_SEMISYNC_BINLOG_REPLY_IS_AHEAD
  eng "%s: Binlog reply is ahead (%s, %lu)."

ER_SEMISYNC_MOVE_BACK_WAIT_POS
  eng "%s: move back wait position (%s, %lu)."

ER_SEMISYNC_INIT_WAIT_POS
  eng "%s: init wait position (%s, %lu)."

ER_SEMISYNC_WAIT_TIME_FOR_BINLOG_SENT
  eng "%s: wait %lu ms for binlog sent (%s, %lu)."

ER_SEMISYNC_WAIT_FOR_BINLOG_TIMEDOUT
  eng "Timeout waiting for reply of binlog (file: %s, pos: %lu), semi-sync up to file %s, position %lu."

ER_SEMISYNC_WAIT_TIME_ASSESSMENT_FOR_COMMIT_TRX_FAILED
  eng "Assessment of waiting time for commitTrx failed at wait position (%s, %lu)."

ER_SEMISYNC_RPL_SWITCHED_OFF
  eng "Semi-sync replication switched OFF."

ER_SEMISYNC_RPL_SWITCHED_ON
  eng "Semi-sync replication switched ON at (%s, %lu)."

ER_SEMISYNC_NO_SPACE_IN_THE_PKT
  eng "No enough space in the packet for semi-sync extra header, semi-sync replication disabled."

ER_SEMISYNC_SYNC_HEADER_UPDATE_INFO
  eng "%s: server(%d), (%s, %lu) sync(%d), repl(%d)."

ER_SEMISYNC_FAILED_TO_INSERT_TRX_NODE
  eng "Semi-sync failed to insert tranx_node for binlog file: %s, position: %lu."

ER_SEMISYNC_TRX_SKIPPED_AT_POS
  eng "%s: Transaction skipped at (%s, %lu)."

ER_SEMISYNC_SOURCE_FAILED_ON_NET_FLUSH
  eng "Semi-sync source failed on net_flush() before waiting for replica reply."

ER_SEMISYNC_RECEIVED_ACK_IS_SMALLER
  eng "The received ack is smaller than m_greatest_ack."

ER_SEMISYNC_ADD_ACK_TO_SLOT
  eng "Add the ack into slot %u."

ER_SEMISYNC_UPDATE_EXISTING_REPLICA_ACK
  eng "Update an exsiting ack in slot %u."

ER_SEMISYNC_FAILED_TO_START_ACK_RECEIVER_THD
  eng "Failed to start semi-sync ACK receiver thread,  could not create thread(errno:%d)."

ER_SEMISYNC_STARTING_ACK_RECEIVER_THD
  eng "Starting ack receiver thread."

ER_SEMISYNC_FAILED_TO_WAIT_ON_DUMP_SOCKET
  eng "Failed to wait on semi-sync dump sockets, error: errno=%d."

ER_SEMISYNC_STOPPING_ACK_RECEIVER_THREAD
  eng "Stopping ack receiver thread."

ER_SEMISYNC_FAILED_REGISTER_REPLICA_TO_RECEIVER
  eng "Failed to register replica to semi-sync ACK receiver thread."

ER_SEMISYNC_START_BINLOG_DUMP_TO_REPLICA
  eng "Start %s binlog_dump to replica (server_id: %d), pos(%s, %lu)."

ER_SEMISYNC_STOP_BINLOG_DUMP_TO_REPLICA
  eng "Stop %s binlog_dump to replica (server_id: %d)."

ER_SEMISYNC_UNREGISTER_TRX_OBSERVER_FAILED
  eng "unregister_trans_observer failed."

ER_SEMISYNC_UNREGISTER_BINLOG_STORAGE_OBSERVER_FAILED
  eng "unregister_binlog_storage_observer failed."

ER_SEMISYNC_UNREGISTER_BINLOG_TRANSMIT_OBSERVER_FAILED
  eng "unregister_binlog_transmit_observer failed."

ER_SEMISYNC_UNREGISTERED_REPLICATOR
  eng "unregister_replicator OK."

ER_SEMISYNC_SOCKET_FD_TOO_LARGE
  eng "Semisync replica socket fd is %u. select() cannot handle if the socket fd is bigger than %u (FD_SETSIZE)."

ER_SEMISYNC_REPLICA_REPLY
  eng "%s: reply - %d."

ER_SEMISYNC_MISSING_MAGIC_NO_FOR_SEMISYNC_PKT
  eng "Missing magic number for semi-sync packet, packet len: %lu."

ER_SEMISYNC_REPLICA_START
  eng "Replica I/O thread: Start %s replication to source '%s@%s:%d' in log '%s' at position %lu."

ER_SEMISYNC_REPLICA_REPLY_WITH_BINLOG_INFO
  eng "%s: reply (%s, %lu)."

ER_SEMISYNC_REPLICA_NET_FLUSH_REPLY_FAILED
  eng "Semi-sync replica net_flush() reply failed."

ER_SEMISYNC_REPLICA_SEND_REPLY_FAILED
  eng "Semi-sync replica send reply failed: %s (%d)."

ER_SEMISYNC_EXECUTION_FAILED_ON_SOURCE
  eng "Execution failed on source: %s; error %d"

ER_SEMISYNC_NOT_SUPPORTED_BY_SOURCE
  eng "Source server does not support semi-sync, fallback to asynchronous replication"

ER_SEMISYNC_REPLICA_SET_FAILED
  eng "Set 'rpl_semi_sync_replica=1' on source failed"

ER_SEMISYNC_FAILED_TO_STOP_ACK_RECEIVER_THD
  eng "Failed to stop ack receiver thread on my_thread_join, errno(%d)."

ER_FIREWALL_FAILED_TO_READ_FIREWALL_TABLES
  eng "Failed to read the firewall tables"

ER_FIREWALL_FAILED_TO_REG_DYNAMIC_PRIVILEGES
  eng "Failed to register dynamic privileges"

ER_FIREWALL_RECORDING_STMT_WAS_TRUNCATED
  eng "Statement was truncated and not recorded: %s"

ER_FIREWALL_RECORDING_STMT_WITHOUT_TEXT
  eng "Statement with no text was not recorded"

ER_FIREWALL_SUSPICIOUS_STMT
  eng "SUSPICIOUS STATEMENT from '%s'. Reason: %s Statement: %s"

ER_FIREWALL_ACCESS_DENIED
  eng "ACCESS DENIED for '%s'. Reason: %s Statement: %s"

ER_FIREWALL_SKIPPED_UNKNOWN_USER_MODE
  eng "Skipped unknown user mode '%s'"

ER_FIREWALL_RELOADING_CACHE
  eng "Reloading cache from disk"

ER_FIREWALL_RESET_FOR_USER
  eng "FIREWALL RESET for '%s'"

ER_FIREWALL_STATUS_FLUSHED
  eng "Counters are reset to zero"

ER_KEYRING_LOGGER_ERROR_MSG
  eng "%s"

ER_AUDIT_LOG_FILTER_IS_NOT_INSTALLED
  eng "Audit Log plugin supports filtering mode, which has not been installed yet. Audit Log plugin will run in the legacy mode, which will be removed in the next release."

ER_AUDIT_LOG_SWITCHING_TO_INCLUDE_LIST
  eng "Previously exclude list is used, now we start using include list, exclude list is set to NULL."

ER_AUDIT_LOG_CANNOT_SET_LOG_POLICY_WITH_OTHER_POLICIES
  eng "Cannot set audit_log_policy simultaneously with either audit_log_connection_policy or  audit_log_statement_policy, setting audit_log_connection_policy and audit_log_statement_policy based on audit_log_policy."

ER_AUDIT_LOG_ONLY_INCLUDE_LIST_USED
  eng "Both include and exclude lists provided, include list is preferred, exclude list is set to NULL."

ER_AUDIT_LOG_INDEX_MAP_CANNOT_ACCESS_DIR
  eng "Could not access '%s' directory."

ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED
  eng "Could not rename file from '%s' to '%s'."

ER_AUDIT_LOG_WRITER_DEST_FILE_ALREADY_EXISTS
  eng "File '%s' should not exist. It may be incomplete. The server crashed."

ER_AUDIT_LOG_WRITER_RENAME_FILE_FAILED_REMOVE_FILE_MANUALLY
  eng "Could not rename file from '%s' to '%s'. Remove the file manually."

ER_AUDIT_LOG_WRITER_INCOMPLETE_FILE_RENAMED
  eng "Incomplete file renamed from '%s' to '%s'."

ER_AUDIT_LOG_WRITER_FAILED_TO_WRITE_TO_FILE
  eng "Error writing file \'%-.200s\' (errno: %d - %s)."

ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_ENCRYPTION
  eng "Could not initialize audit log file encryption."

ER_AUDIT_LOG_EC_WRITER_FAILED_TO_INIT_COMPRESSION
  eng "Could not initialize audit log file compression."

ER_AUDIT_LOG_EC_WRITER_FAILED_TO_CREATE_FILE
  eng "Could not create '%s' file for audit logging."

ER_AUDIT_LOG_RENAME_LOG_FILE_BEFORE_FLUSH
  eng "Audit log file (%s) must be manually renamed before audit_log_flush is set to true."

ER_AUDIT_LOG_FILTER_RESULT_MSG
  eng "%s"

ER_AUDIT_LOG_JSON_READER_FAILED_TO_PARSE
  eng "Error parsing JSON event. Event not accessible."

ER_AUDIT_LOG_JSON_READER_BUF_TOO_SMALL
  eng "Buffer is too small to hold JSON event. Number of events skipped: %zu."

ER_AUDIT_LOG_JSON_READER_FAILED_TO_OPEN_FILE
  eng "Could not open JSON file for reading. Reading next file if exists."

ER_AUDIT_LOG_JSON_READER_FILE_PARSING_ERROR
  eng "JSON file parsing error. Reading next file if exists"

OBSOLETE_ER_AUDIT_LOG_FILTER_INVALID_COLUMN_COUNT
  eng "Invalid column count in the '%s.%s' table."

OBSOLETE_ER_AUDIT_LOG_FILTER_INVALID_COLUMN_DEFINITION
  eng "Invalid column definition of the '%s.%s' table."

ER_AUDIT_LOG_FILTER_FAILED_TO_STORE_TABLE_FLDS
  eng "Could not store field of the %s table."

ER_AUDIT_LOG_FILTER_FAILED_TO_UPDATE_TABLE
  eng "Could not update %s table."

ER_AUDIT_LOG_FILTER_FAILED_TO_INSERT_INTO_TABLE
  eng "Could not insert into %s table."

ER_AUDIT_LOG_FILTER_FAILED_TO_DELETE_FROM_TABLE
  eng "Could not delete from %s table."

ER_AUDIT_LOG_FILTER_FAILED_TO_INIT_TABLE_FOR_READ
  eng "Could not initialize %s table for reading."

ER_AUDIT_LOG_FILTER_FAILED_TO_READ_TABLE
  eng "Could not read %s table."

ER_AUDIT_LOG_FILTER_FAILED_TO_CLOSE_TABLE_AFTER_READING
  eng "Could not close %s table reading."

ER_AUDIT_LOG_FILTER_USER_AND_HOST_CANNOT_BE_EMPTY
  eng "Both user and host columns of %s table cannot be empty."

ER_AUDIT_LOG_FILTER_FLD_FILTERNAME_CANNOT_BE_EMPTY
  eng "Filtername column of %s table cannot be empty."

ER_VALIDATE_PWD_DICT_FILE_NOT_SPECIFIED
  eng "Dictionary file not specified"

ER_VALIDATE_PWD_DICT_FILE_NOT_LOADED
  eng "Dictionary file not loaded"

ER_VALIDATE_PWD_DICT_FILE_TOO_BIG
  eng "Dictionary file size exceeded MAX_DICTIONARY_FILE_LENGTH, not loaded"

ER_VALIDATE_PWD_FAILED_TO_READ_DICT_FILE
  eng "Exception while reading the dictionary file"

ER_VALIDATE_PWD_FAILED_TO_GET_FLD_FROM_SECURITY_CTX
  eng "Can't retrieve the %s from the security context"

ER_VALIDATE_PWD_FAILED_TO_GET_SECURITY_CTX
  eng "Can't retrieve the security context"

ER_VALIDATE_PWD_LENGTH_CHANGED
  eng "Effective value of validate_password_length is changed. New value is %d"

ER_REWRITER_QUERY_ERROR_MSG
  eng "%s"

ER_REWRITER_QUERY_FAILED
  eng "Rewritten query failed to parse:%s"

ER_XPLUGIN_STARTUP_FAILED
  eng "Startup failed with error \"%s\""

OBSOLETE_ER_XPLUGIN_SERVER_EXITING
  eng "Exiting"

OBSOLETE_ER_XPLUGIN_SERVER_EXITED
  eng "Exit done"

ER_XPLUGIN_USING_SSL_CONF_FROM_SERVER
  eng "Using SSL configuration from MySQL Server"

ER_XPLUGIN_USING_SSL_CONF_FROM_MYSQLX
  eng "Using SSL configuration from Mysqlx Plugin"

ER_XPLUGIN_FAILED_TO_USE_SSL_CONF
  eng "Neither MySQL Server nor Mysqlx Plugin has valid SSL configuration"

ER_XPLUGIN_USING_SSL_FOR_TLS_CONNECTION
  eng "Using %s for TLS connections"

ER_XPLUGIN_REFERENCE_TO_SECURE_CONN_WITH_XPLUGIN
  eng "For more information, please see the Using Secure Connections with X Plugin section in the MySQL documentation"

ER_XPLUGIN_ERROR_MSG
  eng "%s"

ER_SHA_PWD_FAILED_TO_PARSE_AUTH_STRING
  eng "Failed to parse stored authentication string for %s. Please check if mysql.user table not corrupted"

ER_SHA_PWD_FAILED_TO_GENERATE_MULTI_ROUND_HASH
  eng "Error in generating multi-round hash for %s. Plugin can not perform authentication without it. This may be a transient problem"

ER_SHA_PWD_AUTH_REQUIRES_RSA_OR_SSL
  eng "Authentication requires either RSA keys or SSL encryption"

ER_SHA_PWD_RSA_KEY_TOO_LONG
  eng "RSA key cipher length of %u is too long. Max value is %u"

ER_PLUGIN_COMMON_FAILED_TO_OPEN_FILTER_TABLES
  eng "Failed to open the %s filter tables"

ER_PLUGIN_COMMON_FAILED_TO_OPEN_TABLE
  eng "Failed to open '%s.%s' %s table"

ER_AUTH_LDAP_ERROR_LOGGER_ERROR_MSG
  eng "%s"

ER_CONN_CONTROL_ERROR_MSG
  eng "%s"

ER_GRP_RPL_ERROR_MSG
  eng "%s"

ER_SHA_PWD_SALT_FOR_USER_CORRUPT
  eng "Password salt for user '%s' is corrupt"

ER_SYS_VAR_COMPONENT_OOM
  eng "Out of memory for component system variable '%s'."

ER_SYS_VAR_COMPONENT_VARIABLE_SET_READ_ONLY
  eng "variable %s of component %s was forced to be read-only: string variable without update_func and PLUGIN_VAR_MEMALLOC flag."

ER_SYS_VAR_COMPONENT_UNKNOWN_VARIABLE_TYPE
  eng "Unknown variable type code 0x%x in component '%s'."

ER_SYS_VAR_COMPONENT_FAILED_TO_PARSE_VARIABLE_OPTIONS
  eng "Parsing options for variable '%s' failed."

ER_SYS_VAR_COMPONENT_FAILED_TO_MAKE_VARIABLE_PERSISTENT
  eng "Setting persistent options for component variable '%s' failed."

ER_COMPONENT_FILTER_CONFUSED
  eng "The log-filter component \"%s\" got confused at \"%s\" (state: %s) ..."

ER_STOP_REPLICA_IO_THREAD_DISK_SPACE
  eng "Waiting until I/O thread for channel '%s' finish writing to disk before stopping. Free some disk space or use 'KILL' to abort I/O thread operation. Notice that aborting the I/O thread while rotating the relay log might corrupt the relay logs, requiring a server restart to fix it."

ER_LOG_FILE_CANNOT_OPEN
  eng "Could not use %s for logging (error %d - %s). Turning logging off for the server process. To turn it on again: fix the cause, then%s restart the MySQL server."

OBSOLETE_ER_UNABLE_TO_COLLECT_LOG_STATUS
  eng "Unable to collect information for column '%-.192s': %-.192s."

OBSOLETE_ER_DEPRECATED_UTF8_ALIAS
  eng "'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous."

OBSOLETE_ER_DEPRECATED_NATIONAL
  eng "NATIONAL/NCHAR/NVARCHAR implies the character set UTF8MB3, which will be replaced by UTF8MB4 in a future release. Please consider using CHAR(x) CHARACTER SET UTF8MB4 in order to be unambiguous."

OBSOLETE_ER_SLAVE_POSSIBLY_DIVERGED_AFTER_DDL
  eng "A commit for an atomic DDL statement was unsuccessful on the source and the replica. The replica supports atomic DDL statements but the source does not, so the action taken by the replica and source might differ. Check that their states have not diverged before proceeding."

ER_PERSIST_OPTION_STATUS
  eng "Configuring persisted options failed: \"%s\"."

ER_NOT_IMPLEMENTED_GET_TABLESPACE_STATISTICS
  eng "The storage engine '%-.192s' does not provide dynamic table statistics"

OBSOLETE_ER_UNABLE_TO_SET_OPTION
  eng "This option cannot be set %s."

OBSOLETE_ER_RESERVED_TABLESPACE_NAME
  eng "The table '%-.192s' may not be created in the reserved tablespace '%-.192s'."

ER_SSL_FIPS_MODE_ERROR
   eng "SSL fips mode error: %s"

ER_CONN_INIT_CONNECT_IGNORED
  eng "init_connect variable is ignored for user: %s host: %s due to expired password."

OBSOLETE_ER_UNSUPPORTED_SQL_MODE
  eng "sql_mode=0x%08x is not supported"

ER_REWRITER_OOM
  eng "Out of memory."

ER_REWRITER_TABLE_MALFORMED_ERROR
  eng "Wrong column count or names when loading rules."

ER_REWRITER_LOAD_FAILED
  eng "Some rules failed to load."

ER_REWRITER_READ_FAILED
  eng "Got error from storage engine while refreshing rewrite rules."

ER_CONN_CONTROL_EVENT_COORDINATOR_INIT_FAILED
  eng "Failed to initialize Connection_event_coordinator"

ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_UPDATE_FAILED
  eng "Failed to update connection delay triggered stats"

ER_CONN_CONTROL_STAT_CONN_DELAY_TRIGGERED_RESET_FAILED
  eng "Failed to reset connection delay triggered stats"

ER_CONN_CONTROL_INVALID_CONN_DELAY_TYPE
  eng "Unexpected option type for connection delay."

ER_CONN_CONTROL_DELAY_ACTION_INIT_FAILED
  eng "Failed to initialize Connection_delay_action"

ER_CONN_CONTROL_FAILED_TO_SET_CONN_DELAY
  eng "Could not set %s delay for connection delay."

ER_CONN_CONTROL_FAILED_TO_UPDATE_CONN_DELAY_HASH
  eng "Failed to update connection delay hash for account : %s"

ER_XPLUGIN_FORCE_STOP_CLIENT
  eng "%s: Force stopping client because exception occurred: %s"

ER_XPLUGIN_MAX_AUTH_ATTEMPTS_REACHED
  eng "%s.%u: Maximum number of authentication attempts reached, login failed."

ER_XPLUGIN_BUFFER_PAGE_ALLOC_FAILED
  eng "Error allocating Buffer_page: %s"

ER_XPLUGIN_DETECTED_HANGING_CLIENTS
  eng "Detected %u hanging client(s)"

ER_XPLUGIN_FAILED_TO_ACCEPT_CLIENT
  eng "Error accepting client"

ER_XPLUGIN_FAILED_TO_SCHEDULE_CLIENT
  eng "Internal error scheduling client for execution"

ER_XPLUGIN_FAILED_TO_PREPARE_IO_INTERFACES
  eng "Preparation of I/O interfaces failed, X Protocol won't be accessible"

ER_XPLUGIN_SRV_SESSION_INIT_THREAD_FAILED
  eng "srv_session_init_thread returned error"

ER_XPLUGIN_UNABLE_TO_USE_USER_SESSION_ACCOUNT
  eng "Unable to use user mysql.session account when connecting the server for internal plugin requests."

ER_XPLUGIN_REFERENCE_TO_USER_ACCOUNT_DOC_SECTION
  eng "For more information, please see the X Plugin User Account section in the MySQL documentation"

ER_XPLUGIN_UNEXPECTED_EXCEPTION_DISPATCHING_CMD
  eng "%s: Unexpected exception dispatching command: %s"

ER_XPLUGIN_EXCEPTION_IN_TASK_SCHEDULER
  eng "Exception in post: %s"

ER_XPLUGIN_TASK_SCHEDULING_FAILED
  eng "Internal error scheduling task"

ER_XPLUGIN_EXCEPTION_IN_EVENT_LOOP
  eng "Exception in event loop: \"%s\": %s"

ER_XPLUGIN_LISTENER_SETUP_FAILED
  eng "Setup of %s failed, %s"

ER_XPLUING_NET_STARTUP_FAILED
  eng "%s"

ER_XPLUGIN_FAILED_AT_SSL_CONF
  eng "Failed at SSL configuration: \"%s\""

OBSOLETE_ER_XPLUGIN_CLIENT_SSL_HANDSHAKE_FAILED
  eng "Error during SSL handshake for client connection (%i)"

OBSOLETE_ER_XPLUGIN_SSL_HANDSHAKE_WITH_SERVER_FAILED
  eng "%s: Error during SSL handshake"

ER_XPLUGIN_FAILED_TO_CREATE_SESSION_FOR_CONN
  eng "%s: Error creating session for connection from %s"

ER_XPLUGIN_FAILED_TO_INITIALIZE_SESSION
  eng "%s: Error initializing session for connection: %s"

ER_XPLUGIN_MESSAGE_TOO_LONG
  eng "%s: Message of size %u received, exceeding the limit of %i"

ER_XPLUGIN_UNINITIALIZED_MESSAGE
  eng "Message is not properly initialized: %s"

ER_XPLUGIN_FAILED_TO_SET_MIN_NUMBER_OF_WORKERS
  eng "Unable to set minimal number of workers to %u; actual value is %i"

ER_XPLUGIN_UNABLE_TO_ACCEPT_CONNECTION
  eng "Unable to accept connection, disconnecting client"

ER_XPLUGIN_ALL_IO_INTERFACES_DISABLED
  eng "All I/O interfaces are disabled, X Protocol won't be accessible"

OBSOLETE_ER_XPLUGIN_INVALID_MSG_DURING_CLIENT_INIT
  eng "%s: Invalid message %i received during client initialization"

OBSOLETE_ER_XPLUGIN_CLOSING_CLIENTS_ON_SHUTDOWN
  eng "%s: closing client because of shutdown (state: %i)"

ER_XPLUGIN_ERROR_READING_SOCKET
  eng "%s: Error reading from socket %s (%i)"

ER_XPLUGIN_PEER_DISCONNECTED_WHILE_READING_MSG_BODY
  eng "%s: peer disconnected while reading message body"

ER_XPLUGIN_READ_FAILED_CLOSING_CONNECTION
  eng "client_id:%s - %s while reading from socket, closing connection"

OBSOLETE_ER_XPLUGIN_INVALID_AUTH_METHOD
  eng "%s.%u: Invalid authentication method %s"

OBSOLETE_ER_XPLUGIN_UNEXPECTED_MSG_DURING_AUTHENTICATION
  eng "%s: Unexpected message of type %i received during authentication"

OBSOLETE_ER_XPLUGIN_ERROR_WRITING_TO_CLIENT
  eng "Error writing to client: %s (%i)"

OBSOLETE_ER_XPLUGIN_SCHEDULER_STARTED
  eng "Scheduler \"%s\" started."

OBSOLETE_ER_XPLUGIN_SCHEDULER_STOPPED
  eng "Scheduler \"%s\" stopped."

ER_XPLUGIN_LISTENER_SYS_VARIABLE_ERROR
  eng "Please see the MySQL documentation for '%s' system variables to fix the error"

ER_XPLUGIN_LISTENER_STATUS_MSG
  eng "X Plugin ready for connections. %s"

ER_XPLUGIN_RETRYING_BIND_ON_PORT
  eng "Retrying `bind()` on TCP/IP port %i"

OBSOLETE_ER_XPLUGIN_SHUTDOWN_TRIGGERED
  eng "Shutdown triggered by mysqld abort flag"

OBSOLETE_ER_XPLUGIN_USER_ACCOUNT_WITH_ALL_PERMISSIONS
  eng "Using %s account for authentication which has all required permissions"

ER_XPLUGIN_EXISTING_USER_ACCOUNT_WITH_INCOMPLETE_GRANTS
  eng "Using existing %s account for authentication. Incomplete grants will be fixed"

OBSOLETE_ER_XPLUGIN_SERVER_STARTS_HANDLING_CONNECTIONS
  eng "Server starts handling incoming connections"

OBSOLETE_ER_XPLUGIN_SERVER_STOPPED_HANDLING_CONNECTIONS
  eng "Stopped handling incoming connections"

OBSOLETE_ER_XPLUGIN_FAILED_TO_INTERRUPT_SESSION
  eng "%s: Could not interrupt client session"

OBSOLETE_ER_XPLUGIN_CLIENT_RELEASE_TRIGGERED
  eng "%s: release triggered by timeout in state:%i"

ER_XPLUGIN_IPv6_AVAILABLE
  eng "IPv6 is available"

OBSOLETE_ER_XPLUGIN_UNIX_SOCKET_NOT_CONFIGURED
  eng "UNIX socket not configured"

ER_XPLUGIN_CLIENT_KILL_MSG
  eng "Kill client: %i %s"

ER_XPLUGIN_FAILED_TO_GET_SECURITY_CTX
  eng "Could not get security context for session"

OBSOLETE_ER_XPLUGIN_FAILED_TO_SWITCH_SECURITY_CTX_TO_ROOT
  eng "Unable to switch security context to root"

ER_XPLUGIN_FAILED_TO_CLOSE_SQL_SESSION
  eng "Error closing SQL session"

ER_XPLUGIN_FAILED_TO_EXECUTE_ADMIN_CMD
  eng "Error executing admin command %s: %s"

ER_XPLUGIN_EMPTY_ADMIN_CMD
  eng "Error executing empty admin command"

ER_XPLUGIN_FAILED_TO_GET_SYS_VAR
  eng "Unable to retrieve system variable \'%s\'"

ER_XPLUGIN_FAILED_TO_GET_CREATION_STMT
  eng "Unable to get creation stmt for collection \'%s\'; query result size: %lu"

ER_XPLUGIN_FAILED_TO_GET_ENGINE_INFO
  eng "Unable to get engine info for collection \'%s\'; creation stmt: %s"

OBSOLETE_ER_XPLUGIN_FAIL_TO_GET_RESULT_DATA
  eng "Error getting result data: %s"

OBSOLETE_ER_XPLUGIN_CAPABILITY_EXPIRED_PASSWORD
  eng "Capability expired password failed with error: %s"

ER_XPLUGIN_FAILED_TO_SET_SO_REUSEADDR_FLAG
  eng "Failed to set SO_REUSEADDR flag (error: %d)."

ER_XPLUGIN_FAILED_TO_OPEN_INTERNAL_SESSION
  eng "Could not open internal MySQL session"

ER_XPLUGIN_FAILED_TO_SWITCH_CONTEXT
  eng "Unable to switch context to user %s"

ER_XPLUGIN_FAILED_TO_UNREGISTER_UDF
  eng "Can\'t unregister \'%s\' user defined function"

OBSOLETE_ER_XPLUGIN_GET_PEER_ADDRESS_FAILED
  eng "%s: get peer address failed, can't resolve IP to hostname"

OBSOLETE_ER_XPLUGIN_CAPABILITY_CLIENT_INTERACTIVE_FAILED
  eng "Capability client interactive failed with error: %s"

ER_XPLUGIN_FAILED_TO_RESET_IPV6_V6ONLY_FLAG
  eng "Failed to reset IPV6_V6ONLY flag (error: %d). The server will listen to IPv6 addresses only."

ER_KEYRING_INVALID_KEY_TYPE
  eng "Invalid key type"

ER_KEYRING_INVALID_KEY_LENGTH
  eng "Invalid key length for given block cipher"

ER_KEYRING_FAILED_TO_CREATE_KEYRING_DIR
  eng "Could not create keyring directory. The keyring_file will stay unusable until correct path to the keyring directory gets provided"

ER_KEYRING_FILE_INIT_FAILED
  eng "keyring_file initialization failure. Please check if the keyring_file_data points to readable keyring file or keyring file can be created in the specified location. The keyring_file will stay unusable until correct path to the keyring file gets provided"

ER_KEYRING_INTERNAL_EXCEPTION_FAILED_FILE_INIT
  eng "keyring_file initialization failure due to internal exception inside the plugin."

ER_KEYRING_FAILED_TO_GENERATE_KEY
  eng "Failed to generate a key due to internal exception inside keyring_file plugin"

ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_INVALID_KEY
  eng "Error while %s key: invalid key_type"

ER_KEYRING_CHECK_KEY_FAILED_DUE_TO_EMPTY_KEY_ID
  eng "Error while %s key: key_id cannot be empty"

ER_KEYRING_OPERATION_FAILED_DUE_TO_INTERNAL_ERROR
  eng "Failed to %s due to internal exception inside %s plugin"

ER_KEYRING_INCORRECT_FILE
  eng "Incorrect Keyring file"

ER_KEYRING_FOUND_MALFORMED_BACKUP_FILE
  eng "Found malformed keyring backup file - removing it"

ER_KEYRING_FAILED_TO_RESTORE_FROM_BACKUP_FILE
  eng "Error while restoring keyring from backup file cannot overwrite keyring with backup"

ER_KEYRING_FAILED_TO_FLUSH_KEYRING_TO_FILE
  eng "Error while flushing in-memory keyring into keyring file"

ER_KEYRING_FAILED_TO_GET_FILE_STAT
  eng "Error while reading stat for %s.Please check if file %s was not removed. OS returned this error: %s"

ER_KEYRING_FAILED_TO_REMOVE_FILE
  eng "Could not remove file %s OS retuned this error: %s"

ER_KEYRING_FAILED_TO_TRUNCATE_FILE
  eng "Could not truncate file %s. OS retuned this error: %s"

ER_KEYRING_UNKNOWN_ERROR
  eng "Unknown error %d"

ER_KEYRING_FAILED_TO_SET_KEYRING_FILE_DATA
  eng "keyring_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path"

ER_KEYRING_FILE_IO_ERROR
  eng "%s"

ER_KEYRING_FAILED_TO_LOAD_KEYRING_CONTENT
  eng "Error while loading keyring content. The keyring might be malformed"

ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING
  eng "Could not flush keys to keyring"

ER_KEYRING_FAILED_TO_FLUSH_KEYS_TO_KEYRING_BACKUP
  eng "Could not flush keys to keyring's backup"

ER_KEYRING_KEY_FETCH_FAILED_DUE_TO_EMPTY_KEY_ID
  eng "Error while fetching key: key_id cannot be empty"

ER_KEYRING_FAILED_TO_REMOVE_KEY_DUE_TO_EMPTY_ID
  eng "Error while removing key: key_id cannot be empty"

ER_KEYRING_OKV_INCORRECT_KEY_VAULT_CONFIGURED
  eng "For keyring_okv to be initialized, please point keyring_okv_conf_dir variable to a directory with Oracle Key Vault configuration file and ssl materials"

ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INCORRECT_CONF
  eng "keyring_okv initialization failure. Please check that the keyring_okv_conf_dir points to a readable directory and that the directory contains Oracle Key Vault configuration file and ssl materials. Please also check that Oracle Key Vault is up and running."

ER_KEYRING_OKV_INIT_FAILED_DUE_TO_INTERNAL_ERROR
  eng "keyring_okv initialization failure due to internal exception inside the plugin"

ER_KEYRING_OKV_INVALID_KEY_TYPE
  eng "Invalid key type"

ER_KEYRING_OKV_INVALID_KEY_LENGTH_FOR_CIPHER
  eng "Invalid key length for given block cipher"

ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR
  eng "Failed to generate a key due to internal exception inside keyring_okv plugin"

ER_KEYRING_OKV_FAILED_TO_FIND_SERVER_ENTRY
  eng "Could not find entry for server in configuration file %s"

ER_KEYRING_OKV_FAILED_TO_FIND_STANDBY_SERVER_ENTRY
  eng "Could not find entry for standby server in configuration file %s"

ER_KEYRING_OKV_FAILED_TO_PARSE_CONF_FILE
  eng "Could not parse the %s file provided"

ER_KEYRING_OKV_FAILED_TO_LOAD_KEY_UID
  eng "Could not load keys' uids from the OKV server"

ER_KEYRING_OKV_FAILED_TO_INIT_SSL_LAYER
  eng "Could not initialize ssl layer"

ER_KEYRING_OKV_FAILED_TO_INIT_CLIENT
  eng "Could not initialize OKV client"

ER_KEYRING_OKV_CONNECTION_TO_SERVER_FAILED
  eng "Could not connect to the OKV server"

ER_KEYRING_OKV_FAILED_TO_REMOVE_KEY
  eng "Could not remove the key"

ER_KEYRING_OKV_FAILED_TO_ADD_ATTRIBUTE
  eng "Could not add attribute, attribute_name=%s attribute value=%s"

ER_KEYRING_OKV_FAILED_TO_GENERATE_KEY
  eng "Could not generate the key."

ER_KEYRING_OKV_FAILED_TO_STORE_KEY
  eng "Could not store the key."

ER_KEYRING_OKV_FAILED_TO_ACTIVATE_KEYS
  eng "Could not activate the key."

ER_KEYRING_OKV_FAILED_TO_FETCH_KEY
  eng "Could not fetch generated key"

ER_KEYRING_OKV_FAILED_TO_STORE_OR_GENERATE_KEY
  eng "Could not store/generate the key - failed to set key attribute x-key-ready"

ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY_SIGNATURE
  eng "Could not retrieve key signature from custom attributes"

ER_KEYRING_OKV_FAILED_TO_RETRIEVE_KEY
  eng "Could not retrieve key from OKV"

ER_KEYRING_OKV_FAILED_TO_LOAD_SSL_TRUST_STORE
  eng "Error loading trust store"

ER_KEYRING_OKV_FAILED_TO_SET_CERTIFICATE_FILE
  eng "Error setting the certificate file."

ER_KEYRING_OKV_FAILED_TO_SET_KEY_FILE
  eng "Error setting the key file."

ER_KEYRING_OKV_KEY_MISMATCH
  eng "Private key does not match the certificate public key"

ER_KEYRING_ENCRYPTED_FILE_INCORRECT_KEYRING_FILE
  eng "Incorrect Keyring file"

ER_KEYRING_ENCRYPTED_FILE_DECRYPTION_FAILED
  eng "Keyring_encrypted_file decryption failed. Please verify --keyring-encrypted-file-password option value."

ER_KEYRING_ENCRYPTED_FILE_FOUND_MALFORMED_BACKUP_FILE
  eng "Found malformed keyring backup file - removing it"

ER_KEYRING_ENCRYPTED_FILE_FAILED_TO_RESTORE_KEYRING
  eng "Error while restoring keyring from backup file cannot overwrite keyring with backup"

ER_KEYRING_ENCRYPTED_FILE_FAILED_TO_FLUSH_KEYRING
  eng "Error while flushing in-memory keyring into keyring file"

ER_KEYRING_ENCRYPTED_FILE_ENCRYPTION_FAILED
  eng "Keyring_encrypted_file encryption failed. Please verify --keyring-encrypted-file-password option value."

ER_KEYRING_ENCRYPTED_FILE_INVALID_KEYRING_DIR
  eng "keyring_encrypted_file_data cannot be set to new value as the keyring file cannot be created/accessed in the provided path"

ER_KEYRING_ENCRYPTED_FILE_FAILED_TO_CREATE_KEYRING_DIR
  eng "Could not create keyring directory The keyring_encrypted_file will stay unusable until correct path to the keyring directory gets provided"

ER_KEYRING_ENCRYPTED_FILE_PASSWORD_IS_INVALID
  eng "The keyring_encrypted_file_password must be set to a valid value."

ER_KEYRING_ENCRYPTED_FILE_PASSWORD_IS_TOO_LONG
  eng "Too long keyring_encrypted_file_password value."

ER_KEYRING_ENCRYPTED_FILE_INIT_FAILURE
  eng "keyring_encrypted_file initialization failure. Please check if the keyring_encrypted_file_data points to readable keyring file or keyring file can be created in the specified location or password to decrypt keyring file is correct."

ER_KEYRING_ENCRYPTED_FILE_INIT_FAILED_DUE_TO_INTERNAL_ERROR
  eng "keyring_encrypted_file initialization failure due to internal exception inside the plugin"

ER_KEYRING_ENCRYPTED_FILE_GEN_KEY_FAILED_DUE_TO_INTERNAL_ERROR
  eng "Failed to generate a key due to internal exception inside keyring_encrypted_file plugin"

ER_KEYRING_AWS_FAILED_TO_SET_CMK_ID
  eng "keyring_aws_cmk_id cannot be set to the new value as AWS KMS seems to not understand the id provided. Please check that CMK id provided is correct."

ER_KEYRING_AWS_FAILED_TO_SET_REGION
  eng "keyring_aws_region cannot be set to the new value as AWS KMS seems to not understand the region provided. Please check that region provided is correct."

ER_KEYRING_AWS_FAILED_TO_OPEN_CONF_FILE
  eng "Could not open keyring_aws configuration file: %s. OS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_ID_FROM_CONF_FILE
  eng "Could not read AWS access key id from keyring_aws configuration file: %s. OS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_ACCESS_KEY_FROM_CONF_FILE
  eng "Could not read AWS access key from keyring_aws configuration file: %s. OS returned this error: %s"

ER_KEYRING_AWS_INVALID_CONF_FILE_PATH
  eng "Path to keyring aws configuration file cannot be empty"

ER_KEYRING_AWS_INVALID_DATA_FILE_PATH
  eng "Path to keyring_aws storage file cannot be empty."

ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DIR
  eng "Unable to create/access keyring directory."

ER_KEYRING_AWS_FAILED_TO_ACCESS_OR_CREATE_KEYRING_DATA_FILE
  eng "Unable to create/access keyring_aws storage file. Please check if keyring_aws_data_file points to location where keyring file can be created/accessed. Please also make sure that MySQL server's user has high enough privileges to access this location."

ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_INTERNAL_ERROR
  eng "keyring_aws initialization failed due to internal error when initializing synchronization primitive - %s. OS returned this error: %s:"

ER_KEYRING_AWS_FAILED_TO_ACCESS_DATA_FILE
  eng "Could not access keyring_aws storage file in the path provided. Please check if the keyring_aws directory can be accessed by MySQL Server"

ER_KEYRING_AWS_CMK_ID_NOT_SET
  eng "keyring_aws_cmk_id has to be set"

ER_KEYRING_AWS_FAILED_TO_GET_KMS_CREDENTIAL_FROM_CONF_FILE
  eng "Could not get AWS KMS credentials from the configuration file"

ER_KEYRING_AWS_INIT_FAILURE
  eng "keyring_aws initialization failure."

ER_KEYRING_AWS_FAILED_TO_INIT_DUE_TO_PLUGIN_INTERNAL_ERROR
  eng "keyring_aws initialization failure due to internal exception inside the plugin"

ER_KEYRING_AWS_INVALID_KEY_LENGTH_FOR_CIPHER
  eng "Invalid key length for given block cipher"

ER_KEYRING_AWS_FAILED_TO_GENERATE_KEY_DUE_TO_INTERNAL_ERROR
  eng "Failed to generate a key due to internal exception inside keyring_file plugin"

ER_KEYRING_AWS_INCORRECT_FILE
  eng "Incorrect Keyring file"

ER_KEYRING_AWS_FOUND_MALFORMED_BACKUP_FILE
  eng "Found malformed keyring backup file - removing it"

ER_KEYRING_AWS_FAILED_TO_RESTORE_FROM_BACKUP_FILE
  eng "Error while restoring keyring from backup file cannot overwrite keyring with backup"

ER_KEYRING_AWS_FAILED_TO_FLUSH_KEYRING_TO_FILE
  eng "Error while flushing in-memory keyring into keyring file"

ER_KEYRING_AWS_INCORRECT_REGION
  eng "Wrong region"

ER_KEYRING_AWS_FAILED_TO_CONNECT_KMS
  eng "Could not connect to AWS KMS with the credentials provided. Please make sure they are correct. AWS KMS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_GENERATE_NEW_KEY
  eng "Could not generate a new key. AWS KMS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_ENCRYPT_KEY
  eng "Could not encrypt key. AWS KMS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_RE_ENCRYPT_KEY
  eng "Could not re-encrypt key. AWS KMS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_DECRYPT_KEY
  eng "Could not decrypt key. AWS KMS returned this error: %s"

ER_KEYRING_AWS_FAILED_TO_ROTATE_CMK
  eng "Could not rotate the CMK. AWS KMS returned this error: %s"

ER_GRP_RPL_GTID_ALREADY_USED
  eng "The requested GTID '%s:%lld' was already used, the transaction will rollback."

ER_GRP_RPL_APPLIER_THD_KILLED
  eng "The group replication applier thread was killed."

ER_GRP_RPL_EVENT_HANDLING_ERROR
  eng "Error at event handling! Got error: %d."

ER_GRP_RPL_ERROR_GTID_EXECUTION_INFO
  eng "Error when extracting group GTID execution information, some recovery operations may face future issues."

ER_GRP_RPL_CERTIFICATE_SIZE_ERROR
  eng "An error occurred when trying to reduce the Certification information size for transmission."

ER_GRP_RPL_CREATE_APPLIER_CACHE_ERROR
  eng "Failed to create group replication pipeline applier cache!"

ER_GRP_RPL_UNBLOCK_WAITING_THD
  eng "Unblocking the group replication thread waiting for applier to start, as the start group replication was killed."

ER_GRP_RPL_APPLIER_PIPELINE_NOT_DISPOSED
  eng "The group replication applier pipeline was not properly disposed. Check the error log for further info."

ER_GRP_RPL_APPLIER_THD_EXECUTION_ABORTED
  eng "The applier thread execution was aborted. Unable to process more transactions, this member will now leave the group."

ER_GRP_RPL_APPLIER_EXECUTION_FATAL_ERROR
  eng "Fatal error during execution on the Applier process of Group Replication. The server will now leave the group."

ER_GRP_RPL_ERROR_STOPPING_CHANNELS
  eng "Error stopping all replication channels while server was leaving the group. %s"

ER_GRP_RPL_ERROR_SENDING_SINGLE_PRIMARY_MSSG
  eng "Error sending single primary message informing that primary did apply relay logs."

ER_GRP_RPL_UPDATE_TRANS_SNAPSHOT_VER_ERROR
  eng "Error updating transaction snapshot version after transaction being positively certified."

ER_GRP_RPL_SIDNO_FETCH_ERROR
  eng "Error fetching transaction sidno after transaction being positively certified."

ER_GRP_RPL_BROADCAST_COMMIT_TRANS_MSSG_FAILED
  eng "Broadcast of committed transactions message failed."

ER_GRP_RPL_GROUP_NAME_PARSE_ERROR
  eng "Unable to parse the group_replication_group_name during the Certification module initialization."

ER_GRP_RPL_ADD_GRPSID_TO_GRPGTIDSID_MAP_ERROR
  eng "Unable to add the group_sid in the group_gtid_sid_map during the Certification module initialization."

ER_GRP_RPL_UPDATE_GRPGTID_EXECUTED_ERROR
  eng "Error updating group_gtid_executed GITD set during the Certification module initialization."

ER_GRP_RPL_DONOR_TRANS_INFO_ERROR
  eng "Unable to handle the donor's transaction information when initializing the conflict detection component. Possible out of memory error."

ER_GRP_RPL_SERVER_CONN_ERROR
  eng "Error when establishing a server connection during the Certification module initialization."

ER_GRP_RPL_ERROR_FETCHING_GTID_EXECUTED_SET
  eng "Error when extracting this member GTID executed set. Certification module can't be properly initialized."

ER_GRP_RPL_ADD_GTID_TO_GRPGTID_EXECUTED_ERROR
  eng "Error while adding the server GTID EXECUTED set to the group_gtid_execute during the Certification module initialization."

ER_GRP_RPL_ERROR_FETCHING_GTID_SET
  eng "Error when extracting this member retrieved set for its applier. Certification module can't be properly initialized."

ER_GRP_RPL_ADD_RETRIEVED_SET_TO_GRP_GTID_EXECUTED_ERROR
  eng "Error while adding the member retrieved set to the group_gtid_executed during the Certification module initialization."

ER_GRP_RPL_CERTIFICATION_INITIALIZATION_FAILURE
  eng "Error during Certification module initialization."

ER_GRP_RPL_UPDATE_LAST_CONFLICT_FREE_TRANS_ERROR
  eng "Unable to update last conflict free transaction, this transaction will not be tracked on performance_schema.replication_group_member_stats.last_conflict_free_transaction."

ER_GRP_RPL_UPDATE_TRANS_SNAPSHOT_REF_VER_ERROR
  eng "Error updating transaction snapshot version reference for internal storage."

ER_GRP_RPL_FETCH_TRANS_SIDNO_ERROR
  eng "Error fetching transaction sidno while adding to the group_gtid_executed set."

ER_GRP_RPL_ERROR_VERIFYING_SIDNO
  eng "Error while ensuring the sidno be present in the group_gtid_executed."

ER_GRP_RPL_CANT_GENERATE_GTID
  eng "Impossible to generate Global Transaction Identifier: the integer component reached the maximal value. Restart the group with a new group_replication_group_name."

ER_GRP_RPL_INVALID_GTID_SET
  eng "Invalid stable transactions set."

ER_GRP_RPL_UPDATE_GTID_SET_ERROR
  eng "Error updating stable transactions set."

ER_GRP_RPL_RECEIVED_SET_MISSING_GTIDS
  eng "There was an error when filling the missing GTIDs on the applier channel received set. Despite not critical, on the long run this may cause performance issues."

OBSOLETE_ER_GRP_RPL_SKIP_COMPUTATION_TRANS_COMMITTED
  eng "Skipping the computation of the Transactions_committed_all_members field as an older instance of this computation is still ongoing."

ER_GRP_RPL_NULL_PACKET
  eng "Null packet on certifier's queue."

ER_GRP_RPL_CANT_READ_GTID
  eng "Error reading GTIDs from the message."

ER_GRP_RPL_PROCESS_GTID_SET_ERROR
  eng "Error processing stable transactions set."

ER_GRP_RPL_PROCESS_INTERSECTION_GTID_SET_ERROR
  eng "Error processing intersection of stable transactions set."

ER_GRP_RPL_SET_STABLE_TRANS_ERROR
  eng "Error setting stable transactions set."

ER_GRP_RPL_CANT_READ_GRP_GTID_EXTRACTED
  eng "Error reading group_gtid_extracted from the View_change_log_event."

ER_GRP_RPL_CANT_READ_WRITE_SET_ITEM
  eng "Error reading the write set item '%s' from the View_change_log_event."

ER_GRP_RPL_INIT_CERTIFICATION_INFO_FAILURE
  eng "Error during certification_info initialization."

ER_GRP_RPL_CONFLICT_DETECTION_DISABLED
  eng "Primary had applied all relay logs, disabled conflict detection."

ER_GRP_RPL_MSG_DISCARDED
  eng "Message received while the plugin is not ready, message discarded."

ER_GRP_RPL_MISSING_GRP_RPL_APPLIER
  eng "Message received without a proper group replication applier."

ER_GRP_RPL_CERTIFIER_MSSG_PROCESS_ERROR
  eng "Error processing message in Certifier."

ER_GRP_RPL_SRV_NOT_ONLINE
  eng "This server was not declared online since it is on status %s."

ER_GRP_RPL_SRV_ONLINE
  eng "This server was declared online within the replication group."

ER_GRP_RPL_DISABLE_SRV_READ_MODE_RESTRICTED
  eng "When declaring the plugin online it was not possible to disable the server read mode settings. Try to disable it manually."

ER_GRP_RPL_MEM_ONLINE
  eng "The member with address %s:%u was declared online within the replication group."

ER_GRP_RPL_MEM_UNREACHABLE
  eng "Member with address %s:%u has become unreachable."

ER_GRP_RPL_MEM_REACHABLE
  eng "Member with address %s:%u is reachable again."

ER_GRP_RPL_SRV_BLOCKED
  eng "This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked until contact with the majority is restored. It is possible to use group_replication_force_members to force a new group membership."

ER_GRP_RPL_SRV_BLOCKED_FOR_SECS
  eng "This server is not able to reach a majority of members in the group. This server will now block all updates. The server will remain blocked for the next %lu seconds. Unless contact with the majority is restored, after this time the member will error out and leave the group. It is possible to use group_replication_force_members to force a new group membership."

ER_GRP_RPL_CHANGE_GRP_MEM_NOT_PROCESSED
  eng "A group membership change was received but the plugin is already leaving due to the configured timeout on group_replication_unreachable_majority_timeout option."

ER_GRP_RPL_MEMBER_CONTACT_RESTORED
  eng "The member has resumed contact with a majority of the members in the group. Regular operation is restored and transactions are unblocked."

ER_GRP_RPL_MEMBER_REMOVED
  eng "Members removed from the group: %s"

ER_GRP_RPL_PRIMARY_MEMBER_LEFT_GRP
  eng "Primary server with address %s left the group. Electing new Primary."

ER_GRP_RPL_MEMBER_ADDED
  eng "Members joined the group: %s"

ER_GRP_RPL_MEMBER_EXIT_PLUGIN_ERROR
  eng "There was a previous plugin error while the member joined the group. The member will now exit the group."

ER_GRP_RPL_MEMBER_CHANGE
  eng "Group membership changed to %s on view %s."

ER_GRP_RPL_MEMBER_LEFT_GRP
  eng "Group membership changed: This member has left the group."

ER_GRP_RPL_MEMBER_EXPELLED
  eng "Member was expelled from the group due to network failures, changing member status to ERROR."

ER_GRP_RPL_SESSION_OPEN_FAILED
  eng "Unable to open session to (re)set read only mode. Skipping."

ER_GRP_RPL_NEW_PRIMARY_ELECTED
  eng "A new primary with address %s:%u was elected. %s"

ER_GRP_RPL_DISABLE_READ_ONLY_FAILED
  eng "Unable to disable super read only flag. Try to disable it manually"

ER_GRP_RPL_ENABLE_READ_ONLY_FAILED
  eng "Unable to set super read only flag. Try to set it manually."

ER_GRP_RPL_SRV_PRIMARY_MEM
  eng "This server is working as primary member."

ER_GRP_RPL_SRV_SECONDARY_MEM
  eng "This server is working as secondary member with primary member address %s:%u."

ER_GRP_RPL_NO_SUITABLE_PRIMARY_MEM
  eng "Unable to set any member as primary. No suitable candidate."

ER_GRP_RPL_SUPER_READ_ONLY_ACTIVATE_ERROR
  eng "Error when activating super_read_only mode on start. The member will now exit the group."

ER_GRP_RPL_EXCEEDS_AUTO_INC_VALUE
  eng "Group contains %lu members which is greater than group_replication_auto_increment_increment value of %lu. This can lead to a higher transactional abort rate."

ER_GRP_RPL_DATA_NOT_PROVIDED_BY_MEM
  eng "Member with address '%s:%u' didn't provide any data during the last group change. Group information can be outdated and lead to errors on recovery."

ER_GRP_RPL_MEMBER_ALREADY_EXISTS
  eng "There is already a member with server_uuid %s. The member will now exit the group."

OBSOLETE_ER_GRP_RPL_GRP_CHANGE_INFO_EXTRACT_ERROR
  eng "Error when extracting information for group change. Operations and checks made to group joiners may be incomplete."

ER_GRP_RPL_GTID_EXECUTED_EXTRACT_ERROR
  eng "Error when extracting this member GTID executed set. Operations and checks made to group joiners may be incomplete."

ER_GRP_RPL_GTID_SET_EXTRACT_ERROR
  eng "Error when extracting this member retrieved set for its applier. Operations and checks made to group joiners may be incomplete."

ER_GRP_RPL_START_FAILED
  eng "The START GROUP_REPLICATION command failed since the group already has 9 members."

ER_GRP_RPL_MEMBER_VER_INCOMPATIBLE
  eng "Member version is incompatible with the group."

ER_GRP_RPL_TRANS_NOT_PRESENT_IN_GRP
  eng "The member contains transactions not present in the group. The member will now exit the group."

ER_GRP_RPL_TRANS_GREATER_THAN_GRP
  eng "It was not possible to assess if the member has more transactions than the group. The member will now exit the group."

ER_GRP_RPL_MEMBER_VERSION_LOWER_THAN_GRP
  eng "Member version is lower than some group member, but since option 'group_replication_allow_local_lower_version_join is enabled, member will be allowed to join."

ER_GRP_RPL_LOCAL_GTID_SETS_PROCESS_ERROR
  eng "Error processing local GTID sets when comparing this member transactions against the group."

ER_GRP_RPL_MEMBER_TRANS_GREATER_THAN_GRP
  eng "This member has more executed transactions than those present in the group. Local transactions: %s > Group transactions: %s"

ER_GRP_RPL_BLOCK_SIZE_DIFF_FROM_GRP
  eng "The member is configured with a group_replication_gtid_assignment_block_size option value '%llu' different from the group '%llu'. The member will now exit the group."

ER_GRP_RPL_TRANS_WRITE_SET_EXTRACT_DIFF_FROM_GRP
  eng "The member is configured with a transaction-write-set-extraction option value '%s' different from the group '%s'. The member will now exit the group."

ER_GRP_RPL_MEMBER_CFG_INCOMPATIBLE_WITH_GRP_CFG
  eng "The member configuration is not compatible with the group configuration. Variables such as group_replication_single_primary_mode or group_replication_enforce_update_everywhere_checks must have the same value on every server in the group. (member configuration option: [%s], group configuration option: [%s])."

ER_GRP_RPL_MEMBER_STOP_RPL_CHANNELS_ERROR
  eng "Error stopping all replication channels while server was leaving the group. %s"

ER_GRP_RPL_PURGE_APPLIER_LOGS
  eng "Detected previous RESET SOURCE invocation or an issue exists in the group replication applier relay log. Purging existing applier logs."

ER_GRP_RPL_RESET_APPLIER_MODULE_LOGS_ERROR
  eng "Unknown error occurred while resetting applier's module logs."

ER_GRP_RPL_APPLIER_THD_SETUP_ERROR
  eng "Failed to setup the group replication applier thread."

ER_GRP_RPL_APPLIER_THD_START_ERROR
  eng "Error while starting the group replication applier thread"

ER_GRP_RPL_APPLIER_THD_STOP_ERROR
  eng "Failed to stop the group replication applier thread."

ER_GRP_RPL_FETCH_TRANS_DATA_FAILED
  eng "Failed to fetch transaction data containing required transaction info for applier"

ER_GRP_RPL_REPLICA_IO_THD_PRIMARY_UNKNOWN
  eng "Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known."

ER_GRP_RPL_SALVE_IO_THD_ON_SECONDARY_MEMBER
  eng "Can't start replica IO THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member."

ER_GRP_RPL_REPLICA_SQL_THD_PRIMARY_UNKNOWN
  eng "Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode and the primary member is not known."

ER_GRP_RPL_REPLICA_SQL_THD_ON_SECONDARY_MEMBER
  eng "Can't start replica SQL THREAD of channel '%s' when group replication is running with single-primary mode on a secondary member."

ER_GRP_RPL_NEEDS_INNODB_TABLE
  eng "Table %s does not use the InnoDB storage engine. This is not compatible with Group Replication."

ER_GRP_RPL_PRIMARY_KEY_NOT_DEFINED
  eng "Table %s does not have any PRIMARY KEY. This is not compatible with Group Replication."

ER_GRP_RPL_FK_WITH_CASCADE_UNSUPPORTED
  eng "Table %s has a foreign key with 'CASCADE', 'SET NULL' or 'SET DEFAULT' clause. This is not compatible with Group Replication."

ER_GRP_RPL_AUTO_INC_RESET
  eng "group_replication_auto_increment_increment is reset to %lu"

ER_GRP_RPL_AUTO_INC_OFFSET_RESET
  eng "auto_increment_offset is reset to %lu"

ER_GRP_RPL_AUTO_INC_SET
  eng "group_replication_auto_increment_increment is set to %lu"

ER_GRP_RPL_AUTO_INC_OFFSET_SET
  eng "auto_increment_offset is set to %lu"

ER_GRP_RPL_FETCH_TRANS_CONTEXT_FAILED
  eng "Failed to fetch transaction context containing required transaction info for certification"

ER_GRP_RPL_FETCH_FORMAT_DESC_LOG_EVENT_FAILED
  eng "Failed to fetch Format_description_log_event containing required server info for applier"

ER_GRP_RPL_FETCH_TRANS_CONTEXT_LOG_EVENT_FAILED
  eng "Failed to fetch Transaction_context_log_event containing required transaction info for certification"

ER_GRP_RPL_FETCH_SNAPSHOT_VERSION_FAILED
  eng "Failed to read snapshot version from transaction context event required for certification"

ER_GRP_RPL_FETCH_GTID_LOG_EVENT_FAILED
  eng "Failed to fetch Gtid_log_event containing required transaction info for certification"

ER_GRP_RPL_UPDATE_SERV_CERTIFICATE_FAILED
  eng "Unable to update certification result on server side, thread_id: %lu"

ER_GRP_RPL_ADD_GTID_INFO_WITH_LOCAL_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when gtid was provided for local transactions"

ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_LOCAL_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when no gtid was provided for local transactions"

ER_GRP_RPL_NOTIFY_CERTIFICATION_OUTCOME_FAILED
  eng "Failed to notify certification outcome"

ER_GRP_RPL_ADD_GTID_INFO_WITH_REMOTE_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when gtid was provided for remote transactions"

ER_GRP_RPL_ADD_GTID_INFO_WITHOUT_REMOTE_GTID_FAILED
  eng "Unable to add gtid information to the group_gtid_executed set when gtid was not provided for remote transactions"

ER_GRP_RPL_FETCH_VIEW_CHANGE_LOG_EVENT_FAILED
  eng "Failed to fetch View_change_log_event containing required info for certification"

OBSOLETE_ER_GRP_RPL_CONTACT_WITH_SRV_FAILED
  eng "Error when contacting the server to ensure the proper logging of a group change in the binlog"

OBSOLETE_ER_GRP_RPL_SRV_WAIT_TIME_OUT
  eng "Timeout when waiting for the server to execute local transactions in order assure the group change proper logging"

ER_GRP_RPL_FETCH_LOG_EVENT_FAILED
  eng "Failed to fetch Log_event containing required server info for applier"

ER_GRP_RPL_START_GRP_RPL_FAILED
  eng "Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with --initialize, --initialize-insecure or --upgrade=MINIMAL on a server upgrade."

ER_GRP_RPL_CONN_INTERNAL_PLUGIN_FAIL
  eng "Failed to establish an internal server connection to execute plugin operations"

ER_GRP_RPL_SUPER_READ_ON
  eng "Setting super_read_only=ON."

ER_GRP_RPL_SUPER_READ_OFF
  eng "Setting super_read_only=OFF."

ER_GRP_RPL_KILLED_SESSION_ID
  eng "killed session id: %d status: %d"

ER_GRP_RPL_KILLED_FAILED_ID
  eng "killed failed id: %d failed: %d"

ER_GRP_RPL_INTERNAL_QUERY
  eng "Internal query: %s result in error. Error number: %ld"

ER_GRP_RPL_COPY_FROM_EMPTY_STRING
  eng "Error copying from empty string "

ER_GRP_RPL_QUERY_FAIL
  eng "Query execution resulted in failure. errno: %d"

ER_GRP_RPL_CREATE_SESSION_UNABLE
  eng "Unable to create a session for executing the queries on the server"

ER_GRP_RPL_MEMBER_NOT_FOUND
  eng "The member with address %s:%u has unexpectedly disappeared, killing the current group replication recovery connection"

ER_GRP_RPL_MAXIMUM_CONNECTION_RETRIES_REACHED
  eng "Maximum number of retries when trying to connect to a donor reached. Aborting group replication incremental recovery."

ER_GRP_RPL_ALL_DONORS_LEFT_ABORT_RECOVERY
  eng "All donors left. Aborting group replication incremental recovery."

ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_DONOR
  eng "Establishing group recovery connection with a possible donor. Attempt %d/%d"

ER_GRP_RPL_ESTABLISH_RECOVERY_WITH_ANOTHER_DONOR
  eng "Retrying group recovery connection with another donor. Attempt %d/%d"

ER_GRP_RPL_NO_VALID_DONOR
  eng "No valid donors exist in the group, retrying"

ER_GRP_RPL_CONFIG_RECOVERY
  eng "Error when configuring the asynchronous recovery channel connection to the donor."

ER_GRP_RPL_ESTABLISHING_CONN_GRP_REC_DONOR
  eng "Establishing connection to a group replication recovery donor %s at %s port: %d."

ER_GRP_RPL_CREATE_GRP_RPL_REC_CHANNEL
  eng "Error while creating the group replication recovery channel with donor %s at %s port: %d."

ER_GRP_RPL_DONOR_SERVER_CONN
  eng "There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable."

ER_GRP_RPL_CHECK_STATUS_TABLE
  eng "For details please check performance_schema.replication_connection_status table and error log messages of Replica I/O for channel group_replication_recovery."

ER_GRP_RPL_STARTING_GRP_REC
  eng "Error while starting the group replication incremental recovery receiver/applier threads"

ER_GRP_RPL_DONOR_CONN_TERMINATION
  eng "Terminating existing group replication donor connection and purging the corresponding logs."

ER_GRP_RPL_STOPPING_GRP_REC
  eng "Error when stopping the group replication incremental recovery's donor connection"

ER_GRP_RPL_PURGE_REC
  eng "Error when purging the group replication recovery's relay logs"

ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_APPLIER
  eng "Unable to kill the current group replication recovery donor connection after an applier error. Incremental recovery will shutdown."

ER_GRP_RPL_UNABLE_TO_KILL_CONN_REC_DONOR_FAILOVER
  eng "Unable to kill the current group replication recovery donor connection during failover. Incremental recovery will shutdown."

ER_GRP_RPL_FAILED_TO_NOTIFY_GRP_MEMBERSHIP_EVENT
  eng "Unexpected error when notifying an internal component named %s regarding a group membership event."

ER_GRP_RPL_FAILED_TO_BROADCAST_GRP_MEMBERSHIP_NOTIFICATION
  eng "An undefined error was found while broadcasting an internal group membership notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!"

ER_GRP_RPL_FAILED_TO_BROADCAST_MEMBER_STATUS_NOTIFICATION
  eng "An undefined error was found while broadcasting an internal group member status notification! This is likely to happen if your components or plugins are not properly loaded or are malfunctioning!"

ER_GRP_RPL_OOM_FAILED_TO_GENERATE_IDENTIFICATION_HASH
  eng "No memory to generate write identification hash"

ER_GRP_RPL_WRITE_IDENT_HASH_BASE64_ENCODING_FAILED
  eng "Base 64 encoding of the write identification hash failed"

ER_GRP_RPL_INVALID_BINLOG_FORMAT
  eng "Binlog format should be ROW for Group Replication"

OBSOLETE_ER_GRP_RPL_BINLOG_CHECKSUM_SET
  eng "binlog_checksum should be NONE for Group Replication"

ER_GRP_RPL_TRANS_WRITE_SET_EXTRACTION_NOT_SET
  eng "A transaction_write_set_extraction algorithm should be selected when running Group Replication"

ER_GRP_RPL_UNSUPPORTED_TRANS_ISOLATION
  eng "Transaction isolation level (tx_isolation) is set to SERIALIZABLE, which is not compatible with Group Replication"

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_STOPPING
  eng "Transaction cannot be executed while Group Replication is stopping."

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_WHILE_RECOVERING
  eng "Transaction cannot be executed while Group Replication is recovering. Try again when the server is ONLINE."

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_ERROR_STATE
  eng "Transaction cannot be executed while Group Replication is on ERROR state. Check for errors and restart the plugin"

ER_GRP_RPL_CANNOT_EXECUTE_TRANS_IN_OFFLINE_MODE
  eng "Transaction cannot be executed while Group Replication is OFFLINE. Check for errors and restart the plugin"

ER_GRP_RPL_MULTIPLE_CACHE_TYPE_NOT_SUPPORTED_FOR_SESSION
  eng "We can only use one cache type at a time on session %u"

ER_GRP_RPL_FAILED_TO_REINIT_BINLOG_CACHE_FOR_READ
  eng "Failed to reinit binlog cache log for read on session %u"

ER_GRP_RPL_FAILED_TO_CREATE_TRANS_CONTEXT
  eng "Failed to create the context of the current transaction on session %u"

ER_GRP_RPL_FAILED_TO_EXTRACT_TRANS_WRITE_SET
  eng "Failed to extract the set of items written during the execution of the current transaction on session %u"

ER_GRP_RPL_FAILED_TO_GATHER_TRANS_WRITE_SET
  eng "Failed to gather the set of items written during the execution of the current transaction on session %u"

ER_GRP_RPL_TRANS_SIZE_EXCEEDS_LIMIT
  eng "Error on session %u. Transaction of size %llu exceeds specified limit %lu. To increase the limit please adjust group_replication_transaction_size_limit option."

OBSOLETE_ER_GRP_RPL_REINIT_OF_INTERNAL_CACHE_FOR_READ_FAILED
  eng "Error while re-initializing an internal cache, for read operations, on session %u"

OBSOLETE_ER_GRP_RPL_APPENDING_DATA_TO_INTERNAL_CACHE_FAILED
  eng "Error while appending data to an internal cache on session %u"

ER_GRP_RPL_WRITE_TO_TRANSACTION_MESSAGE_FAILED
  eng "Error while writing to transaction message on session %u"

ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_OUTCOME_NOTIFICTION
  eng "Unable to register for getting notifications regarding the outcome of the transaction on session %u"

ER_GRP_RPL_MSG_TOO_LONG_BROADCASTING_TRANS_FAILED
  eng "Error broadcasting transaction to the group on session %u. Message is too big."

ER_GRP_RPL_BROADCASTING_TRANS_TO_GRP_FAILED
  eng "Error while broadcasting the transaction to the group on session %u"

ER_GRP_RPL_ERROR_WHILE_WAITING_FOR_CONFLICT_DETECTION
  eng "Error while waiting for conflict detection procedure to finish on session %u"

OBSOLETE_ER_GRP_RPL_REINIT_OF_INTERNAL_CACHE_FOR_WRITE_FAILED
  eng "Error while re-initializing an internal cache, for write operations, on session %u"

OBSOLETE_ER_GRP_RPL_FAILED_TO_CREATE_COMMIT_CACHE
  eng "Failed to create group replication commit cache on session %u"

OBSOLETE_ER_GRP_RPL_REINIT_OF_COMMIT_CACHE_FOR_WRITE_FAILED
  eng "Failed to reinit group replication commit cache for write on session %u"

OBSOLETE_ER_GRP_RPL_PREV_REC_SESSION_RUNNING
  eng "A previous recovery session is still running. Please stop the group replication plugin and wait for it to stop"

ER_GRP_RPL_FATAL_REC_PROCESS
  eng "Fatal error during the incremental recovery process of Group Replication. The server will leave the group."

OBSOLETE_ER_GRP_RPL_WHILE_STOPPING_REP_CHANNEL
  eng "Error stopping all replication channels while server was leaving the group. %s"

ER_GRP_RPL_UNABLE_TO_EVALUATE_APPLIER_STATUS
  eng "Unable to evaluate the group replication applier execution status. Group replication recovery will shutdown to avoid data corruption."

ER_GRP_RPL_ONLY_ONE_SERVER_ALIVE
  eng "Only one server alive. Declaring this server as online within the replication group"

ER_GRP_RPL_CERTIFICATION_REC_PROCESS
  eng "Error when processing certification information in the incremental recovery process"

ER_GRP_RPL_UNABLE_TO_ENSURE_EXECUTION_REC
  eng "Unable to ensure the execution of group transactions received during recovery."

ER_GRP_RPL_WHILE_SENDING_MSG_REC
  eng "Error while sending message in the group replication incremental recovery process."

OBSOLETE_ER_GRP_RPL_READ_UNABLE_FOR_SUPER_READ_ONLY
  eng "Unable to read the server value for the super_read_only variable."

ER_GRP_RPL_READ_UNABLE_FOR_READ_ONLY_SUPER_READ_ONLY
  eng "Unable to read the server values for the read_only and super_read_only variables."

ER_GRP_RPL_UNABLE_TO_RESET_SERVER_READ_MODE
  eng "Unable to reset the server read mode settings. Try to reset them manually."

ER_GRP_RPL_UNABLE_TO_CERTIFY_PLUGIN_TRANS
  eng "Due to a plugin error, some transactions were unable to be certified and will now rollback."

ER_GRP_RPL_UNBLOCK_CERTIFIED_TRANS
  eng "Error when trying to unblock non certified or consistent transactions. Check for consistency errors when restarting the service"

OBSOLETE_ER_GRP_RPL_SERVER_WORKING_AS_SECONDARY
  eng "This server is working as secondary member with primary member address %s:%u."

ER_GRP_RPL_FAILED_TO_START_WITH_INVALID_SERVER_ID
  eng "Unable to start Group Replication. Replication applier infrastructure is not initialized since the server was started with server_id=0. Please, restart the server with server_id larger than 0."

ER_GRP_RPL_FORCE_MEMBERS_MUST_BE_EMPTY
  eng "group_replication_force_members must be empty on group start. Current value: '%s'"

ER_GRP_RPL_PLUGIN_STRUCT_INIT_NOT_POSSIBLE_ON_SERVER_START
  eng "It was not possible to guarantee the initialization of plugin structures on server start"

ER_GRP_RPL_FAILED_TO_ENABLE_SUPER_READ_ONLY_MODE
  eng "Could not enable the server read only mode and guarantee a safe recovery execution"

ER_GRP_RPL_FAILED_TO_INIT_COMMUNICATION_ENGINE
  eng "Error on group communication engine initialization"

ER_GRP_RPL_FAILED_TO_START_ON_SECONDARY_WITH_ASYNC_CHANNELS
  eng "Can't start group replication on secondary member with single-primary mode while asynchronous replication channels are running."

ER_GRP_RPL_FAILED_TO_START_COMMUNICATION_ENGINE
  eng "Error on group communication engine start"

ER_GRP_RPL_TIMEOUT_ON_VIEW_AFTER_JOINING_GRP
  eng "Timeout on wait for view after joining group"

ER_GRP_RPL_FAILED_TO_CALL_GRP_COMMUNICATION_INTERFACE
  eng "Error calling group communication interfaces"

ER_GRP_RPL_MEMBER_SERVER_UUID_IS_INCOMPATIBLE_WITH_GRP
  eng "Member server_uuid is incompatible with the group. Server_uuid %s matches group_replication_group_name %s."

ER_GRP_RPL_MEMBER_CONF_INFO
  eng "Member configuration: member_id: %lu; member_uuid: \"%s\"; single-primary mode: \"%s\"; group_replication_auto_increment_increment: %lu; group_replication_view_change_uuid: \"%s\";"

ER_GRP_RPL_FAILED_TO_CONFIRM_IF_SERVER_LEFT_GRP
  eng "Unable to confirm whether the server has left the group or not. Check performance_schema.replication_group_members to check group membership information."

ER_GRP_RPL_SERVER_IS_ALREADY_LEAVING
  eng "Skipping leave operation: concurrent attempt to leave the group is on-going."

ER_GRP_RPL_SERVER_ALREADY_LEFT
  eng "Skipping leave operation: member already left the group."

ER_GRP_RPL_WAITING_FOR_VIEW_UPDATE
  eng "Going to wait for view modification"

ER_GRP_RPL_TIMEOUT_RECEIVING_VIEW_CHANGE_ON_SHUTDOWN
  eng "While leaving the group due to a stop, shutdown or failure there was a timeout receiving a view change. This can lead to a possible inconsistent state. Check the log for more details"

ER_GRP_RPL_REQUESTING_NON_MEMBER_SERVER_TO_LEAVE
  eng "Requesting to leave the group despite of not being a member"

ER_GRP_RPL_IS_STOPPING
  eng "Plugin 'group_replication' is stopping."

ER_GRP_RPL_IS_STOPPED
  eng "Plugin 'group_replication' has been stopped."

ER_GRP_RPL_FAILED_TO_ENABLE_READ_ONLY_MODE_ON_SHUTDOWN
  eng "On plugin shutdown it was not possible to enable the server read only mode. Local transactions will be accepted and committed."

ER_GRP_RPL_RECOVERY_MODULE_TERMINATION_TIMED_OUT_ON_SHUTDOWN
  eng "On shutdown there was a timeout on the Group Replication recovery module termination. Check the log for more details"

ER_GRP_RPL_APPLIER_TERMINATION_TIMED_OUT_ON_SHUTDOWN
  eng "On shutdown there was a timeout on the Group Replication applier termination."

ER_GRP_RPL_FAILED_TO_SHUTDOWN_REGISTRY_MODULE
  eng "Unexpected failure while shutting down registry module!"

ER_GRP_RPL_FAILED_TO_INIT_HANDLER
  eng "Failure during Group Replication handler initialization"

ER_GRP_RPL_FAILED_TO_REGISTER_SERVER_STATE_OBSERVER
  eng "Failure when registering the server state observers"

ER_GRP_RPL_FAILED_TO_REGISTER_TRANS_STATE_OBSERVER
  eng "Failure when registering the transactions state observers"

ER_GRP_RPL_FAILED_TO_REGISTER_BINLOG_STATE_OBSERVER
  eng "Failure when registering the binlog state observers"

ER_GRP_RPL_FAILED_TO_START_ON_BOOT
  eng "Unable to start Group Replication on boot"

ER_GRP_RPL_FAILED_TO_STOP_ON_PLUGIN_UNINSTALL
  eng "Failure when stopping Group Replication on plugin uninstall"

ER_GRP_RPL_FAILED_TO_UNREGISTER_SERVER_STATE_OBSERVER
  eng "Failure when unregistering the server state observers"

ER_GRP_RPL_FAILED_TO_UNREGISTER_TRANS_STATE_OBSERVER
  eng "Failure when unregistering the transactions state observers"

ER_GRP_RPL_FAILED_TO_UNREGISTER_BINLOG_STATE_OBSERVER
  eng "Failure when unregistering the binlog state observers"

ER_GRP_RPL_ALL_OBSERVERS_UNREGISTERED
  eng "All Group Replication server observers have been successfully unregistered"

ER_GRP_RPL_FAILED_TO_PARSE_THE_GRP_NAME
  eng "Unable to parse the group_replication_group_name."

ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_GRP
  eng "Unable to parse the group_replication_group_name."

ER_GRP_RPL_APPLIER_NOT_STARTED_DUE_TO_RUNNING_PREV_SHUTDOWN
  eng "Cannot start the Group Replication applier as a previous shutdown is still running: The thread will stop once its task is complete."

ER_GRP_RPL_FAILED_TO_INIT_APPLIER_MODULE
  eng "Unable to initialize the Group Replication applier module."

ER_GRP_RPL_APPLIER_INITIALIZED
  eng "Group Replication applier module successfully initialized!"

ER_GRP_RPL_COMMUNICATION_SSL_CONF_INFO
  eng "Group communication SSL configuration: group_replication_ssl_mode: \"%s\"; server_key_file: \"%s\"; server_cert_file: \"%s\"; client_key_file: \"%s\"; client_cert_file: \"%s\"; ca_file: \"%s\"; ca_path: \"%s\"; cipher: \"%s\"; tls_version: \"%s\"; tls_ciphersuites: \"%s\"; crl_file: \"%s\"; crl_path: \"%s\"; ssl_fips_mode: \"%s\""

ER_GRP_RPL_ABORTS_AS_SSL_NOT_SUPPORTED_BY_MYSQLD
  eng "MySQL server does not have SSL support and group_replication_ssl_mode is \"%s\", START GROUP_REPLICATION will abort"

ER_GRP_RPL_SSL_DISABLED
  eng "Group communication SSL configuration: group_replication_ssl_mode: \"%s\""

ER_GRP_RPL_UNABLE_TO_INIT_COMMUNICATION_ENGINE
  eng "Unable to initialize the group communication engine"

ER_GRP_RPL_BINLOG_DISABLED
  eng "Binlog must be enabled for Group Replication"

ER_GRP_RPL_GTID_MODE_OFF
  eng "Gtid mode should be ON for Group Replication"

ER_GRP_RPL_LOG_REPLICA_UPDATES_NOT_SET
  eng "LOG_REPLICA_UPDATES should be ON for Group Replication"

ER_GRP_RPL_INVALID_TRANS_WRITE_SET_EXTRACTION_VALUE
  eng "Extraction of transaction write sets requires an hash algorithm configuration. Please, double check that the parameter transaction-write-set-extraction is set to a valid algorithm."

ER_GRP_RPL_APPLIER_METADATA_REPO_MUST_BE_TABLE
  eng "Applier metadata repository must be set to TABLE"

ER_GRP_RPL_CONNECTION_METADATA_REPO_MUST_BE_TABLE
  eng "Connection metadata repository must be set to TABLE."

ER_GRP_RPL_INCORRECT_TYPE_SET_FOR_PARALLEL_APPLIER
  eng "In order to use parallel applier on Group Replication, parameter replica-parallel-type must be set to 'LOGICAL_CLOCK'."

ER_GRP_RPL_REPLICA_PRESERVE_COMMIT_ORDER_NOT_SET
  eng "Group Replication requires replica-preserve-commit-order to be set to ON when using more than 1 applier threads."

ER_GRP_RPL_SINGLE_PRIM_MODE_NOT_ALLOWED_WITH_UPDATE_EVERYWHERE
  eng "It is not allowed to run single primary mode with 'group_replication_enforce_update_everywhere_checks' enabled."

ER_GRP_RPL_MODULE_TERMINATE_ERROR
  eng "error_message: %s"

ER_GRP_RPL_GRP_NAME_OPTION_MANDATORY
  eng "The group_replication_group_name option is mandatory"

ER_GRP_RPL_GRP_NAME_IS_TOO_LONG
  eng "The group_replication_group_name '%s' is not a valid UUID, its length is too big"

ER_GRP_RPL_GRP_NAME_IS_NOT_VALID_UUID
  eng "The group_replication_group_name '%s' is not a valid UUID"

ER_GRP_RPL_FLOW_CTRL_MIN_QUOTA_GREATER_THAN_MAX_QUOTA
  eng "group_replication_flow_control_min_quota cannot be larger than group_replication_flow_control_max_quota"

ER_GRP_RPL_FLOW_CTRL_MIN_RECOVERY_QUOTA_GREATER_THAN_MAX_QUOTA
  eng "group_replication_flow_control_min_recovery_quota cannot be larger than group_replication_flow_control_max_quota"

ER_GRP_RPL_FLOW_CTRL_MAX_QUOTA_SMALLER_THAN_MIN_QUOTAS
  eng "group_replication_flow_control_max_quota cannot be smaller than group_replication_flow_control_min_quota or group_replication_flow_control_min_recovery_quota"

ER_GRP_RPL_INVALID_SSL_RECOVERY_STRING
  eng "The given value for recovery ssl option 'group_replication_%s' is invalid as its length is beyond the limit"

OBSOLETE_ER_GRP_RPL_SUPPORTS_ONLY_ONE_FORCE_MEMBERS_SET
  eng "There is one group_replication_force_members operation already ongoing"

OBSOLETE_ER_GRP_RPL_FORCE_MEMBERS_SET_UPDATE_NOT_ALLOWED
  eng "group_replication_force_members can only be updated when Group Replication is running and a majority of the members are unreachable"

ER_GRP_RPL_GRP_COMMUNICATION_INIT_WITH_CONF
  eng "Initialized group communication with configuration: group_replication_group_name: '%s'; group_replication_local_address: '%s'; group_replication_group_seeds: '%s'; group_replication_bootstrap_group: '%s'; group_replication_poll_spin_loops: %lu; group_replication_compression_threshold: %lu; group_replication_ip_allowlist: '%s'; group_replication_communication_debug_options: '%s'; group_replication_member_expel_timeout: '%lu'; group_replication_communication_max_message_size: %lu; group_replication_message_cache_size: '%luu; group_replication_communication_stack: '%lu'"

ER_GRP_RPL_UNKNOWN_GRP_RPL_APPLIER_PIPELINE_REQUESTED
  eng "Unknown group replication applier pipeline requested"

ER_GRP_RPL_FAILED_TO_BOOTSTRAP_EVENT_HANDLING_INFRASTRUCTURE
  eng "Unable to bootstrap group replication event handling infrastructure. Unknown handler type: %d"

ER_GRP_RPL_APPLIER_HANDLER_NOT_INITIALIZED
  eng "One of the group replication applier handlers is null due to an initialization error"

ER_GRP_RPL_APPLIER_HANDLER_IS_IN_USE
  eng "A group replication applier handler, marked as unique, is already in use."

ER_GRP_RPL_APPLIER_HANDLER_ROLE_IS_IN_USE
  eng "A group replication applier handler role, that was marked as unique, is already in use."

ER_GRP_RPL_FAILED_TO_INIT_APPLIER_HANDLER
  eng "Error on group replication applier handler initialization"

ER_GRP_RPL_SQL_SERVICE_FAILED_TO_INIT_SESSION_THREAD
  eng "Error when initializing a session thread for internal server connection."

ER_GRP_RPL_SQL_SERVICE_COMM_SESSION_NOT_INITIALIZED
  eng "Error running internal SQL query: %s. The internal server communication session is not initialized"

ER_GRP_RPL_SQL_SERVICE_SERVER_SESSION_KILLED
  eng "Error running internal SQL query: %s. The internal server session was killed or server is shutting down."

ER_GRP_RPL_SQL_SERVICE_FAILED_TO_RUN_SQL_QUERY
  eng "Error running internal SQL query: %s. Got internal SQL error: %s(%d)"

ER_GRP_RPL_SQL_SERVICE_SERVER_INTERNAL_FAILURE
  eng "Error running internal SQL query: %s. Internal failure."

ER_GRP_RPL_SQL_SERVICE_RETRIES_EXCEEDED_ON_SESSION_STATE
  eng "Error, maximum number of retries exceeded when waiting for the internal server session state to be operating"

ER_GRP_RPL_SQL_SERVICE_FAILED_TO_FETCH_SECURITY_CTX
  eng "Error when trying to fetch security context when contacting the server for internal plugin requests."

ER_GRP_RPL_SQL_SERVICE_SERVER_ACCESS_DENIED_FOR_USER
  eng "There was an error when trying to access the server with user: %s. Make sure the user is present in the server and that the MySQL upgrade procedure was run correctly."

ER_GRP_RPL_SQL_SERVICE_MAX_CONN_ERROR_FROM_SERVER
  eng "Failed to establish an internal server connection to execute plugin operations since the server does not have available connections, please increase @@GLOBAL.MAX_CONNECTIONS. Server error: %i."

ER_GRP_RPL_SQL_SERVICE_SERVER_ERROR_ON_CONN
  eng "Failed to establish an internal server connection to execute plugin operations. Server error: %i. Server error message: %s"

ER_GRP_RPL_UNREACHABLE_MAJORITY_TIMEOUT_FOR_MEMBER
  eng "This member could not reach a majority of the members for more than %ld seconds. The member will now leave the group as instructed by the group_replication_unreachable_majority_timeout option."

ER_GRP_RPL_SERVER_SET_TO_READ_ONLY_DUE_TO_ERRORS
  eng "The server was automatically set into read only mode after an error was detected."

ER_GRP_RPL_GMS_LISTENER_FAILED_TO_LOG_NOTIFICATION
  eng "Unable to log notification to table (errno: %lu) (res: %d)! Message: %s"

ER_GRP_RPL_GRP_COMMUNICATION_ENG_INIT_FAILED
  eng "Failure in group communication engine '%s' initialization"

ER_GRP_RPL_SET_GRP_COMMUNICATION_ENG_LOGGER_FAILED
  eng "Unable to set the group communication engine logger"

ER_GRP_RPL_DEBUG_OPTIONS
  eng "Current debug options are: '%s'."

ER_GRP_RPL_INVALID_DEBUG_OPTIONS
  eng "Some debug options in '%s' are not valid."

ER_GRP_RPL_EXIT_GRP_GCS_ERROR
  eng "Error calling group communication interfaces while trying to leave the group"

ER_GRP_RPL_GRP_MEMBER_OFFLINE
  eng "Member is not ONLINE, it is not possible to force a new group membership"

ER_GRP_RPL_GCS_INTERFACE_ERROR
  eng "Error calling group communication interfaces"

ER_GRP_RPL_FORCE_MEMBER_VALUE_SET_ERROR
  eng "Error setting group_replication_force_members value '%s' on group communication interfaces"

ER_GRP_RPL_FORCE_MEMBER_VALUE_SET
  eng "The group_replication_force_members value '%s' was set in the group communication interfaces"

ER_GRP_RPL_FORCE_MEMBER_VALUE_TIME_OUT
  eng "Timeout on wait for view after setting group_replication_force_members value '%s' into group communication interfaces"

ER_GRP_RPL_BROADCAST_COMMIT_MSSG_TOO_BIG
  eng "Broadcast of committed transactions message failed. Message is too big."

ER_GRP_RPL_SEND_STATS_ERROR
  eng "Error while sending stats message"

ER_GRP_RPL_MEMBER_STATS_INFO
  eng "Flow control - update member stats: %s stats certifier_queue %d, applier_queue %d certified %ld (%ld), applied %ld (%ld), local %ld (%ld), quota %ld (%ld) mode=%d"

ER_GRP_RPL_FLOW_CONTROL_STATS
  eng "Flow control: throttling to %ld commits per %ld sec, with %d writing and %d non-recovering members, min capacity %lld, lim throttle %lld"

ER_GRP_RPL_UNABLE_TO_CONVERT_PACKET_TO_EVENT
  eng "Unable to convert a packet into an event on the applier. Error: %s"

ER_GRP_RPL_PIPELINE_CREATE_FAILED
  eng "Failed to create group replication pipeline cache."

ER_GRP_RPL_PIPELINE_REINIT_FAILED_WRITE
  eng "Failed to reinit group replication pipeline cache for write."

ER_GRP_RPL_UNABLE_TO_CONVERT_EVENT_TO_PACKET
  eng "Unable to convert the event into a packet on the applier. Error: %s"

ER_GRP_RPL_PIPELINE_FLUSH_FAIL
  eng "Failed to flush group replication pipeline cache."

ER_GRP_RPL_PIPELINE_REINIT_FAILED_READ
  eng "Failed to reinit group replication pipeline cache for read."

OBSOLETE_ER_GRP_RPL_STOP_REP_CHANNEL
  eng "Error stopping all replication channels while server was leaving the group. Got error: %d. Please check the error log for more details."

ER_GRP_RPL_GCS_GR_ERROR_MSG
  eng "%s"

ER_GRP_RPL_REPLICA_IO_THREAD_UNBLOCKED
  eng "The replica IO thread of channel '%s' is unblocked as the member is declared ONLINE now."

ER_GRP_RPL_REPLICA_IO_THREAD_ERROR_OUT
  eng "The replica IO thread of channel '%s' will error out as the member failed to come ONLINE."

ER_GRP_RPL_REPLICA_APPLIER_THREAD_UNBLOCKED
  eng "The replica applier thread of channel '%s' is unblocked as the member is declared ONLINE now."

ER_GRP_RPL_REPLICA_APPLIER_THREAD_ERROR_OUT
  eng "The replica applier thread of channel '%s' will error out as the member failed to come ONLINE."

ER_LDAP_AUTH_FAILED_TO_CREATE_OR_GET_CONNECTION
  eng "LDAP authentication initialize: failed to create/ get connection from the pool. "

ER_LDAP_AUTH_DEINIT_FAILED
  eng "LDAP authentication de_initialize Failed"

ER_LDAP_AUTH_SKIPPING_USER_GROUP_SEARCH
  eng "Skipping group search, No group attribute mentioned"

ER_LDAP_AUTH_POOL_DISABLE_MAX_SIZE_ZERO
  eng "Pool max size is 0, connection pool is disabled"

ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT_CREATOR
  eng "Connection pool initialization, failed to create LDAP object creator"

ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_OBJECT
  eng "Connection pool initialization, failed to create LDAP object"

ER_LDAP_AUTH_TLS_CONF
  eng "LDAP TLS configuration"

ER_LDAP_AUTH_TLS_CONNECTION
  eng "LDAP TLS connection"

ER_LDAP_AUTH_CONN_POOL_NOT_CREATED
  eng "LDAP pool is not created."

ER_LDAP_AUTH_CONN_POOL_INITIALIZING
  eng "LDAP pool is initializing"

ER_LDAP_AUTH_CONN_POOL_DEINITIALIZING
  eng "LDAP pool is de-initializing"

ER_LDAP_AUTH_ZERO_MAX_POOL_SIZE_UNCHANGED
  eng "Pool max size old and new values are 0"

ER_LDAP_AUTH_POOL_REINITIALIZING
  eng "LDAP pool is re-initializing"

ER_LDAP_AUTH_FAILED_TO_WRITE_PACKET
  eng "Plug-in has failed to write the packet."

ER_LDAP_AUTH_SETTING_USERNAME
  eng "Setting LDAP user name as : %s"

ER_LDAP_AUTH_USER_AUTH_DATA
  eng "User authentication data: %s size: %lu"

ER_LDAP_AUTH_INFO_FOR_USER
  eng "User is authenticated as: %s external user: %s"

ER_LDAP_AUTH_USER_GROUP_SEARCH_INFO
  eng "Group search information base DN: %s scope: %d filter: %s attribute: %s"

ER_LDAP_AUTH_GRP_SEARCH_SPECIAL_HDL
  eng "Special handling for group search, {GA} found"

ER_LDAP_AUTH_GRP_IS_FULL_DN
  eng "Group search special handling, group full DN found. "

ER_LDAP_AUTH_USER_NOT_FOUND_IN_ANY_GRP
  eng "User %s is not member of any group."

ER_LDAP_AUTH_USER_FOUND_IN_MANY_GRPS
  eng "User %s is member of more than one group"

ER_LDAP_AUTH_USER_HAS_MULTIPLE_GRP_NAMES
  eng "For user %s has multiple user group names. Please check if group attribute name is correct"

ER_LDAP_AUTH_SEARCHED_USER_GRP_NAME
  eng "Searched group name: %s"

ER_LDAP_AUTH_OBJECT_CREATE_TIMESTAMP
  eng "LDAP authentication object creation time_stamp: %s dn: %s"

ER_LDAP_AUTH_CERTIFICATE_NAME
  eng "Certificate name: %s"

ER_LDAP_AUTH_FAILED_TO_POOL_DEINIT
  eng "Failed to pool de-initialized: pool is already reconstructing"

ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_RECONSTRUCTING
  eng "Pool initialization failed: pool is already initialized"

ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_INIT_STATE
  eng "Pool initialization failed: pool is initializing"

ER_LDAP_AUTH_FAILED_TO_INITIALIZE_POOL_IN_DEINIT_STATE
  eng "Pool initialization failed: pool is de-initializing"

ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_POOL_IN_RECONSTRUCT_STATE
  eng "Failed to pool deinitialized: pool is already reconstructing"

ER_LDAP_AUTH_FAILED_TO_DEINITIALIZE_NOT_READY_POOL
  eng "Failed to pool deinitialized : pool is not ready"

ER_LDAP_AUTH_FAILED_TO_GET_CONNECTION_AS_PLUGIN_NOT_READY
  eng "Ldap_connection_pool::get: Failed to return connection as plug-in is not ready/initializing/de-initializing"

ER_LDAP_AUTH_CONNECTION_POOL_INIT_FAILED
  eng "Connection pool has failed to initialized"

ER_LDAP_AUTH_MAX_ALLOWED_CONNECTION_LIMIT_HIT
  eng "Ldap_connetion_pool::get LDAP maximum connection allowed size is reached. Increase the maximum limit."

ER_LDAP_AUTH_MAX_POOL_SIZE_SET_FAILED
  eng "Set max pool size failed."

ER_LDAP_AUTH_PLUGIN_FAILED_TO_READ_PACKET
  eng "Plug-in has failed to read the packet from client"

ER_LDAP_AUTH_CREATING_LDAP_CONNECTION
  eng "Ldap_authentication::initialize: creating new LDAP connection. "

ER_LDAP_AUTH_GETTING_CONNECTION_FROM_POOL
  eng "Ldap_authentication::initialize: getting connection from pool. "

ER_LDAP_AUTH_RETURNING_CONNECTION_TO_POOL
  eng "Ldap_authentication::de_initialize putting back connection in the pool"

ER_LDAP_AUTH_SEARCH_USER_GROUP_ATTR_NOT_FOUND
  eng "Ldap_authentication::search_user_group no group attribute found"

ER_LDAP_AUTH_LDAP_INFO_NULL
  eng "Ldap_connetion_pool::put ldap info null"

ER_LDAP_AUTH_FREEING_CONNECTION
  eng "Ldap_connection_pool::put connection is freeing. "

ER_LDAP_AUTH_CONNECTION_PUSHED_TO_POOL
  eng "Ldap_connection_pool::put connection in pushed in the pool"

ER_LDAP_AUTH_CONNECTION_CREATOR_ENTER
  eng "Ldap_connection_creator::Ldap_connection_creator"

ER_LDAP_AUTH_STARTING_TLS
  eng "starting TLS"

ER_LDAP_AUTH_CONNECTION_GET_LDAP_INFO_NULL
  eng "Ldap_connection_pool::get: (ldap_info == NULL)|| (*ldap_info)"

ER_LDAP_AUTH_DELETING_CONNECTION_KEY
  eng "Ldap_connection_pool::deinit: deleting connection key %s"

ER_LDAP_AUTH_POOLED_CONNECTION_KEY
  eng " Ldap_connection_pool::get pooled connection key: %s"

ER_LDAP_AUTH_CREATE_CONNECTION_KEY
  eng "Ldap_connection_pool::get create connection key: %s"

ER_LDAP_AUTH_COMMUNICATION_HOST_INFO
  eng "LDAP communication host %s port %u"

ER_LDAP_AUTH_METHOD_TO_CLIENT
  eng "Sending authentication method to client : %s"

ER_LDAP_AUTH_SASL_REQUEST_FROM_CLIENT
  eng "SASL request received from mysql client: %s"

ER_LDAP_AUTH_SASL_PROCESS_SASL
  eng "Ldap_sasl_authentication::process_sasl rc: %s"

ER_LDAP_AUTH_SASL_BIND_SUCCESS_INFO
  eng "Ldap_sasl_authentication::process_sasl sasl bind succeed. dn: %s method: %s server credential: %s"

ER_LDAP_AUTH_STARTED_FOR_USER
  eng "LDAP authentication started for user name: %s"

ER_LDAP_AUTH_DISTINGUISHED_NAME
  eng "%s"

ER_LDAP_AUTH_INIT_FAILED
  eng "LDAP authentication initialize is failed with: %s"

ER_LDAP_AUTH_OR_GROUP_RETRIEVAL_FAILED
  eng "LDAP authentication failed or group retrieval failed: %s"

ER_LDAP_AUTH_USER_GROUP_SEARCH_FAILED
  eng "Search user group has failed: %s"

ER_LDAP_AUTH_USER_BIND_FAILED
  eng "LDAP user bind has failed: %s"

ER_LDAP_AUTH_POOL_GET_FAILED_TO_CREATE_CONNECTION
  eng "Connection pool get: Failed to create LDAP connection. %s"

ER_LDAP_AUTH_FAILED_TO_CREATE_LDAP_CONNECTION
  eng "Failed to create new LDAP connection:  %s"

ER_LDAP_AUTH_FAILED_TO_ESTABLISH_TLS_CONNECTION
  eng "Failed to establish TLS connection:  %s"

ER_LDAP_AUTH_FAILED_TO_SEARCH_DN
  eng "Failed to search user full dn: %s"

ER_LDAP_AUTH_CONNECTION_POOL_REINIT_ENTER
  eng "Ldap_connection_pool::reinit"

ER_SYSTEMD_NOTIFY_PATH_TOO_LONG
  eng "The path '%s', from the NOTIFY_SOCKET environment variable, is too long. At %u bytes it exceeds the limit of %u bytes for an AF_UNIX socket."

ER_SYSTEMD_NOTIFY_CONNECT_FAILED
  eng "Failed to connect to systemd notification socket named %s. Error: '%s'"

ER_SYSTEMD_NOTIFY_WRITE_FAILED
  eng "Failed to write '%s' to systemd notification. Error: '%s'"

ER_FOUND_MISSING_GTIDS
  eng "Cannot replicate to server with server_uuid='%.36s' because the present server has purged required binary logs. The connecting server needs to replicate the missing transactions from elsewhere, or be replaced by a new server created from a more recent backup. To prevent this error in the future, consider increasing the binary log expiration period on the present server. %s."

ER_PID_FILE_PRIV_DIRECTORY_INSECURE
  eng "Insecure configuration for --pid-file: Location '%s' in the path is accessible to all OS users. Consider choosing a different directory."

ER_CANT_CHECK_PID_PATH
  eng "Can't start server: can't check PID filepath: %s"

ER_VALIDATE_PWD_STATUS_VAR_REGISTRATION_FAILED
  eng "validate_password status variables registration failed."

ER_VALIDATE_PWD_STATUS_VAR_UNREGISTRATION_FAILED
  eng "validate_password status variables unregistration failed."

ER_VALIDATE_PWD_DICT_FILE_OPEN_FAILED
  eng "Dictionary file open failed"

ER_VALIDATE_PWD_COULD_BE_NULL
  eng "given password string could be null"

ER_VALIDATE_PWD_STRING_CONV_TO_LOWERCASE_FAILED
  eng "failed to convert the password string to lower case"

ER_VALIDATE_PWD_STRING_CONV_TO_BUFFER_FAILED
  eng "failed to convert the password string into a buffer"

ER_VALIDATE_PWD_STRING_HANDLER_MEM_ALLOCATION_FAILED
  eng "memory allocation failed for string handler"

ER_VALIDATE_PWD_STRONG_POLICY_DICT_FILE_UNSPECIFIED
  eng "Since the validate_password_policy is mentioned as Strong, dictionary file must be specified"

ER_VALIDATE_PWD_CONVERT_TO_BUFFER_FAILED
  eng "convert_to_buffer service failed"

ER_VALIDATE_PWD_VARIABLE_REGISTRATION_FAILED
  eng "%s variable registration failed."

ER_VALIDATE_PWD_VARIABLE_UNREGISTRATION_FAILED
  eng "%s variable unregistration failed."

ER_KEYRING_MIGRATION_EXTRA_OPTIONS
  eng "Please specify options specific to keyring migration. Any additional options can be ignored. NOTE: Although some options are valid, migration tool can still report error example: plugin variables for which plugin is not loaded yet."

OBSOLETE_ER_INVALID_DEFAULT_UTF8MB4_COLLATION
  eng "Invalid default collation %s: utf8mb4_0900_ai_ci or utf8mb4_general_ci expected"

ER_IB_MSG_0
  eng "%s"

ER_IB_MSG_1
  eng "%s"

ER_IB_MSG_2
  eng "%s"

ER_IB_MSG_3
  eng "%s"

ER_IB_MSG_4
  eng "%s"

ER_IB_MSG_5
  eng "%s"

ER_IB_MSG_6
  eng "%s"

ER_IB_MSG_7
  eng "%s"

ER_IB_MSG_8
  eng "%s"

ER_IB_MSG_9
  eng "%s"

ER_IB_MSG_10
  eng "%s"

ER_IB_MSG_11
  eng "%s"

ER_IB_MSG_12
  eng "%s"

ER_IB_MSG_13
  eng "%s"

ER_IB_MSG_14
  eng "%s"

ER_IB_MSG_15
  eng "%s"

ER_IB_MSG_16
  eng "%s"

ER_IB_MSG_17
  eng "%s"

ER_IB_MSG_18
  eng "%s"

ER_IB_MSG_19
  eng "%s"

ER_IB_MSG_20
  eng "%s"

ER_IB_MSG_21
  eng "%s"

ER_IB_MSG_22
  eng "%s"

ER_IB_MSG_23
  eng "%s"

ER_IB_MSG_24
  eng "%s"

ER_IB_MSG_25
  eng "%s"

ER_IB_MSG_26
  eng "%s"

ER_IB_MSG_27
  eng "%s"

ER_IB_MSG_28
  eng "%s"

ER_IB_MSG_29
  eng "%s"

ER_IB_MSG_30
  eng "%s"

ER_IB_MSG_31
  eng "%s"

ER_IB_MSG_32
  eng "%s"

ER_IB_MSG_33
  eng "%s"

ER_IB_MSG_34
  eng "%s"

ER_IB_MSG_35
  eng "%s"

ER_IB_MSG_36
  eng "%s"

ER_IB_MSG_37
  eng "%s"

ER_IB_MSG_38
  eng "%s"

ER_IB_MSG_39
  eng "%s"

ER_IB_MSG_40
  eng "%s"

ER_IB_MSG_41
  eng "%s"

ER_IB_MSG_42
  eng "%s"

ER_IB_MSG_43
  eng "%s"

ER_IB_MSG_44
  eng "%s"

ER_IB_MSG_45
  eng "%s"

ER_IB_MSG_46
  eng "%s"

ER_IB_MSG_47
  eng "%s"

ER_IB_MSG_48
  eng "%s"

ER_IB_MSG_49
  eng "%s"

ER_IB_MSG_50
  eng "%s"

ER_IB_MSG_51
  eng "%s"

ER_IB_MSG_52
  eng "%s"

ER_IB_MSG_53
  eng "%s"

ER_IB_MSG_54
  eng "Failed to set NUMA memory policy of buffer pool page frames with mbind(%p,%zu,%s,...,...,%s) failed with %s"

ER_IB_MSG_55
  eng "%s"

ER_IB_MSG_56
  eng "%s"

ER_IB_MSG_57
  eng "%s"

ER_IB_MSG_58
  eng "%s"

ER_IB_MSG_59
  eng "%s"

ER_IB_MSG_60
  eng "%s"

ER_IB_MSG_61
  eng "%s"

ER_IB_MSG_62
  eng "%s"

ER_IB_MSG_63
  eng "%s"

ER_IB_MSG_64
  eng "%s"

ER_IB_MSG_65
  eng "%s"

ER_IB_MSG_66
  eng "%s"

ER_IB_MSG_67
  eng "%s"

ER_IB_MSG_68
  eng "%s"

ER_IB_MSG_69
  eng "%s"

ER_IB_MSG_70
  eng "%s"

ER_IB_MSG_71
  eng "%s"

ER_IB_MSG_72
  eng "%s"

ER_IB_MSG_73
  eng "%s"

ER_IB_MSG_74
  eng "%s"

ER_IB_MSG_75
  eng "%s"

ER_IB_MSG_76
  eng "%s"

ER_IB_MSG_77
  eng "%s"

ER_IB_MSG_78
  eng "%s"

ER_IB_MSG_79
  eng "%s"

ER_IB_MSG_80
  eng "%s"

ER_IB_MSG_81
  eng "%s"

ER_IB_MSG_82
  eng "%s"

ER_IB_ERR_PAGE_DIRTY_AT_SHUTDOWN
  eng "Page still fixed or dirty at shutdown. %s"

ER_IB_MSG_84
  eng "%s"

ER_IB_MSG_85
  eng "%s"

ER_IB_MSG_86
  eng "%s"

OBSOLETE_ER_IB_MSG_87
  eng "%s"

OBSOLETE_ER_IB_MSG_88
  eng "%s"

OBSOLETE_ER_IB_MSG_89
  eng "%s"

OBSOLETE_ER_IB_MSG_90
  eng "%s"

OBSOLETE_ER_IB_MSG_91
  eng "%s"

OBSOLETE_ER_IB_MSG_92
  eng "%s"

OBSOLETE_ER_IB_MSG_93
  eng "%s"

OBSOLETE_ER_IB_MSG_94
  eng "%s"

ER_IB_MSG_95
  eng "%s"

ER_IB_MSG_96
  eng "%s"

ER_IB_MSG_97
  eng "%s"

ER_IB_MSG_98
  eng "%s"

ER_IB_MSG_99
  eng "%s"

ER_IB_MSG_100
  eng "%s"

ER_IB_MSG_101
  eng "%s"

ER_IB_MSG_102
  eng "%s"

ER_IB_MSG_103
  eng "%s"

ER_IB_MSG_104
  eng "%s"

ER_IB_MSG_105
  eng "%s"

ER_IB_MSG_106
  eng "%s"

ER_IB_MSG_107
  eng "%s"

ER_IB_MSG_108
  eng "%s"

ER_IB_MSG_109
  eng "%s"

ER_IB_MSG_110
  eng "%s"

ER_IB_MSG_111
  eng "%s"

ER_IB_MSG_112
  eng "%s"

OBSOLETE_ER_IB_MSG_113
  eng "%s"

OBSOLETE_ER_IB_MSG_114
  eng "%s"

OBSOLETE_ER_IB_MSG_115
  eng "%s"

OBSOLETE_ER_IB_MSG_116
  eng "%s"

OBSOLETE_ER_IB_MSG_117
  eng "%s"

OBSOLETE_ER_IB_MSG_118
  eng "%s"

ER_IB_MSG_119
  eng "%s"

ER_IB_MSG_120
  eng "%s"

ER_IB_MSG_121
  eng "%s"

ER_IB_MSG_122
  eng "%s"

ER_IB_MSG_123
  eng "%s"

ER_IB_MSG_124
  eng "%s"

ER_IB_MSG_125
  eng "%s"

ER_IB_MSG_126
  eng "%s"

ER_IB_MSG_127
  eng "%s"

ER_IB_MSG_128
  eng "%s"

ER_IB_MSG_129
  eng "%s"

ER_IB_MSG_130
  eng "%s"

ER_IB_MSG_131
  eng "%s"

ER_IB_MSG_132
  eng "%s"

ER_IB_MSG_133
  eng "%s"

ER_IB_MSG_134
  eng "%s"

ER_IB_MSG_135
  eng "%s"

ER_IB_MSG_136
  eng "%s"

ER_IB_MSG_137
  eng "%s"

ER_IB_MSG_138
  eng "%s"

ER_IB_MSG_139
  eng "%s"

ER_IB_MSG_140
  eng "%s"

ER_IB_MSG_141
  eng "%s"

ER_IB_MSG_142
  eng "%s"

ER_IB_MSG_143
  eng "%s"

ER_IB_MSG_144
  eng "%s"

ER_IB_MSG_145
  eng "%s"

ER_IB_MSG_146
  eng "%s"

ER_IB_MSG_147
  eng "%s"

ER_IB_MSG_148
  eng "%s"

ER_IB_CLONE_INTERNAL
  eng "%s"

ER_IB_CLONE_TIMEOUT
  eng "%s"

ER_IB_CLONE_STATUS_FILE
  eng "%s"

ER_IB_CLONE_SQL
  eng "%s"

ER_IB_CLONE_VALIDATE
  eng "%s"

ER_IB_CLONE_PUNCH_HOLE
  eng "%s"

ER_IB_CLONE_GTID_PERSIST
  eng "%s"

ER_IB_MSG_156
  eng "%s"

ER_IB_MSG_157
  eng "%s"

ER_IB_MSG_158
  eng "%s"

ER_IB_MSG_159
  eng "%s"

ER_IB_MSG_160
  eng "%s"

ER_IB_MSG_161
  eng "%s"

ER_IB_MSG_162
  eng "%s"

ER_IB_MSG_163
  eng "%s"

ER_IB_MSG_164
  eng "%s"

ER_IB_MSG_165
  eng "%s"

ER_IB_MSG_166
  eng "%s"

ER_IB_MSG_167
  eng "%s"

ER_IB_MSG_168
  eng "%s"

ER_IB_MSG_169
  eng "%s"

ER_IB_MSG_170
  eng "%s"

ER_IB_MSG_171
  eng "%s"

ER_IB_MSG_172
  eng "%s"

ER_IB_MSG_173
  eng "%s"

ER_IB_MSG_174
  eng "%s"

ER_IB_MSG_175
  eng "%s"

ER_IB_MSG_176
  eng "%s"

ER_IB_MSG_177
  eng "%s"

ER_IB_MSG_178
  eng "%s"

ER_IB_MSG_179
  eng "%s"

ER_IB_MSG_180
  eng "%s"

ER_IB_LONG_AHI_DISABLE_WAIT
  eng "Waited for %u secs for hash index ref_count (%zu) to drop to 0. index: \"%s\" table: \"%s\""

ER_IB_MSG_182
  eng "%s"

ER_IB_MSG_183
  eng "%s"

ER_IB_MSG_184
  eng "%s"

ER_IB_MSG_185
  eng "%s"

ER_IB_MSG_186
  eng "%s"

ER_IB_MSG_187
  eng "%s"

ER_IB_MSG_188
  eng "%s"

ER_IB_MSG_189
  eng "%s"

ER_IB_MSG_190
  eng "%s"

ER_IB_MSG_191
  eng "%s"

ER_IB_MSG_192
  eng "%s"

ER_IB_MSG_193
  eng "%s"

ER_IB_MSG_194
  eng "%s"

ER_IB_MSG_195
  eng "%s"

ER_IB_MSG_196
  eng "%s"

ER_IB_MSG_197
  eng "%s"

ER_IB_MSG_198
  eng "%s"

ER_IB_MSG_199
  eng "%s"

ER_IB_MSG_200
  eng "%s"

ER_IB_MSG_201
  eng "%s"

ER_IB_MSG_202
  eng "%s"

ER_IB_MSG_203
  eng "%s"

ER_IB_MSG_204
  eng "%s"

ER_IB_MSG_205
  eng "%s"

ER_IB_MSG_206
  eng "%s"

ER_IB_MSG_207
  eng "%s"

ER_IB_MSG_208
  eng "%s"

ER_IB_MSG_209
  eng "%s"

ER_IB_MSG_210
  eng "%s"

ER_IB_MSG_211
  eng "%s"

ER_IB_MSG_212
  eng "%s"

ER_IB_MSG_213
  eng "%s"

ER_IB_MSG_214
  eng "%s"

ER_IB_MSG_215
  eng "%s"

ER_IB_MSG_216
  eng "%s"

ER_IB_MSG_217
  eng "%s"

ER_IB_MSG_218
  eng "%s"

ER_IB_MSG_219
  eng "%s"

ER_IB_MSG_220
  eng "%s"

ER_IB_MSG_221
  eng "%s"

ER_IB_MSG_222
  eng "%s"

ER_IB_MSG_223
  eng "%s"

ER_IB_MSG_224
  eng "%s"

ER_IB_MSG_225
  eng "%s"

ER_IB_MSG_226
  eng "%s"

ER_IB_MSG_227
  eng "%s"

ER_IB_MSG_228
  eng "%s"

ER_IB_MSG_229
  eng "%s"

ER_IB_MSG_230
  eng "%s"

ER_IB_MSG_231
  eng "%s"

ER_IB_MSG_232
  eng "%s"

ER_IB_MSG_233
  eng "%s"

ER_IB_MSG_234
  eng "%s"

ER_IB_MSG_235
  eng "%s"

ER_IB_MSG_236
  eng "%s"

ER_IB_MSG_237
  eng "%s"

ER_IB_MSG_238
  eng "%s"

ER_IB_MSG_239
  eng "%s"

ER_IB_MSG_240
  eng "%s"

ER_IB_MSG_241
  eng "%s"

ER_IB_MSG_242
  eng "%s"

ER_IB_MSG_243
  eng "%s"

ER_IB_MSG_244
  eng "%s"

ER_IB_MSG_245
  eng "%s"

ER_IB_MSG_246
  eng "%s"

ER_IB_MSG_247
  eng "%s"

ER_IB_MSG_248
  eng "%s"

ER_IB_MSG_249
  eng "%s"

ER_IB_MSG_250
  eng "%s"

ER_IB_MSG_251
  eng "%s"

ER_IB_MSG_252
  eng "%s"

ER_IB_MSG_253
  eng "%s"

ER_IB_MSG_254
  eng "%s"

ER_IB_MSG_255
  eng "%s"

ER_IB_MSG_256
  eng "%s"

ER_IB_MSG_257
  eng "%s"

ER_IB_MSG_258
  eng "%s"

ER_IB_MSG_259
  eng "%s"

ER_IB_MSG_260
  eng "%s"

ER_IB_MSG_261
  eng "%s"

ER_IB_MSG_262
  eng "%s"

ER_IB_MSG_263
  eng "%s"

ER_IB_MSG_264
  eng "%s"

ER_IB_MSG_265
  eng "%s"

ER_IB_MSG_266
  eng "%s"

ER_IB_MSG_267
  eng "%s"

ER_IB_MSG_268
  eng "%s"

ER_IB_MSG_269
  eng "%s"

ER_IB_MSG_270
  eng "%s"

ER_IB_MSG_271
  eng "%s"

ER_IB_MSG_272
  eng "Table flags are 0x%lx in the data dictionary but the flags in file %s  are 0x%llx!"

ER_IB_MSG_273
  eng "Can't read encryption key from file %s!"

OBSOLETE_ER_IB_MSG_274
  eng "Cannot close file %s, because n_pending_flushes %zu"

OBSOLETE_ER_IB_MSG_275
  eng "Cannot close file %s, because modification count %lld != flush count %lld"

OBSOLETE_ER_IB_MSG_276
  eng "Cannot close file %s, because it is in use"

OBSOLETE_ER_IB_MSG_277
  eng "Open file list len in shard %zu is %llu"

ER_IB_MSG_278
  eng "Tablespace %s, waiting for IO to stop for %lld seconds"

OBSOLETE_ER_IB_MSG_279
  eng "%s"

ER_IB_MSG_280
  eng "%s"

ER_IB_MSG_281
  eng "%s"

ER_IB_MSG_282
  eng "%s"

ER_IB_MSG_283
  eng "%s"

ER_IB_MSG_284
  eng "You must raise the value of innodb_open_files in my.cnf! Remember that InnoDB keeps all redo log files and all system tablespace files open for the whole time mysqld is running, and needs to open also some .ibd files if the file-per-table storage model is used. Current open files %zu, max allowed open files %zu."

ER_IB_MSG_285
  eng "Max tablespace id is too high, %lu"

ER_IB_WARN_ACCESSING_NONEXISTINC_SPACE
  eng "Trying to access missing tablespace %lu"

ER_IB_MSG_287
  eng "Trying to close/delete tablespace '%s' but there are %lu pending operations on it."

ER_IB_MSG_288
  eng "Trying to delete/close tablespace '%s' but there are %lu flushes and %zu pending I/O's on it."

ER_IB_MSG_289
  eng "%s"

OBSOLETE_ER_IB_MSG_290
  eng "Cannot delete tablespace %lu because it is not found in the tablespace memory cache."

ER_IB_MSG_291
  eng "While deleting tablespace %lu in DISCARD TABLESPACE. File rename/delete failed: %s"

ER_IB_MSG_292
  eng "Cannot delete tablespace %lu in DISCARD TABLESPACE: %s"

ER_IB_MSG_293
  eng "Cannot rename '%s' to '%s' for space ID %lu because the source file does not exist."

ER_IB_MSG_294
  eng "Cannot rename '%s' to '%s' for space ID %lu because the target file exists. Remove the target file and try again."

ER_IB_MSG_295
  eng "Cannot rename file '%s' (space id %lu) retried %llu times. There are either pending IOs or flushes or the file is being extended."

ER_IB_MSG_296
  eng "Cannot find space id %lu in the tablespace memory cache, though the file '%s' in a rename operation should have that ID."

ER_IB_MSG_297
  eng "Rename waiting for IO to resume"

ER_IB_MSG_298
  eng "Cannot find tablespace for '%s' in the tablespace memory cache"

ER_IB_MSG_299
  eng "Cannot find tablespace for '%s' in the tablespace memory cache"

ER_IB_MSG_300
  eng "Tablespace '%s' is already in the tablespace memory cache"

ER_IB_MSG_301
  eng "Cannot create file '%s'"

ER_IB_MSG_UNEXPECTED_FILE_EXISTS
  eng "The file '%s' already exists though the corresponding table did not exist. Have you moved InnoDB .ibd files around without using the SQL commands DISCARD TABLESPACE and IMPORT TABLESPACE, or did mysqld crash in the middle of CREATE TABLE? You can resolve the problem by removing the file '%s' under the 'datadir' of MySQL."

ER_IB_MSG_303
  eng "posix_fallocate(): Failed to preallocate data for file %s, desired size %llu Operating system error number %d - %s. Check that the disk is not full or a disk quota exceeded. Make sure the file system supports this function. Refer to your operating system documentation for operating system error code information."

ER_IB_MSG_304
  eng "Could not write the first page to tablespace '%s'"

ER_IB_MSG_305
  eng "File flush of tablespace '%s' failed"

ER_IB_MSG_306
  eng "Could not find a valid tablespace file for `%s`. %s"

ER_IB_MSG_307
  eng "Ignoring data file '%s' with space ID %lu. Another data file called '%s' exists with the same space ID"

ER_IB_MSG_308
  eng "%s"

ER_IB_MSG_309
  eng "%s"

ER_IB_MSG_310
  eng "%s"

ER_IB_MSG_311
  eng "%s"

ER_IB_MSG_312
  eng "Can't set encryption information for tablespace %s!"

ER_IB_MSG_313
  eng "%s"

ER_IB_MSG_314
  eng "%s"

ER_IB_MSG_315
  eng "%s"

ER_IB_MSG_316
  eng "%s"

ER_IB_MSG_317
  eng "%s"

ER_IB_MSG_318
  eng "%s"

ER_IB_MSG_319
  eng "%s"

ER_IB_MSG_320
  eng "%s"

ER_IB_MSG_321
  eng "%s"

ER_IB_MSG_322
  eng "%s"

ER_IB_MSG_323
  eng "%s"

ER_IB_MSG_324
  eng "%s"

ER_IB_MSG_325
  eng "%s"

ER_IB_MSG_326
  eng "%s"

OBSOLETE_ER_IB_MSG_327
  eng "%s"

ER_IB_MSG_328
  eng "%s"

ER_IB_MSG_329
  eng "%s"

ER_IB_MSG_330
  eng "%s"

ER_IB_MSG_331
  eng "%s"

ER_IB_MSG_332
  eng "%s"

ER_IB_MSG_333
  eng "%s"

ER_IB_MSG_334
  eng "%s"

ER_IB_MSG_335
  eng "%s"

ER_IB_MSG_336
  eng "%s"

ER_IB_MSG_337
  eng "%s"

ER_IB_MSG_338
  eng "%s"

ER_IB_MSG_339
  eng "%s"

ER_IB_MSG_340
  eng "%s"

ER_IB_MSG_341
  eng "%s"

ER_IB_MSG_342
  eng "%s"

ER_IB_MSG_343
  eng "%s"

ER_IB_MSG_344
  eng "%s"

ER_IB_MSG_345
  eng "%s"

ER_IB_MSG_346
  eng "%s"

ER_IB_MSG_347
  eng "%s"

ER_IB_MSG_348
  eng "%s"

ER_IB_MSG_349
  eng "%s"

ER_IB_MSG_350
  eng "%s"

OBSOLETE_ER_IB_MSG_351
  eng "%s"

ER_IB_MSG_UNPROTECTED_LOCATION_ALLOWED
  eng "The datafile '%s' for tablespace %s is in an unprotected location. This file cannot be recovered after a crash until this location is added to innodb_directories."

OBSOLETE_ER_IB_MSG_353
  eng "%s"

ER_IB_MSG_354
  eng "%s"

ER_IB_MSG_355
  eng "%s"

ER_IB_MSG_356
  eng "%s"

ER_IB_MSG_357
  eng "%s"

ER_IB_MSG_358
  eng "%s"

ER_IB_MSG_359
  eng "%s"

ER_IB_MSG_360
  eng "%s"

ER_IB_MSG_361
  eng "%s"

ER_IB_MSG_362
  eng "%s"

OBSOLETE_ER_IB_MSG_363
  eng "%s"

ER_IB_MSG_364
  eng "%s"

ER_IB_MSG_365
  eng "%s"

ER_IB_MSG_IGNORE_SCAN_PATH
  eng "Scan path '%s' is ignored because %s"

ER_IB_MSG_367
  eng "%s"

ER_IB_MSG_368
  eng "%s"

ER_IB_MSG_369
  eng "%s"

ER_IB_MSG_370
  eng "%s"

ER_IB_MSG_371
  eng "%s"

ER_IB_MSG_372
  eng "%s"

ER_IB_MSG_373
  eng "%s"

ER_IB_MSG_374
  eng "%s"

ER_IB_MSG_375
  eng "%s"

ER_IB_MSG_376
  eng "%s"

ER_IB_MSG_377
  eng "%s"

ER_IB_MSG_378
  eng "%s"

ER_IB_MSG_379
  eng "%s"

ER_IB_MSG_380
  eng "%s"

ER_IB_MSG_381
  eng "%s"

ER_IB_MSG_382
  eng "%s"

ER_IB_MSG_383
  eng "%s"

ER_IB_MSG_384
  eng "%s"

ER_IB_MSG_385
  eng "%s"

ER_IB_MSG_386
  eng "%s"

ER_IB_MSG_387
  eng "%s"

ER_IB_MSG_GENERAL_TABLESPACE_UNDER_DATADIR
  eng "A general tablespace cannot be located under the datadir. Cannot open file '%s'."

ER_IB_MSG_IMPLICIT_TABLESPACE_IN_DATADIR
  eng "A file-per-table tablespace cannot be located in the datadir. Cannot open file '%s'."

ER_IB_MSG_390
  eng "%s"

ER_IB_MSG_391
  eng "%s"

ER_IB_MSG_392
  eng "%s"

ER_IB_MSG_393
  eng "%s"

ER_IB_MSG_394
  eng "%s"

ER_IB_MSG_395
  eng "%s"

ER_IB_MSG_396
  eng "%s"

ER_IB_MSG_397
  eng "%s"

ER_IB_MSG_398
  eng "%s"

ER_IB_MSG_399
  eng "%s"

OBSOLETE_ER_IB_MSG_400
  eng "%s"

ER_IB_MSG_401
  eng "%s"

ER_IB_MSG_402
  eng "%s"

ER_IB_MSG_403
  eng "%s"

ER_IB_MSG_404
  eng "%s"

ER_IB_MSG_405
  eng "%s"

ER_IB_MSG_406
  eng "%s"

ER_IB_MSG_407
  eng "%s"

ER_IB_MSG_408
  eng "%s"

ER_IB_MSG_409
  eng "%s"

ER_IB_MSG_410
  eng "%s"

ER_IB_MSG_411
  eng "%s"

ER_IB_MSG_412
  eng "%s"

ER_IB_MSG_413
  eng "%s"

ER_IB_MSG_414
  eng "%s"

ER_IB_MSG_415
  eng "%s"

ER_IB_MSG_416
  eng "%s"

ER_IB_MSG_417
  eng "%s"

ER_IB_MSG_418
  eng "%s"

ER_IB_MSG_419
  eng "%s"

ER_IB_MSG_420
  eng "%s"

ER_IB_MSG_421
  eng "%s"

ER_IB_MSG_422
  eng "%s"

ER_IB_MSG_423
  eng "%s"

ER_IB_MSG_424
  eng "%s"

ER_IB_MSG_425
  eng "%s"

ER_IB_MSG_426
  eng "%s"

ER_IB_MSG_427
  eng "%s"

ER_IB_MSG_428
  eng "%s"

ER_IB_MSG_429
  eng "%s"

ER_IB_MSG_430
  eng "%s"

ER_IB_MSG_431
  eng "%s"

ER_IB_MSG_432
  eng "%s"

ER_IB_MSG_433
  eng "%s"

ER_IB_MSG_434
  eng "%s"

ER_IB_MSG_435
  eng "%s"

ER_IB_MSG_436
  eng "%s"

ER_IB_MSG_437
  eng "%s"

ER_IB_MSG_438
  eng "%s"

ER_IB_MSG_439
  eng "%s"

ER_IB_MSG_440
  eng "%s"

ER_IB_MSG_441
  eng "%s"

ER_IB_MSG_442
  eng "%s"

ER_IB_MSG_443
  eng "%s"

OBSOLETE_ER_IB_MSG_444
  eng "%s"

ER_IB_MSG_445
  eng "%s"

ER_IB_MSG_446
  eng "%s"

ER_IB_MSG_447
  eng "%s"

ER_IB_MSG_448
  eng "%s"

ER_IB_MSG_449
  eng "%s"

ER_IB_MSG_450
  eng "%s"

ER_IB_MSG_451
  eng "%s"

ER_IB_MSG_452
  eng "%s"

ER_IB_MSG_453
  eng "%s"

ER_IB_MSG_454
  eng "%s"

ER_IB_MSG_455
  eng "%s"

ER_IB_MSG_456
  eng "%s"

ER_IB_MSG_457
  eng "%s"

ER_IB_MSG_458
  eng "%s"

ER_IB_MSG_459
  eng "%s"

ER_IB_MSG_460
  eng "%s"

ER_IB_MSG_461
  eng "%s"

ER_IB_MSG_462
  eng "%s"

ER_IB_MSG_463
  eng "%s"

ER_IB_MSG_464
  eng "%s"

ER_IB_MSG_465
  eng "%s"

ER_IB_MSG_466
  eng "%s"

ER_IB_MSG_467
  eng "%s"

ER_IB_MSG_468
  eng "%s"

ER_IB_MSG_469
  eng "%s"

ER_IB_MSG_470
  eng "%s"

ER_IB_MSG_471
  eng "%s"

ER_IB_MSG_472
  eng "%s"

ER_IB_MSG_473
  eng "%s"

ER_IB_MSG_474
  eng "%s"

ER_IB_MSG_475
  eng "%s"

ER_IB_MSG_476
  eng "%s"

ER_IB_MSG_477
  eng "%s"

ER_IB_MSG_478
  eng "%s"

ER_IB_MSG_479
  eng "%s"

ER_IB_MSG_480
  eng "%s"

ER_IB_MSG_481
  eng "%s"

ER_IB_MSG_482
  eng "%s"

ER_IB_MSG_483
  eng "%s"

ER_IB_MSG_484
  eng "%s"

ER_IB_MSG_485
  eng "%s"

ER_IB_MSG_486
  eng "%s"

ER_IB_MSG_487
  eng "%s"

ER_IB_MSG_488
  eng "%s"

ER_IB_MSG_489
  eng "%s"

ER_IB_MSG_490
  eng "%s"

ER_IB_MSG_491
  eng "%s"

ER_IB_MSG_492
  eng "%s"

ER_IB_MSG_493
  eng "%s"

ER_IB_MSG_494
  eng "%s"

ER_IB_MSG_495
  eng "%s"

ER_IB_MSG_496
  eng "%s"

ER_IB_MSG_497
  eng "%s"

ER_IB_MSG_498
  eng "%s"

ER_IB_MSG_499
  eng "%s"

ER_IB_MSG_500
  eng "%s"

ER_IB_MSG_501
  eng "%s"

ER_IB_MSG_502
  eng "%s"

ER_IB_MSG_503
  eng "%s"

ER_IB_MSG_504
  eng "%s"

ER_IB_MSG_505
  eng "%s"

ER_IB_MSG_506
  eng "%s"

ER_IB_MSG_507
  eng "%s"

ER_IB_MSG_508
  eng "%s"

ER_IB_MSG_509
  eng "%s"

ER_IB_MSG_510
  eng "%s"

ER_IB_MSG_511
  eng "%s"

ER_IB_MSG_512
  eng "%s"

ER_IB_MSG_513
  eng "%s"

ER_IB_MSG_514
  eng "%s"

ER_IB_MSG_515
  eng "%s"

ER_IB_MSG_516
  eng "%s"

ER_IB_MSG_517
  eng "%s"

ER_IB_MSG_518
  eng "%s"

ER_IB_MSG_519
  eng "%s"

ER_IB_MSG_520
  eng "%s"

ER_IB_MSG_521
  eng "%s"

ER_IB_MSG_522
  eng "%s"

ER_IB_MSG_523
  eng "%s"

ER_IB_MSG_524
  eng "%s"

ER_IB_MSG_525
  eng "%s"

ER_IB_MSG_526
  eng "%s"

ER_IB_MSG_527
  eng "%s"

OBSOLETE_ER_IB_MSG_528
  eng "%s"

OBSOLETE_ER_IB_MSG_529
  eng "%s"

ER_IB_MSG_530
  eng "%s"

ER_IB_MSG_531
  eng "%s"

ER_IB_MSG_532
  eng "%s"

ER_IB_MSG_533
  eng "%s"

ER_IB_MSG_534
  eng "%s"

OBSOLETE_ER_IB_MSG_535
  eng "%s"

OBSOLETE_ER_IB_MSG_536
  eng "%s"

ER_IB_MSG_537
  eng "%s"

ER_IB_MSG_538
  eng "%s"

ER_IB_MSG_539
  eng "%s"

ER_IB_MSG_540
  eng "%s"

ER_IB_MSG_541
  eng "%s"

ER_IB_MSG_542
  eng "%s"

ER_IB_MSG_543
  eng "%s"

ER_IB_MSG_544
  eng "%s"

ER_IB_MSG_545
  eng "%s"

ER_IB_MSG_546
  eng "%s"

ER_IB_MSG_547
  eng "%s"

ER_IB_MSG_548
  eng "%s"

ER_IB_MSG_549
  eng "%s"

ER_IB_MSG_550
  eng "%s"

ER_IB_MSG_551
  eng "%s"

ER_IB_MSG_552
  eng "%s"

ER_IB_MSG_553
  eng "%s"

ER_IB_MSG_554
  eng "%s"

ER_IB_MSG_555
  eng "%s"

ER_IB_MSG_556
  eng "%s"

ER_IB_MSG_557
  eng "%s"

ER_IB_MSG_558
  eng "%s"

ER_IB_MSG_559
  eng "%s"

ER_IB_MSG_560
  eng "%s"

ER_IB_MSG_561
  eng "%s"

ER_IB_MSG_562
  eng "%s"

ER_IB_MSG_563
  eng "%s"

ER_IB_MSG_564
  eng "%s"

ER_IB_MSG_INVALID_LOCATION_FOR_TABLE
  eng "Cannot create a tablespace for table %s because the directory is not a valid location. %s"

ER_IB_MSG_566
  eng "%s"

ER_IB_MSG_567
  eng "%s"

ER_IB_MSG_568
  eng "%s"

ER_IB_MSG_569
  eng "%s"

ER_IB_MSG_570
  eng "%s"

ER_IB_MSG_571
  eng "%s"

OBSOLETE_ER_IB_MSG_572
  eng "%s"

ER_IB_MSG_573
  eng "%s"

ER_IB_MSG_574
  eng "%s"

OBSOLETE_ER_IB_MSG_575
  eng "%s"

OBSOLETE_ER_IB_MSG_576
  eng "%s"

OBSOLETE_ER_IB_MSG_577
  eng "%s"

ER_IB_MSG_578
  eng "%s"

ER_IB_MSG_579
  eng "%s"

ER_IB_MSG_580
  eng "%s"

ER_IB_MSG_581
  eng "%s"

ER_IB_MSG_582
  eng "%s"

ER_IB_MSG_583
  eng "%s"

ER_IB_MSG_584
  eng "%s"

ER_IB_MSG_585
  eng "%s"

ER_IB_MSG_586
  eng "%s"

ER_IB_MSG_587
  eng "%s"

ER_IB_MSG_588
  eng "%s"

ER_IB_MSG_589
  eng "%s"

ER_IB_MSG_590
  eng "%s"

ER_IB_MSG_591
  eng "%s"

ER_IB_MSG_592
  eng "%s"

ER_IB_MSG_593
  eng "%s"

ER_IB_MSG_594
  eng "%s"

ER_IB_MSG_595
  eng "%s"

ER_IB_MSG_596
  eng "%s"

ER_IB_MSG_597
  eng "%s"

ER_IB_MSG_598
  eng "%s"

ER_IB_MSG_599
  eng "%s"

ER_IB_MSG_600
  eng "%s"

ER_IB_MSG_601
  eng "%s"

ER_IB_MSG_602
  eng "%s"

ER_IB_MSG_603
  eng "%s"

ER_IB_MSG_604
  eng "%s"

ER_IB_MSG_605
  eng "%s"

ER_IB_MSG_606
  eng "%s"

ER_IB_MSG_607
  eng "%s"

ER_IB_MSG_608
  eng "%s"

ER_IB_MSG_609
  eng "%s"

ER_IB_MSG_610
  eng "%s"

ER_IB_MSG_611
  eng "%s"

ER_IB_MSG_612
  eng "%s"

ER_IB_MSG_613
  eng "%s"

ER_IB_MSG_614
  eng "%s"

ER_IB_MSG_615
  eng "%s"

ER_IB_MSG_616
  eng "%s"

ER_IB_MSG_617
  eng "%s"

ER_IB_MSG_618
  eng "%s"

ER_IB_MSG_619
  eng "%s"

ER_IB_MSG_620
  eng "%s"

ER_IB_MSG_621
  eng "%s"

ER_IB_MSG_622
  eng "%s"

ER_IB_MSG_623
  eng "%s"

ER_IB_MSG_624
  eng "%s"

ER_IB_MSG_625
  eng "%s"

ER_IB_MSG_626
  eng "%s"

ER_IB_MSG_627
  eng "%s"

ER_IB_MSG_628
  eng "%s"

ER_IB_MSG_629
  eng "%s"

ER_IB_MSG_630
  eng "%s"

ER_IB_MSG_631
  eng "%s"

ER_IB_MSG_632
  eng "%s"

ER_IB_MSG_633
  eng "%s"

ER_IB_MSG_634
  eng "%s"

ER_IB_MSG_635
  eng "%s"

ER_IB_MSG_636
  eng "Blocked High Priority Transaction (ID %llu, Thread ID %s) forces rollback of the blocking transaction (ID %llu - %s)."

ER_IB_MSG_637
  eng "%s"

ER_IB_MSG_638
  eng "%s"

ER_IB_MSG_639
  eng "Blocked High Priority Transaction (Thread ID %s) waking up the blocking transaction (ID %llu) by pretending it's a deadlock victim."

OBSOLETE_ER_IB_MSG_640
  eng "%s"

OBSOLETE_ER_IB_MSG_641
  eng "%s"

ER_IB_MSG_642
  eng "%s"

ER_IB_MSG_643
  eng "%s"

ER_IB_MSG_644
  eng "%s"

ER_IB_MSG_645
  eng "%s"

ER_IB_MSG_646
  eng "%s"

ER_IB_MSG_647
  eng "%s"

ER_IB_MSG_648
  eng "%s"

ER_IB_MSG_649
  eng "%s"

ER_IB_MSG_650
  eng "%s"

ER_IB_MSG_651
  eng "%s"

ER_IB_MSG_652
  eng "%s"

ER_IB_MSG_DDL_LOG_DELETE_BY_ID_OK
  eng "%s"

ER_IB_MSG_654
  eng "%s"

ER_IB_MSG_655
  eng "%s"

ER_IB_MSG_656
  eng "%s"

ER_IB_MSG_657
  eng "%s"

ER_IB_MSG_658
  eng "%s"

ER_IB_MSG_659
  eng "%s"

ER_IB_MSG_660
  eng "%s"

ER_IB_MSG_661
  eng "%s"

ER_IB_MSG_662
  eng "%s"

ER_IB_MSG_663
  eng "%s"

OBSOLETE_ER_IB_MSG_664
  eng "The transaction log size is too large for innodb_log_buffer_size (%lu >= %lu / 2). Trying to extend it."

OBSOLETE_ER_IB_MSG_665
  eng "innodb_log_buffer_size was extended to %lu bytes."

OBSOLETE_ER_IB_MSG_666
  eng "The transaction log files are too small for the single transaction log (size=%lu). So, the last checkpoint age might exceed the log group capacity %llu."

OBSOLETE_ER_IB_MSG_667
  eng "The age of the last checkpoint is %llu, which exceeds the log group capacity %llu."

OBSOLETE_ER_IB_MSG_668
  eng "Cannot continue operation. ib_logfiles are too small for innodb_thread_concurrency %lu. The combined size of ib_logfiles should be bigger than 200 kB * innodb_thread_concurrency. To get mysqld to start up, set innodb_thread_concurrency in my.cnf to a lower value, for example, to 8. After an ERROR-FREE shutdown of mysqld you can adjust the size of ib_logfiles. %s"

OBSOLETE_ER_IB_MSG_669
  eng "Redo log was encrypted, but keyring plugin is not loaded."

OBSOLETE_ER_IB_MSG_670
  eng "Read redo log encryption metadata successful."

OBSOLETE_ER_IB_MSG_671
  eng "Can't set redo log tablespace encryption metadata."

OBSOLETE_ER_IB_MSG_672
  eng "Cannot read the encryption information in log file header, please check if keyring plugin loaded and the key file exists."

OBSOLETE_ER_IB_MSG_673
  eng "Can't set redo log tablespace to be encrypted in read-only mode."

OBSOLETE_ER_IB_MSG_674
  eng "Can't set redo log tablespace to be encrypted."

OBSOLETE_ER_IB_MSG_675
  eng "Can't set redo log tablespace to be encrypted."

OBSOLETE_ER_IB_MSG_676
  eng "Redo log encryption is enabled."

OBSOLETE_ER_IB_MSG_677
  eng "Flush waiting for archiver to catch up lag LSN: %llu"

OBSOLETE_ER_IB_MSG_678
  eng "Flush overwriting data to archive - wait too long (1 minute) lag LSN: %llu"

OBSOLETE_ER_IB_MSG_679
  eng "%s"

OBSOLETE_ER_IB_MSG_680
  eng "Starting shutdown..."

OBSOLETE_ER_IB_MSG_681
  eng "Waiting for %s to exit"

OBSOLETE_ER_IB_MSG_682
  eng "Waiting for %lu active transactions to finish"

OBSOLETE_ER_IB_MSG_683
  eng "Waiting for master thread to be suspended"

OBSOLETE_ER_IB_MSG_684
  eng "Waiting for page_cleaner to finish flushing of buffer pool"

OBSOLETE_ER_IB_MSG_685
  eng "Pending checkpoint_writes: %lu. Pending log flush writes: %lu."

OBSOLETE_ER_IB_MSG_686
  eng "Waiting for %lu buffer page I/Os to complete"

OBSOLETE_ER_IB_MSG_687
  eng "MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!"

OBSOLETE_ER_IB_MSG_688
  eng "Background thread %s woke up during shutdown"

OBSOLETE_ER_IB_MSG_689
  eng "Waiting for archiver to finish archiving page and log"

OBSOLETE_ER_IB_MSG_690
  eng "Background thread %s woke up during shutdown"

OBSOLETE_ER_IB_MSG_691
  eng "Waiting for dirty buffer pages to be flushed"

OBSOLETE_ER_IB_MSG_692
  eng "Log sequence number at shutdown %llu is lower than at startup %llu!"

OBSOLETE_ER_IB_MSG_693
  eng "Waiting for archiver to finish archiving page and log"

ER_IB_MSG_694
  eng "############### CORRUPT LOG RECORD FOUND ###############"

ER_IB_MSG_695
  eng "Log record type %d, page %lu:%lu. Log parsing proceeded successfully up to %llu. Previous log record type %d, is multi %llu Recv offset %zd, prev %llu"

ER_IB_MSG_696
  eng "Hex dump starting %llu bytes before and ending %llu bytes after the corrupted record:"

ER_IB_MSG_697
  eng "Set innodb_force_recovery to ignore this error."

ER_IB_MSG_LOG_CORRUPT
  eng "The redo log file may have been corrupt and it is possible that the log scan did not proceed far enough in recovery! Please run CHECK TABLE on your InnoDB tables to check that they are ok! If mysqld crashes after this recovery; %s"

ER_IB_MSG_699
  eng "%llu pages with log records were left unprocessed!"

ER_IB_MSG_LOG_FORMAT_OLD_AND_LOG_CORRUPTED
  eng "Upgrade after a crash is not supported. This redo log was created with %s, and it appears corrupted. Please follow the instructions at %s"

ER_IB_MSG_LOG_FORMAT_OLD_AND_NO_CLEAN_SHUTDOWN
  eng "Upgrade is not supported after a crash or shutdown with innodb_fast_shutdown = 2. This redo log was created with %s, and it appears logically non empty. Please follow the instructions at %s"

OBSOLETE_ER_IB_MSG_702
  eng "%s"

OBSOLETE_ER_IB_MSG_703
  eng "%s"

ER_IB_MSG_LOG_FORMAT_BEFORE_8_0_30
  eng "Redo log format is v%lu. The redo log was created before MySQL 8.0.30."

ER_IB_MSG_LOG_FILE_FORMAT_UNKNOWN
  eng "Unknown redo log format (v%lu) in file %s. Please follow the instructions at %s"

ER_IB_MSG_RECOVERY_CHECKPOINT_NOT_FOUND
  eng "No valid checkpoint found (corrupted redo log). You can try --innodb-force-recovery=6 as a last resort."

ER_IB_MSG_707
  eng "Applying a batch of %llu redo log records ..."

ER_IB_MSG_708
  eng "%s"

ER_IB_MSG_709
  eng "%s"

ER_IB_MSG_710
  eng "Apply batch completed!"

ER_IB_MSG_711
  eng "%s"

ER_IB_MSG_712
  eng "%s"

ER_IB_MSG_713
  eng "%s"

ER_IB_MSG_714
  eng "%s"

ER_IB_MSG_715
  eng "%s"

ER_IB_MSG_716
  eng "%s"

ER_IB_MSG_717
  eng "An optimized(without redo logging) DDL operation has been performed. All modified pages may not have been flushed to the disk yet.\nThis offline backup may not be consistent"

ER_IB_MSG_718
  eng "Extending tablespace : %lu space name: %s to new size: %lu pages during recovery."

ER_IB_MSG_719
  eng "Could not extend tablespace: %lu space name: %s to new size: %lu pages during recovery."

ER_IB_MSG_720
  eng "Log block %lu at lsn %llu has valid header, but checksum field contains %lu, should be %lu."

ER_IB_MSG_RECOVERY_SKIPPED_IN_READ_ONLY_MODE
  eng "Recovery skipped, --innodb-read-only set!"

ER_IB_MSG_722
  eng "Log scan progressed past the checkpoint LSN %llu."

ER_IB_MSG_723
  eng "Log parsing buffer overflow. Recovery may have failed! Please set log_buffer_size to a value higher than %lu."

ER_IB_MSG_724
  eng "Set innodb_force_recovery to ignore this error.";

ER_IB_MSG_725
  eng "Doing recovery: scanned up to log sequence number %llu"

ER_IB_MSG_726
  eng "Database was not shutdown normally!"

ER_IB_MSG_727
  eng "Starting crash recovery."

ER_IB_MSG_728
  eng "The user has set SRV_FORCE_NO_LOG_REDO on, skipping log redo"

ER_IB_MSG_LOG_FILES_CREATED_BY_MEB_AND_READ_ONLY_MODE
  eng "Cannot restore from mysqlbackup, InnoDB running in read-only mode!"

ER_IB_MSG_LOG_FILES_CREATED_BY_MEB
  eng "The redo log file was created by mysqlbackup --apply-log at %s. The following crash recovery is part of a normal restore."

ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE
  eng "Opening cloned database"

ER_IB_MSG_LOG_FORMAT_OLD
  eng "Redo log is from an earlier version, v%lu."

OBSOLETE_ER_IB_MSG_LOG_FORMAT_NOT_SUPPORTED
  eng "Redo log format v%lu not supported. Current supported format is v%lu."

ER_IB_MSG_RECOVERY_CHECKPOINT_FROM_BEFORE_CLEAN_SHUTDOWN
  eng "Are you sure you are using the right redo log files to start up the database? Log sequence number in the redo log files is %llu, less than the log sequence number in the first system tablespace file header, %llu."

ER_IB_MSG_RECOVERY_IS_NEEDED
  eng "The log sequence number %llu in the system tablespace does not match the log sequence number %llu in the redo log files!"

ER_IB_MSG_RECOVERY_IN_READ_ONLY
  eng "Can't initiate database recovery, running in read-only-mode."

ER_IB_MSG_737
  eng "We scanned the log up to %llu. A checkpoint was at %llu and the maximum LSN on a database page was %llu. It is possible that the database is now corrupt!"

ER_IB_MSG_738
  eng "Waiting for recv_writer to finish flushing of buffer pool"

ER_IB_MSG_739
  eng "Recovery parsing buffer extended to %zu."

ER_IB_MSG_740
  eng "Out of memory while resizing recovery parsing buffer."

ER_IB_MSG_741
  eng "%s"

ER_IB_MSG_742
  eng "%s"

ER_IB_MSG_743
  eng "%s"

ER_IB_MSG_744
  eng "%s"

ER_IB_MSG_745
  eng "%s"

ER_IB_MSG_746
  eng "%s"

ER_IB_MSG_747
  eng "%s"

ER_IB_MSG_748
  eng "%s"

ER_IB_MSG_749
  eng "%s"

ER_IB_MSG_750
  eng "%s"

ER_IB_MSG_751
  eng "%s"

ER_IB_MSG_752
  eng "%s"

ER_IB_MSG_753
  eng "%s"

ER_IB_MSG_754
  eng "%s"

ER_IB_MSG_755
  eng "%s"

ER_IB_MSG_756
  eng "%s"

ER_IB_MSG_757
  eng "%s"

ER_IB_MSG_758
  eng "%s"

ER_IB_MSG_759
  eng "%s"

ER_IB_MSG_760
  eng "%s"

ER_IB_MSG_761
  eng "%s"

ER_IB_MSG_762
  eng "%s"

ER_IB_MSG_763
  eng "%s"

ER_IB_MSG_764
  eng "%s"

ER_IB_MSG_765
  eng "%s"

ER_IB_MSG_766
  eng "%s"

ER_IB_MSG_767
  eng "%s"

ER_IB_MSG_768
  eng "%s"

ER_IB_MSG_769
  eng "%s"

ER_IB_MSG_770
  eng "%s"

ER_IB_MSG_771
  eng "%s"

ER_IB_MSG_772
  eng "%s"

ER_IB_MSG_773
  eng "%s"

ER_IB_MSG_774
  eng "%s"

ER_IB_MSG_775
  eng "%s"

ER_IB_MSG_776
  eng "%s"

ER_IB_MSG_777
  eng "%s"

ER_IB_MSG_778
  eng "%s"

ER_IB_MSG_779
  eng "%s"

ER_IB_MSG_780
  eng "%s"

ER_IB_MSG_781
  eng "%s"

ER_IB_MSG_782
  eng "%s"

ER_IB_MSG_783
  eng "%s"

ER_IB_MSG_784
  eng "%s"

ER_IB_MSG_785
  eng "%s"

ER_IB_MSG_786
  eng "%s"

ER_IB_MSG_787
  eng "%s"

ER_IB_MSG_788
  eng "%s"

ER_IB_MSG_789
  eng "%s"

ER_IB_MSG_790
  eng "%s"

ER_IB_MSG_791
  eng "%s"

ER_IB_MSG_792
  eng "%s"

ER_IB_MSG_793
  eng "%s"

ER_IB_MSG_794
  eng "%s"

ER_IB_MSG_795
  eng "%s"

ER_IB_MSG_796
  eng "%s"

ER_IB_MSG_797
  eng "%s"

ER_IB_MSG_798
  eng "%s"

ER_IB_MSG_799
  eng "%s"

OBSOLETE_ER_IB_MSG_800
  eng "%s"

ER_IB_MSG_801
  eng "%s"

ER_IB_MSG_802
  eng "%s"

ER_IB_MSG_803
  eng "%s"

ER_IB_MSG_804
  eng "%s"

ER_IB_MSG_805
  eng "%s"

ER_IB_MSG_806
  eng "%s"

ER_IB_MSG_807
  eng "%s"

ER_IB_MSG_808
  eng "%s"

ER_IB_MSG_809
  eng "%s"

ER_IB_MSG_810
  eng "%s"

ER_IB_MSG_811
  eng "%s"

ER_IB_MSG_812
  eng "%s"

ER_IB_MSG_813
  eng "%s"

ER_IB_MSG_814
  eng "%s"

ER_IB_MSG_815
  eng "%s"

ER_IB_MSG_816
  eng "%s"

ER_IB_MSG_817
  eng "%s"

ER_IB_MSG_818
  eng "%s"

ER_IB_MSG_819
  eng "%s"

ER_IB_MSG_820
  eng "%s"

ER_IB_MSG_821
  eng "%s"

ER_IB_MSG_822
  eng "%s"

ER_IB_MSG_823
  eng "%s"

ER_IB_MSG_824
  eng "%s"

ER_IB_MSG_825
  eng "%s"

ER_IB_MSG_826
  eng "%s"

ER_IB_MSG_827
  eng "%s"

ER_IB_MSG_828
  eng "%s"

ER_IB_MSG_829
  eng "%s"

ER_IB_MSG_830
  eng "%s"

ER_IB_MSG_831
  eng "%s"

ER_IB_MSG_832
  eng "%s"

ER_IB_MSG_833
  eng "%s"

ER_IB_MSG_834
  eng "%s"

ER_IB_MSG_835
  eng "%s"

ER_IB_MSG_836
  eng "%s"

ER_IB_MSG_837
  eng "%s"

ER_IB_MSG_838
  eng "%s"

ER_IB_MSG_839
  eng "%s"

ER_IB_MSG_840
  eng "%s"

ER_IB_MSG_841
  eng "%s"

ER_IB_MSG_842
  eng "%s"

ER_IB_MSG_CANT_ENCRYPT_REDO_LOG_DATA
  eng "Can't encrypt data of redo log"

ER_IB_MSG_844
  eng "%s"

ER_IB_MSG_845
  eng "%s"

ER_IB_MSG_CANT_DECRYPT_REDO_LOG
  eng "Decryption of redo log block at offset %llu in file %s failed because there's no keyring configured"

ER_IB_MSG_847
  eng "%s"

ER_IB_MSG_848
  eng "%s"

ER_IB_MSG_849
  eng "%s"

ER_IB_MSG_850
  eng "%s"

ER_IB_MSG_851
  eng "%s"

ER_IB_MSG_852
  eng "%s"

ER_IB_MSG_853
  eng "%s"

ER_IB_MSG_854
  eng "%s"

ER_IB_MSG_855
  eng "%s"

ER_IB_MSG_856
  eng "%s"

ER_IB_MSG_857
  eng "%s"

ER_IB_MSG_858
  eng "%s"

ER_IB_MSG_859
  eng "%s"

ER_IB_MSG_860
  eng "%s"

ER_IB_MSG_861
  eng "%s"

ER_IB_MSG_862
  eng "%s"

ER_IB_MSG_863
  eng "%s"

ER_IB_MSG_864
  eng "%s"

ER_IB_MSG_865
  eng "%s"

ER_IB_MSG_866
  eng "%s"

ER_IB_MSG_867
  eng "%s"

ER_IB_MSG_868
  eng "%s"

ER_IB_MSG_869
  eng "%s"

ER_IB_MSG_870
  eng "%s"

ER_IB_MSG_871
  eng "%s"

ER_IB_MSG_872
  eng "%s"

ER_IB_MSG_873
  eng "%s"

ER_IB_MSG_874
  eng "%s"

ER_IB_MSG_875
  eng "%s"

ER_IB_MSG_876
  eng "%s"

ER_IB_MSG_877
  eng "%s"

ER_IB_MSG_878
  eng "%s"

ER_IB_MSG_879
  eng "%s"

ER_IB_MSG_880
  eng "%s"

ER_IB_MSG_881
  eng "%s"

ER_IB_MSG_882
  eng "%s"

ER_IB_MSG_883
  eng "%s"

ER_IB_MSG_884
  eng "%s"

ER_IB_MSG_885
  eng "%s"

ER_IB_MSG_886
  eng "%s"

ER_IB_MSG_887
  eng "%s"

ER_IB_MSG_888
  eng "%s"

ER_IB_MSG_889
  eng "%s"

ER_IB_MSG_890
  eng "%s"

ER_IB_MSG_891
  eng "%s"

ER_IB_MSG_892
  eng "%s"

ER_IB_MSG_893
  eng "%s"

ER_IB_MSG_894
  eng "%s"

ER_IB_MSG_895
  eng "%s"

ER_IB_MSG_896
  eng "%s"

ER_IB_MSG_897
  eng "%s"

ER_IB_MSG_898
  eng "%s"

ER_IB_MSG_899
  eng "%s"

ER_IB_MSG_900
  eng "%s"

ER_IB_MSG_901
  eng "%s"

ER_IB_MSG_902
  eng "%s"

ER_IB_MSG_903
  eng "%s"

ER_IB_MSG_904
  eng "%s"

ER_IB_MSG_905
  eng "%s"

ER_IB_MSG_906
  eng "%s"

ER_IB_MSG_907
  eng "%s"

ER_IB_MSG_908
  eng "%s"

ER_IB_MSG_909
  eng "%s"

ER_IB_MSG_910
  eng "%s"

ER_IB_MSG_911
  eng "%s"

ER_IB_MSG_912
  eng "%s"

ER_IB_MSG_913
  eng "%s"

ER_IB_MSG_914
  eng "%s"

ER_IB_MSG_915
  eng "%s"

ER_IB_MSG_916
  eng "%s"

ER_IB_MSG_917
  eng "%s"

ER_IB_MSG_918
  eng "%s"

ER_IB_MSG_919
  eng "%s"

ER_IB_MSG_920
  eng "%s"

ER_IB_MSG_921
  eng "%s"

ER_IB_MSG_922
  eng "%s"

ER_IB_MSG_923
  eng "%s"

ER_IB_MSG_924
  eng "%s"

ER_IB_MSG_925
  eng "%s"

ER_IB_MSG_926
  eng "%s"

ER_IB_MSG_927
  eng "%s"

ER_IB_MSG_928
  eng "%s"

ER_IB_MSG_929
  eng "%s"

ER_IB_MSG_930
  eng "%s"

ER_IB_MSG_931
  eng "%s"

ER_IB_MSG_932
  eng "%s"

ER_IB_MSG_933
  eng "%s"

ER_IB_MSG_934
  eng "%s"

ER_IB_MSG_935
  eng "%s"

ER_IB_MSG_936
  eng "%s"

ER_IB_MSG_937
  eng "%s"

ER_IB_MSG_938
  eng "%s"

ER_IB_MSG_939
  eng "%s"

ER_IB_MSG_940
  eng "%s"

ER_IB_MSG_941
  eng "%s"

ER_IB_MSG_942
  eng "%s"

ER_IB_MSG_943
  eng "%s"

ER_IB_MSG_944
  eng "%s"

ER_IB_MSG_945
  eng "%s"

ER_IB_MSG_946
  eng "%s"

ER_IB_MSG_947
  eng "%s"

ER_IB_MSG_948
  eng "%s"

ER_IB_MSG_949
  eng "%s"

ER_IB_MSG_950
  eng "%s"

ER_IB_MSG_951
  eng "%s"

ER_IB_MSG_952
  eng "%s"

ER_IB_MSG_953
  eng "%s"

ER_IB_MSG_954
  eng "%s"

ER_IB_MSG_955
  eng "%s"

ER_IB_MSG_956
  eng "%s"

ER_IB_MSG_957
  eng "%s"

ER_IB_MSG_958
  eng "%s"

ER_IB_MSG_959
  eng "%s"

ER_IB_MSG_960
  eng "%s"

ER_IB_MSG_961
  eng "%s"

ER_IB_MSG_962
  eng "%s"

ER_IB_MSG_963
  eng "%s"

ER_IB_MSG_964
  eng "%s"

ER_IB_MSG_965
  eng "%s"

ER_IB_MSG_966
  eng "%s"

ER_IB_MSG_967
  eng "%s"

ER_IB_MSG_968
  eng "%s"

ER_IB_MSG_969
  eng "%s"

ER_IB_MSG_970
  eng "%s"

ER_IB_MSG_971
  eng "%s"

ER_IB_MSG_972
  eng "%s"

ER_IB_MSG_973
  eng "%s"

ER_IB_MSG_974
  eng "%s"

ER_IB_MSG_975
  eng "%s"

ER_IB_MSG_976
  eng "%s"

ER_IB_MSG_977
  eng "%s"

ER_IB_MSG_978
  eng "%s"

ER_IB_MSG_979
  eng "%s"

ER_IB_MSG_980
  eng "%s"

ER_IB_MSG_981
  eng "%s"

ER_IB_MSG_982
  eng "%s"

ER_IB_MSG_983
  eng "%s"

ER_IB_MSG_984
  eng "%s"

ER_IB_MSG_985
  eng "%s"

ER_IB_MSG_986
  eng "%s"

ER_IB_MSG_987
  eng "%s"

ER_IB_MSG_988
  eng "%s"

ER_IB_MSG_989
  eng "%s"

ER_IB_MSG_990
  eng "%s"

ER_IB_MSG_991
  eng "%s"

ER_IB_MSG_992
  eng "%s"

ER_IB_MSG_993
  eng "%s"

ER_IB_MSG_994
  eng "%s"

ER_IB_MSG_995
  eng "%s"

ER_IB_MSG_996
  eng "%s"

ER_IB_MSG_997
  eng "%s"

ER_IB_MSG_998
  eng "%s"

ER_IB_MSG_999
  eng "%s"

ER_IB_MSG_1000
  eng "%s"

ER_IB_MSG_1001
  eng "%s"

ER_IB_MSG_1002
  eng "%s"

ER_IB_MSG_1003
  eng "%s"

ER_IB_MSG_1004
  eng "%s"

ER_IB_MSG_1005
  eng "%s"

ER_IB_MSG_1006
  eng "%s"

ER_IB_MSG_1007
  eng "%s"

ER_IB_MSG_1008
  eng "%s"

ER_IB_MSG_1009
  eng "%s"

ER_IB_MSG_1010
  eng "%s"

ER_IB_MSG_1011
  eng "%s"

ER_IB_MSG_1012
  eng "%s"

ER_IB_MSG_1013
  eng "%s"

ER_IB_MSG_1014
  eng "%s"

ER_IB_MSG_1015
  eng "%s"

ER_IB_MSG_1016
  eng "%s"

ER_IB_MSG_1017
  eng "%s"

ER_IB_MSG_1018
  eng "%s"

ER_IB_MSG_1019
  eng "%s"

ER_IB_MSG_1020
  eng "%s"

ER_IB_MSG_1021
  eng "%s"

ER_IB_MSG_1022
  eng "%s"

ER_IB_MSG_1023
  eng "%s"

ER_IB_MSG_1024
  eng "%s"

ER_IB_MSG_1025
  eng "%s"

ER_IB_MSG_1026
  eng "%s"

ER_IB_MSG_1027
  eng "%s"

ER_IB_MSG_1028
  eng "%s"

ER_IB_MSG_1029
  eng "%s"

ER_IB_MSG_1030
  eng "%s"

ER_IB_MSG_1031
  eng "%s"

ER_IB_MSG_1032
  eng "%s"

ER_IB_MSG_1033
  eng "%s"

ER_IB_MSG_1034
  eng "%s"

ER_IB_MSG_1035
  eng "%s"

ER_IB_MSG_1036
  eng "%s"

ER_IB_MSG_1037
  eng "%s"

ER_IB_MSG_1038
  eng "%s"

ER_IB_MSG_1039
  eng "%s"

ER_IB_MSG_1040
  eng "%s"

ER_IB_MSG_1041
  eng "%s"

ER_IB_MSG_1042
  eng "%s"

ER_IB_MSG_1043
  eng "%s"

ER_IB_MSG_1044
  eng "%s"

ER_IB_MSG_1045
  eng "%s"

ER_IB_MSG_1046
  eng "Old log sequence number %llu was greater than the new log sequence number %llu. Please submit a bug report to http://bugs.mysql.com"

ER_IB_MSG_1047
  eng "Semaphore wait has lasted > %llu seconds. We intentionally crash the server because it appears to be hung."

ER_IB_MSG_1048
  eng "Waiting for %llu table(s) to be dropped"

ER_IB_MSG_1049
  eng "Waiting for change buffer merge to complete number of bytes of change buffer just merged: %llu"

OBSOLETE_ER_IB_MSG_1050
  eng "Can't set undo tablespace(s) to be encrypted since --innodb_undo_tablespaces=0."

ER_IB_MSG_1051
  eng "Can't set undo tablespace(s) to be encrypted in read-only-mode."

ER_IB_MSG_1052
  eng "Can't set undo tablespace '%s' to be encrypted."

ER_IB_MSG_1053
  eng "Can't set undo tablespace '%s' to be encrypted. Failed to write header page."

ER_IB_MSG_1054
  eng "Can't set undo tablespace '%s' to be encrypted. Error %d - %s"

ER_IB_MSG_1055
  eng "Encryption is enabled for undo tablespace '%s'."

ER_IB_MSG_1056
  eng "Can't rotate encryption on undo tablespace '%s'."

ER_IB_MSG_1057
  eng "Encryption is enabled for undo tablespace '%s'."

ER_IB_MSG_1058
  eng "os_file_get_status() failed on '%s'. Can't determine file permissions."

ER_IB_MSG_1059
  eng "%s can't be opened in %s mode."

ER_IB_MSG_1060
  eng "'%s' not a regular file."

ER_IB_MSG_LOG_FILE_OS_CREATE_FAILED
  eng "Cannot create %s"

ER_IB_MSG_FILE_RESIZE
  eng "Setting file %s size to %llu MB. Progress : %u%%"

ER_IB_MSG_LOG_FILE_RESIZE_FAILED
  eng "Cannot resize redo log file %s to %llu MB (%s)"

ER_IB_MSG_LOG_FILES_CREATE_AND_READ_ONLY_MODE
  eng "Cannot create redo log files in read-only mode (--innodb-read-only)."

ER_IB_MSG_1065
  eng "Redo log encryption is enabled, but the keyring is not loaded."

ER_IB_MSG_LOG_FILE_PREPARE_ON_CREATE_FAILED
  eng "Failed to create redo log file %s (error: %d) for start LSN %llu"

OBSOLETE_ER_IB_MSG_1067
  eng "Renaming log file %s to %s"

ER_IB_MSG_LOG_FILES_INITIALIZED
  eng "New redo log files created, LSN=%llu"

ER_IB_MSG_LOG_FILE_OPEN_FAILED
  eng "Unable to open '%s' (error: %d)."

ER_IB_MSG_1070
  eng "Cannot create construction log file '%s' for undo tablespace '%s'."

ER_IB_MSG_1071
  eng "Creating UNDO Tablespace %s"

ER_IB_MSG_1072
  eng "Setting file %s size to %llu MB"

ER_IB_MSG_1073
  eng "Physically writing the file full"

ER_IB_MSG_1074
  eng "Error in creating %s: probably out of disk space"

ER_IB_MSG_1075
  eng "Can't set encryption metadata for space %s"

ER_IB_MSG_1076
  eng "Cannot read first page of '%s' - %s"

ER_IB_MSG_1077
  eng "Undo tablespace number %lu was being truncated when mysqld quit."

ER_IB_MSG_1078
  eng "Cannot recover a truncated undo tablespace in read-only mode"

ER_IB_MSG_1079
  eng "Reconstructing undo tablespace number %lu."

ER_IB_MSG_1080
  eng "Cannot create %s because %s already uses Space ID=%lu! Did you change innodb_undo_directory?"

ER_IB_MSG_1081
  eng "UNDO tablespace %s must be %s"

ER_IB_MSG_1082
  eng "Error creating file for %s"

ER_IB_MSG_1083
  eng "Error reading encryption for %s"

ER_IB_MSG_CANNOT_OPEN_57_UNDO
  eng "Unable to open undo tablespace number %lu"

ER_IB_MSG_1085
  eng "Opened %llu existing undo tablespaces."

ER_IB_MSG_1086
  eng "Cannot create undo tablespaces since innodb_%s has been set. Using %llu existing undo tablespaces."

ER_IB_MSG_1087
  eng "Cannot continue InnoDB startup in %s mode because there are no existing undo tablespaces found."

ER_IB_MSG_1088
  eng "Could not create undo tablespace '%s'."

ER_IB_MSG_1089
  eng "Error %d - %s - opening newly created undo tablespace '%s'."

ER_IB_MSG_1090
  eng "Created %llu undo tablespaces."

ER_IB_MSG_1091
  eng "Unable to create encrypted undo tablespace number %lu. please check if the keyring is initialized correctly"

ER_IB_MSG_1092
  eng "Encryption is enabled for undo tablespace number %lu."

ER_IB_MSG_1093
  eng "Unable to initialize the header page in undo tablespace number %lu."

ER_IB_MSG_1094
  eng "Cannot delete old undo tablespaces because they contain undo logs for XA PREPARED transactions."

ER_IB_MSG_1095
  eng "Upgrading %zu existing undo tablespaces that were tracked in the system tablespace to %lu new independent undo tablespaces."

ER_IB_MSG_1096
  eng "Deleting %llu new independent undo tablespaces that we just created."

ER_IB_MSG_1097
  eng "Waiting for purge to start"

ER_IB_MSG_1098
  eng "Creating shared tablespace for temporary tables"

ER_IB_MSG_1099
  eng "The %s data file must be writable!"

ER_IB_MSG_1100
  eng "Could not create the shared %s."

ER_IB_MSG_1101
  eng "Unable to create the shared %s."

ER_IB_MSG_1102
  eng "The %s data file cannot be re-opened after check_file_spec() succeeded!"

ER_IB_MSG_1103
  eng "%d threads created by InnoDB had not exited at shutdown!"

ER_IB_MSG_1104
  eng "InnoDB Database creation was aborted %swith error %s. You may need to delete the ibdata1 file before trying to start up again."

ER_IB_MSG_1105
  eng "Plugin initialization aborted %swith error %s."

ER_IB_MSG_BUF_PENDING_IO
  eng "Waiting for %zu buffer page I/Os to complete."

ER_IB_MSG_1107
  eng "PUNCH HOLE support available"

ER_IB_MSG_1108
  eng "PUNCH HOLE support not available"

ER_IB_MSG_1109
  eng "Size of InnoDB's ulint is %zu but size of void* is %zu. The sizes should be the same so that on a 64-bit platforms you can allocate more than 4 GB of memory."

ER_IB_MSG_1110
  eng "Database upgrade cannot be accomplished in read-only mode."

ER_IB_MSG_1111
  eng "Database upgrade cannot be accomplished with innodb_force_recovery > 0"

ER_IB_MSG_1112
  eng "%s"

ER_IB_MSG_1113
  eng "%s"

ER_IB_MSG_1114
  eng "%s"

ER_IB_MSG_1115
  eng "%s"

ER_IB_MSG_1116
  eng "%s"

ER_IB_MSG_1117
  eng "%s"

OBSOLETE_ER_IB_MSG_1118
  eng "%s"

ER_IB_MSG_1119
  eng "%s"

ER_IB_MSG_1120
  eng "%s"

ER_IB_MSG_1121
  eng "%s"

ER_IB_MSG_1122
  eng "MySQL was built without a memory barrier capability on this architecture, which might allow a mutex/rw_lock violation under high thread concurrency. This may cause a hang."

ER_IB_MSG_1123
  eng "Compressed tables use zlib %s"

ER_IB_MSG_1124
  eng "%s"

ER_IB_MSG_1125
  eng "Startup called second time during the process lifetime. In the MySQL Embedded Server Library you cannot call server_init() more than once during the process lifetime."

ER_IB_MSG_1126
  eng "%s"

ER_IB_MSG_1127
  eng "Unable to create monitor file %s: %s"

ER_IB_MSG_1128
  eng "Disabling background ibuf IO read threads."

ER_IB_MSG_1129
  eng "Cannot initialize AIO sub-system"

ER_IB_MSG_1130
  eng "Initializing buffer pool, total size = %lf%c, instances = %lu, chunk size =%lf%c "

ER_IB_MSG_1131
  eng "Cannot allocate memory for the buffer pool"

ER_IB_MSG_1132
  eng "Completed initialization of buffer pool"

ER_IB_MSG_1133
  eng "Small buffer pool size (%lluM), the flst_validate() debug function can cause a deadlock if the buffer pool fills up."

ER_IB_MSG_1134
  eng "Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!"

ER_IB_MSG_DATA_DIRECTORY_NOT_INITIALIZED_OR_CORRUPTED
  eng "Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files."

ER_IB_MSG_LOG_FILES_INVALID_SET
  eng "Only one redo log file found"

ER_IB_MSG_LOG_FILE_SIZE_INVALID
  eng "The redo log file %s size %llu is not a multiple of innodb_page_size"

ER_IB_MSG_LOG_FILES_DIFFERENT_SIZES
  eng "The redo log file %s is of different size %llu bytes than other log files %llu bytes!"

ER_IB_MSG_1139
  eng "Use --innodb-directories to find the tablespace files. If that fails then use --innodb-force-recovery=1 to ignore this and to permanently lose all changes to the missing tablespace(s)"

ER_IB_MSG_RECOVERY_CORRUPT
  eng "The redo log file may have been corrupt and it is possible that the log scan or parsing did not proceed far enough in recovery. Please run CHECK TABLE on your InnoDB tables to check that they are ok! It may be safest to recover your InnoDB database from a backup!"

OBSOLETE_ER_IB_MSG_LOG_FILES_RESIZE_ON_START_IN_READ_ONLY_MODE
  eng "Cannot resize redo log files in read-only mode. Provide --innodb_redo_log_capacity >= %lluMB or start without --innodb-read-only."

ER_IB_MSG_1142
  eng "Cannot open DD tablespace."

ER_IB_MSG_LOG_FILES_REWRITING
  eng "Starting to delete and rewrite redo log files."

ER_IB_MSG_1144
  eng "Undo from 5.7 found. It will be purged"

ER_IB_MSG_1145
  eng "%s"

ER_IB_MSG_1146
  eng "%s"

ER_IB_MSG_1147
  eng "Tablespace size stored in header is %lu pages, but the sum of data file sizes is %lu pages"

ER_IB_MSG_1148
  eng "Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force a startup if you are trying to recover a badly corrupt database."

ER_IB_MSG_1149
  eng "Tablespace size stored in header is %lu pages, but the sum of data file sizes is only %lu pages"

ER_IB_MSG_1150
  eng "Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database."

ER_IB_MSG_1151
  eng "%s started; log sequence number %llu"

ER_IB_MSG_1152
  eng "Waiting for purge to complete"

OBSOLETE_ER_IB_MSG_1153
  eng "Waiting for dict_stats_thread to exit"

ER_IB_MSG_1154
  eng "Query counter shows %lld queries still inside InnoDB at shutdown"

ER_IB_MSG_1155
  eng "Shutdown completed; log sequence number %llu"

ER_IB_MSG_1156
  eng "Cannot continue operation."

ER_IB_MSG_1157
  eng "%s"

ER_IB_MSG_1158
  eng "%s"

ER_IB_MSG_1159
  eng "%s"

ER_IB_MSG_1160
  eng "%s"

ER_IB_MSG_1161
  eng "%s"

ER_IB_MSG_1162
  eng "%s"

ER_IB_MSG_1163
  eng "%s"

ER_IB_MSG_1164
  eng "%s"

ER_IB_MSG_1165
  eng "%s"

ER_IB_MSG_UNDO_TRUNCATE_FAIL_TO_READ_LOG_FILE
  eng "Unable to read the existing undo truncate log file '%s'. The error is %s"

ER_IB_MSG_UNDO_MARKED_FOR_TRUNCATE
  eng "Undo tablespace %s is marked for truncate"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_MDL
  eng "%s"

ER_IB_MSG_UNDO_TRUNCATE_START
  eng "Truncating UNDO tablespace %s"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_DDL_LOG_START
  eng "%s"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_LOG_CREATE
  eng "Cannot create truncate log for undo tablespace '%s'."

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_TRUNCATE
  eng "%s"

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_FAILURE
  eng "Failed to truncate undo tablespace '%s'."

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_STATE_UPDATE
  eng "%s"

ER_IB_MSG_UNDO_TRUNCATE_COMPLETE
  eng "Completed truncate of undo tablespace %s."

OBSOLETE_ER_IB_MSG_UNDO_INJECT_TRUNCATE_DONE
  eng "%s"

ER_IB_MSG_1177
  eng "%s"

ER_IB_MSG_1178
  eng "%s"

ER_IB_MSG_1179
  eng "%s"

ER_IB_MSG_1180
  eng "%s"

ER_IB_MSG_1181
  eng "%s"

ER_IB_MSG_1182
  eng "%s"

ER_IB_MSG_1183
  eng "%s"

ER_IB_MSG_1184
  eng "%s"

ER_IB_MSG_1185
  eng "%s"

ER_IB_MSG_1186
  eng "%s"

ER_IB_MSG_1187
  eng "%s"

ER_IB_MSG_1188
  eng "%s"

ER_IB_MSG_1189
  eng "%s"

ER_IB_MSG_TRX_RECOVERY_ROLLBACK_COMPLETED
  eng "Rollback of non-prepared transactions completed"

ER_IB_MSG_1191
  eng "%s"

ER_IB_MSG_1192
  eng "%s"

ER_IB_MSG_1193
  eng "%s"

ER_IB_MSG_1194
  eng "%s"

ER_IB_MSG_1195
  eng "%s"

ER_IB_MSG_1196
  eng "%s"

ER_IB_MSG_1197
  eng "%s"

ER_IB_MSG_1198
  eng "%s"

ER_IB_MSG_1199
  eng "%s"

ER_IB_MSG_1200
  eng "%s"

ER_IB_MSG_1201
  eng "%s"

ER_IB_MSG_1202
  eng "%s"

ER_IB_MSG_1203
  eng "%s"

ER_IB_MSG_1204
  eng "%s"

ER_IB_MSG_1205
  eng "%s"

ER_IB_MSG_1206
  eng "%s"

ER_IB_MSG_1207
  eng "%s"

ER_IB_MSG_1208
  eng "%s"

ER_IB_MSG_1209
  eng "%s"

ER_IB_MSG_1210
  eng "%s"

ER_IB_MSG_1211
  eng "Blocked High Priority Transaction (ID %llu, Thread ID %s) killed the blocking transaction (ID %llu - %s) by rolling it back."

ER_IB_MSG_1212
  eng "%s"

ER_IB_MSG_1213
  eng "gettimeofday() failed: %s"

ER_IB_MSG_1214
  eng "Can't create UNDO tablespace %s %s"

ER_IB_MSG_1215
  eng "%s"

ER_IB_MSG_LOG_FILES_RESIZE_ON_START
  eng "Resizing redo log from %lluM to %lluM (LSN=%llu) synchronously. If this takes too long, consider starting the server with large --innodb_redo_log_capacity, and resizing the redo log online using SET."

ER_IB_MSG_1217
  eng "%s"

ER_IB_MSG_1218
  eng "%s"

ER_IB_MSG_1219
  eng "%s"

ER_IB_MSG_1220
  eng "%s"

ER_IB_MSG_1221
  eng "%s"

ER_IB_MSG_1222
  eng "%s"

ER_IB_MSG_1223
  eng "%s"

ER_IB_MSG_1224
  eng "%s"

ER_IB_MSG_1225
  eng "%s"

ER_IB_MSG_1226
  eng "%s"

ER_IB_MSG_1227
  eng "%s"

ER_IB_MSG_1228
  eng "%s"

ER_IB_MSG_1229
  eng "%s"

OBSOLETE_ER_IB_MSG_1230
  eng "%s"

ER_IB_MSG_1231
  eng "%s"

OBSOLETE_ER_IB_MSG_1232
  eng "%s"

ER_IB_MSG_1233
  eng "%s"

ER_IB_MSG_LOG_WRITER_OUT_OF_SPACE
  eng "Out of space in the redo log. Checkpoint LSN: %llu. Consider increasing innodb_redo_log_capacity."

ER_IB_MSG_1235
  eng "%s"

ER_IB_MSG_LOG_WRITER_ABORTS_LOG_ARCHIVER
  eng "Log writer waited too long for redo-archiver to advance (1 second). There are unarchived: %llu bytes. Archiver LSN: %llu. Aborted the redo-archiver. Consider increasing innodb_redo_log_capacity."

ER_IB_MSG_LOG_WRITER_WAITING_FOR_ARCHIVER
  eng "Log writer is waiting for redo-archiver to catch up unarchived: %llu bytes. Archiver LSN: %llu. Consider increasing innodb_redo_log_capacity."

ER_IB_MSG_1238
  eng "%s"

ER_IB_MSG_1239
  eng "%s"

OBSOLETE_ER_IB_MSG_1240
  eng "%s"

ER_IB_MSG_1241
  eng "%s"

ER_IB_MSG_LOG_FILES_CANNOT_ENCRYPT_IN_READ_ONLY
  eng "Can't set redo log files to be encrypted in read-only mode."

ER_IB_MSG_LOG_FILES_ENCRYPTION_INIT_FAILED
  eng "Can't set redo log files to be encrypted."

OBSOLETE_ER_IB_MSG_1244
  eng "Can't set redo log tablespace to be encrypted."

ER_IB_MSG_1245
  eng "Redo log encryption is enabled."

ER_IB_MSG_1246
  eng "Waiting for archiver to finish archiving page and log"

ER_IB_MSG_1247
  eng "Starting shutdown..."

ER_IB_MSG_1248
  eng "Waiting for %s to exit."

ER_IB_MSG_1249
  eng "Waiting for rollback of %zu recovered transactions, before shutdown."

ER_IB_MSG_1250
  eng "Waiting for master thread to be suspended."

ER_IB_MSG_1251
  eng "Waiting for page_cleaner to finish flushing of buffer pool."

ER_IB_MSG_BUF_PENDING_IO_ON_SHUTDOWN
  eng "Shutdown is waiting for %zu buffer page I/Os to complete."

ER_IB_MSG_1253
  eng "MySQL has requested a very fast shutdown without flushing the InnoDB buffer pool to data files. At the next mysqld startup InnoDB will do a crash recovery!"

OBSOLETE_ER_IB_MSG_1254
  eng "%s"

ER_IB_MSG_1255
  eng "%s"

ER_IB_MSG_1256
  eng "%s"

ER_IB_MSG_1257
  eng "%s"

ER_IB_MSG_1258
  eng "%s"

ER_IB_MSG_1259
  eng "%s"

ER_IB_MSG_1260
  eng "%s"

ER_IB_MSG_1261
  eng "%s"

ER_IB_MSG_1262
  eng "%s"

ER_IB_MSG_1263
  eng "%s"

ER_IB_MSG_LOG_FILE_HEADER_INVALID_CHECKSUM
  eng "Invalid redo log header checksum."

ER_IB_MSG_LOG_FORMAT_BEFORE_5_7_9
  eng "Unsupported redo log format (v%lu). The redo log was created before MySQL 5.7.9"

ER_IB_MSG_1266
  eng "%s"

ER_IB_MSG_LOG_PARAMS_CONCURRENCY_MARGIN_UNSAFE
  eng "Cannot continue operation. The innodb_redo_log_capacity=%lluM is too small for the innodb_thread_concurrency=%lu. The capacity of redo should be >= %lluM. To get mysqld running, set innodb_thread_concurrency to a smaller value or increase innodb_redo_log_capacity. %s"

ER_IB_MSG_1268
  eng "%s"

ER_IB_MSG_1269
  eng "%s"

ER_IB_MSG_THREAD_CONCURRENCY_CHANGED
  eng "User has set innodb_thread_concurrency to %lu."

ER_RPL_REPLICA_SQL_THREAD_STOP_CMD_EXEC_TIMEOUT
  eng "STOP REPLICA command execution is incomplete: Replica SQL thread got the stop signal, thread is busy, SQL thread will stop once the current task is complete."

ER_RPL_REPLICA_IO_THREAD_STOP_CMD_EXEC_TIMEOUT
  eng "STOP REPLICA command execution is incomplete: Replica IO thread got the stop signal, thread is busy, IO thread will stop once the current task is complete."

ER_RPL_GTID_UNSAFE_STMT_ON_NON_TRANS_TABLE
  eng "Statement violates GTID consistency: Updates to non-transactional tables can only be done in either autocommitted statements or single-statement transactions, and never in the same statement as updates to transactional tables."

ER_RPL_GTID_UNSAFE_STMT_CREATE_SELECT
  eng "Statement violates GTID consistency: CREATE TABLE ... SELECT."

OBSOLETE_ER_RPL_GTID_UNSAFE_STMT_ON_TEMPORARY_TABLE
  eng "Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed outside transactional context.  These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions."

ER_BINLOG_ROW_VALUE_OPTION_IGNORED
  eng "When %.192s, the option binlog_row_value_options=%.192s will be ignored and updates will be written in full format to binary log."

ER_BINLOG_USE_V1_ROW_EVENTS_IGNORED
  eng "When %.192s, the option log_bin_use_v1_row_events=1 will be ignored and row events will be written in new format to binary log."

ER_BINLOG_ROW_VALUE_OPTION_USED_ONLY_FOR_AFTER_IMAGES
  eng "When %.192s, the option binlog_row_value_options=%.192s will be used only for the after-image. Full values will be written in the before-image, so the saving in disk space due to binlog_row_value_options is limited to less than 50%%."

ER_CONNECTION_ABORTED
  eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s)."

ER_NORMAL_SERVER_SHUTDOWN
  eng "%s: Normal shutdown."

ER_KEYRING_MIGRATE_FAILED
  eng "Can not perform keyring migration : %s."

ER_GRP_RPL_LOWER_CASE_TABLE_NAMES_DIFF_FROM_GRP
  eng "The member is configured with a lower_case_table_names option value '%u' different from the group '%u'. The member will now exit the group. If there is existing data on member, it may be incompatible with group if it was created with a lower_case_table_names value different from the group."

ER_OOM_SAVE_GTIDS
  eng "An out-of-memory error occurred while saving the set of GTIDs from the last binary log into the mysql.gtid_executed table"

ER_LCTN_NOT_FOUND
  eng "The lower_case_table_names setting for the data dictionary was not found. Starting the server using lower_case_table_names = '%u'."

OBSOLETE_ER_REGEXP_INVALID_CAPTURE_GROUP_NAME
  eng "A capture group has an invalid name."

ER_COMPONENT_FILTER_WRONG_VALUE
  eng "Variable '%-.64s' can't be set to the value of '%-.200s'"

ER_XPLUGIN_FAILED_TO_STOP_SERVICES
  eng "Stopping services failed with error \"%s\""

ER_INCONSISTENT_ERROR
  eng "Query caused different errors on source and replica. Error on source: message (format)='%s' error code=%d; Error on replica:actual message='%s', error code=%d. Default database:'%s'. Query:'%s'"

ER_SERVER_SOURCE_FATAL_ERROR_READING_BINLOG
  eng "Got fatal error %d from source when reading data from binary log: '%-.512s'"

ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE
  eng "Replication event checksum verification failed while reading from network."

ER_REPLICA_CREATE_EVENT_FAILURE
  eng "Failed to create %s"

ER_REPLICA_FATAL_ERROR
  eng "Fatal error: %s"

ER_REPLICA_HEARTBEAT_FAILURE
  eng "Unexpected source's heartbeat data: %s"

ER_REPLICA_INCIDENT
  eng "The incident %s occurred on the source. Message: %s"

ER_REPLICA_SOURCE_COM_FAILURE
  eng "Source command %s failed: %s"

ER_REPLICA_RELAY_LOG_READ_FAILURE
  eng "Relay log read failure: %s"

ER_REPLICA_RELAY_LOG_WRITE_FAILURE
  eng "Relay log write failure: %s"

ER_SERVER_REPLICA_CM_INIT_REPOSITORY
  eng "Replica failed to initialize connection metadata structure from the repository"

ER_SERVER_REPLICA_AM_INIT_REPOSITORY
  eng "Replica failed to initialize applier metadata structure from the repository"

ER_SERVER_NET_PACKET_TOO_LARGE
  eng "Got a packet bigger than 'max_allowed_packet' bytes"

ER_SERVER_NO_SYSTEM_TABLE_ACCESS
  eng "Access to %.64s '%.64s.%.64s' is rejected."

OBSOLETE_ER_SERVER_UNKNOWN_ERROR
  eng "Unknown error"

ER_SERVER_UNKNOWN_SYSTEM_VARIABLE
  eng "Unknown system variable '%-.64s'"

ER_SERVER_NO_SESSION_TO_SEND_TO
  eng "A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-%06d - %s"

ER_SERVER_NEW_ABORTING_CONNECTION 08S01
  eng "Aborted connection %u to db: '%-.192s' user: '%-.48s' host: '%-.255s' (%-.64s; diagnostics area: MY-%06d - %-.64s)"

ER_SERVER_OUT_OF_SORTMEMORY
  eng "Out of sort memory, consider increasing server sort buffer size!"

ER_SERVER_RECORD_FILE_FULL
  eng "The table '%-.192s' is full!"

ER_SERVER_DISK_FULL_NOWAIT
  eng "Create table/tablespace '%-.192s' failed, as disk is full."

ER_SERVER_HANDLER_ERROR
  eng "Handler reported error %d - %s"

ER_SERVER_NOT_FORM_FILE
  eng "Incorrect information in file: '%-.200s'"

ER_SERVER_CANT_OPEN_FILE
  eng "Can't open file: '%-.200s' (OS errno: %d - %s)"

ER_SERVER_FILE_NOT_FOUND
  eng "Can't find file: '%-.200s' (OS errno: %d - %s)"

ER_SERVER_FILE_USED
  eng "'%-.192s' is locked against change (OS errno: %d - %s)"

ER_SERVER_CANNOT_LOAD_FROM_TABLE_V2
  eng "Cannot load from %s.%s. The table is probably corrupted!"

ER_ERROR_INFO_FROM_DA
  eng "Error in diagnostics area: MY-%06d - %s"

ER_SERVER_TABLE_CHECK_FAILED
  eng "Incorrect definition of table %s.%s: expected column '%s' at position %d, found '%s'."

ER_SERVER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2
  eng "The column count of %s.%s is wrong. Expected %d, found %d. Created with MySQL %d, now running %d. Please perform the MySQL upgrade procedure."

ER_SERVER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2
  eng "Column count of %s.%s is wrong. Expected %d, found %d. The table is probably corrupted"

ER_SERVER_ACL_TABLE_ERROR
  eng ""

ER_SERVER_REPLICA_INIT_QUERY_FAILED
  eng "Replica SQL thread aborted. Can't execute init_replica query, MY-%06d - '%s'"

ER_SERVER_REPLICA_CONVERSION_FAILED
  eng "Column %d of table '%-.192s.%-.192s' cannot be converted from type '%-.32s' to type '%-.32s'"

ER_SERVER_REPLICA_IGNORED_TABLE
  eng "Replica SQL thread ignored the query because of replicate-*-table rules"

ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION
  eng "Cannot replicate anonymous transaction when AUTO_POSITION = 1, at file %.400s, position %lld."

ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON
  eng "Cannot replicate anonymous transaction when @@GLOBAL.GTID_MODE = ON, at file %.400s, position %lld."

ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF
  eng "Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE = OFF, at file %.400s, position %lld."

# This entry is intended for testing (for instance, the server-log test
# component throws this, and has the built-in filtering engine select these)
# as it is disjunct from all error-codes used in real operation. Message is
# kept intentionally short to despam resulting output files.
ER_SERVER_TEST_MESSAGE
  eng "Simulated error"

ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR
  eng "%s"

ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED
  eng "Audit Log filtering has not been installed."

ER_PLUGIN_FAILED_TO_OPEN_TABLES
  eng "Failed to open the %s filter tables."

ER_PLUGIN_FAILED_TO_OPEN_TABLE
  eng "Failed to open '%s.%s' %s table."

ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY
  eng "Filter name cannot be empty."

ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER
  eng "Invalid character in the user name."

ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE
  eng "Request ignored for '%s'@'%s'. SUPER or AUDIT_ADMIN needed to perform operation"

ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED
  eng "No keyring installed."

ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER
  eng "Invalid character in the host name."

ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET
  eng "Audit log encryption password has not been set; it will be generated automatically. Use audit_log_encryption_password_get to obtain the password or audit_log_encryption_password_set to set a new one."

ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY
  eng "Could not create AES key. OpenSSL's EVP_BytesToKey function failed."

ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED
  eng "Audit log encryption password cannot be fetched from the keyring. Password used so far is used for encryption."

ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS
  eng "Could not reinitialize audit log filters."

ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY
  eng "User cannot be empty."

ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC
  eng "First character of the user name must be alphanumeric."

ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXIST
  eng "Specified filter has not been found."

ER_IB_MSG_1271
  eng "Cannot upgrade server earlier than 5.7 to 8.0"

ER_STARTING_INIT
  eng "%s (mysqld %s) initializing of server in progress as process %lu"

ER_ENDING_INIT
  eng "%s (mysqld %s) initializing of server has completed"

ER_IB_MSG_1272
  eng "Cannot boot server version %lu on data directory built by version %llu. Downgrade is not supported"

ER_SERVER_SHUTDOWN_INFO
  eng "Received SHUTDOWN from user %s. Shutting down mysqld (Version: %s)."

ER_GRP_RPL_PLUGIN_ABORT
  eng "The plugin encountered a critical error and will abort: %s"

OBSOLETE_ER_REGEXP_INVALID_FLAG
  eng "Invalid match mode flag in regular expression."

OBSOLETE_ER_XA_REPLICATION_FILTERS
  eng "The use of replication filters with XA transactions is not supported, and can lead to an undefined state in the replica."

OBSOLETE_ER_UPDATE_GTID_PURGED_WITH_GR
  eng "Cannot update GTID_PURGED with the Group Replication plugin running"

ER_AUDIT_LOG_TABLE_DEFINITION_NOT_UPDATED
  eng "'%s.%s' table definition has not been upgraded; Please perform the MySQL upgrade procedure."

ER_DD_INITIALIZE_SQL_ERROR
  eng "Execution of server-side SQL statement '%s' failed with error code = %d, error message = '%s'."

ER_NO_PATH_FOR_SHARED_LIBRARY
  eng "No paths allowed for shared library."

ER_UDF_ALREADY_EXISTS
  eng "Function '%-.192s' already exists."

ER_SET_EVENT_FAILED
  eng "Got Error: %ld from SetEvent."

ER_FAILED_TO_ALLOCATE_SSL_BIO
  eng "Error allocating SSL BIO."

ER_IB_MSG_1273
  eng "%s"

ER_PID_FILEPATH_LOCATIONS_INACCESSIBLE
  eng "One or several locations were inaccessible while checking PID filepath."

ER_UNKNOWN_VARIABLE_IN_PERSISTED_CONFIG_FILE
  eng "Currently unknown variable '%s' was read from the persisted config file."

ER_FAILED_TO_HANDLE_DEFAULTS_FILE
  eng "Fatal error in defaults handling. Program aborted!"

ER_DUPLICATE_SYS_VAR
  eng "Duplicate variable name '%s'."

ER_FAILED_TO_INIT_SYS_VAR
  eng "Failed to initialize system variables."

ER_SYS_VAR_NOT_FOUND
  eng "Variable name '%s' not found."

ER_IB_MSG_1274
  eng "Some (%d) threads are still active"

ER_IB_MSG_1275
  eng "%s"

# Unused since MySQL 8.0.15
OBSOLETE_ER_TARGET_TS_UNENCRYPTED
  eng "Source tablespace is encrypted but target tablespace is not."

ER_IB_MSG_WAIT_FOR_ENCRYPT_THREAD
  eng "Waiting for tablespace_alter_encrypt_thread to exit"

ER_IB_MSG_1277
  eng "%s"

ER_IB_MSG_NO_ENCRYPT_PROGRESS_FOUND
  eng "%s"

ER_IB_MSG_RESUME_OP_FOR_SPACE
  eng "%s"

ER_IB_MSG_1280
  eng "%s"

ER_IB_MSG_1281
  eng "%s"

ER_IB_MSG_1282
  eng "%s"

ER_IB_MSG_1283
  eng "%s"

ER_IB_MSG_1284
  eng "%s"

ER_CANT_SET_ERROR_SUPPRESSION_LIST_FROM_COMMAND_LINE
  eng "%s: Could not add suppression rule for code \"%s\". Rule-set may be full, or code may not correspond to an error-log message."

ER_INVALID_VALUE_OF_BIND_ADDRESSES
  eng "Invalid value for command line option bind-addresses: '%s'"

ER_RELAY_LOG_SPACE_LIMIT_DISABLED
  eng "Ignoring the @@global.relay_log_space_limit option because @@global.relay_log_purge is disabled."

ER_GRP_RPL_ERROR_GTID_SET_EXTRACTION
  eng "Error when extracting GTID execution information: %s"

ER_GRP_RPL_MISSING_GRP_RPL_ACTION_COORDINATOR
  eng "Message received without a proper group coordinator module."

ER_GRP_RPL_JOIN_WHEN_GROUP_ACTION_RUNNING
  eng "A member cannot join the group while a group configuration operation '%s' is running initiated by '%s'."

ER_GRP_RPL_JOINER_EXIT_WHEN_GROUP_ACTION_RUNNING
  eng "A member is joining the group while a group configuration operation '%s' is running initiated by '%s'. The member will now leave the group."

ER_GRP_RPL_CHANNEL_THREAD_WHEN_GROUP_ACTION_RUNNING
  eng "Can't start %s for channel '%s' when group replication is running a group configuration operation '%s' initiated by '%s'."

ER_GRP_RPL_APPOINTED_PRIMARY_NOT_PRESENT
  eng "A primary election was invoked but the requested primary member is not in the group. Request ignored."

ER_GRP_RPL_ERROR_ON_MESSAGE_SENDING
  eng "Error while sending message. Context: %s"

ER_GRP_RPL_CONFIGURATION_ACTION_ERROR
  eng "Error while executing a group configuration operation: %s"

ER_GRP_RPL_CONFIGURATION_ACTION_LOCAL_TERMINATION
  eng "Configuration operation '%s' terminated. %s"

ER_GRP_RPL_CONFIGURATION_ACTION_START
  eng "Starting group operation local execution: %s"

ER_GRP_RPL_CONFIGURATION_ACTION_END
  eng "Termination of group operation local execution: %s"

ER_GRP_RPL_CONFIGURATION_ACTION_KILLED_ERROR
  eng "A configuration change was killed in this member. The member will now leave the group as its configuration may have diverged."

ER_GRP_RPL_PRIMARY_ELECTION_PROCESS_ERROR
  eng "There was an issue on the primary election process: %s The member will now leave the group."

ER_GRP_RPL_PRIMARY_ELECTION_STOP_ERROR
  eng "There was an issue when stopping a previous election process: %s"

ER_GRP_RPL_NO_STAGE_SERVICE
  eng "It was not possible to initialize stage logging for this task. The operation will still run without stage tracking."

ER_GRP_RPL_UDF_REGISTER_ERROR
  eng "Could not execute the installation of Group Replication UDF function: %s. Check if the function is already present, if so, try to remove it"

ER_GRP_RPL_UDF_UNREGISTER_ERROR
  eng "Could not uninstall Group Replication UDF functions. Try to remove them manually if present."

ER_GRP_RPL_UDF_REGISTER_SERVICE_ERROR
  eng "Could not execute the installation of Group Replication UDF functions. Check for other errors in the log and try to reinstall the plugin"

ER_GRP_RPL_SERVER_UDF_ERROR
  eng "The function '%s' failed. %s"

OBSOLETE_ER_CURRENT_PASSWORD_NOT_REQUIRED
  eng "Do not specify the current password while changing it for other users."

OBSOLETE_ER_INCORRECT_CURRENT_PASSWORD
  eng "Incorrect current password. Specify the correct password which has to be replaced."

OBSOLETE_ER_MISSING_CURRENT_PASSWORD
  eng "Current password needs to be specified in the REPLACE clause in order to change it."

ER_SERVER_WRONG_VALUE_FOR_VAR
  eng "Variable '%-.64s' can't be set to the value of '%-.200s'"

ER_COULD_NOT_CREATE_WINDOWS_REGISTRY_KEY
  eng "%s was unable to create a new Windows registry key %s for %s; continuing to use the previous ident."

ER_SERVER_GTID_UNSAFE_CREATE_DROP_TEMP_TABLE_IN_TRX_IN_SBR
  eng "Statement violates GTID consistency: CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE are not allowed inside a transaction or inside a procedure in a transactional context when @@session.binlog_format=STATEMENT."

OBSOLETE_ER_SECONDARY_ENGINE
  eng "Secondary engine operation failed. %s."

OBSOLETE_ER_SECONDARY_ENGINE_DDL
  eng "DDLs on a table with a secondary engine defined are not allowed."

OBSOLETE_ER_NO_SESSION_TEMP
  eng "Unable to allocate temporary tablespace for this session"

ER_XPLUGIN_FAILED_TO_SWITCH_SECURITY_CTX
  eng "Unable to switch security context to user: %s"

ER_RPL_GTID_UNSAFE_ALTER_ADD_COL_WITH_DEFAULT_EXPRESSION
  eng "Statement violates GTID consistency: ALTER TABLE ... ADD COLUMN .. with expression as DEFAULT."

ER_UPGRADE_PARSE_ERROR
  eng "Error in parsing %s '%s'.'%s' during upgrade. %s"

ER_DATA_DIRECTORY_UNUSABLE
  eng "The designated data directory %s is unusable. You can remove all files that the server added to it."
  bgn "Зададената папка за базата %s е неизползваема. Можете да изтриете файловете които сървъра добави в нея."

ER_LDAP_AUTH_USER_GROUP_SEARCH_ROOT_BIND
  eng "Group search rebinding via root DN: %s "

ER_PLUGIN_INSTALL_ERROR
  eng "Error installing plugin '%s': %s"

ER_PLUGIN_UNINSTALL_ERROR
  eng "Error uninstalling plugin '%s': %s"

ER_SHARED_TABLESPACE_USED_BY_PARTITIONED_TABLE
  eng "Partitioned table '%s' is not allowed to use shared tablespace '%s'. Please move all partitions to file-per-table tablespaces before upgrade."

ER_UNKNOWN_TABLESPACE_TYPE
  eng "Cannot determine the type of the tablespace named '%s'."

ER_WARN_DEPRECATED_UTF8_ALIAS_OPTION
  eng "%s: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous."

ER_WARN_DEPRECATED_UTF8MB3_CHARSET_OPTION
  eng "%s: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead."

ER_WARN_DEPRECATED_UTF8MB3_COLLATION_OPTION
  eng "%s: '%-.64s' is a collation of the deprecated character set UTF8MB3. Please consider using UTF8MB4 with an appropriate collation instead."

ER_SSL_MEMORY_INSTRUMENTATION_INIT_FAILED
  eng "The SSL library function %s failed. This is typically caused by the SSL library already being used. As a result the SSL memory allocation will not be instrumented."
  bgn "Функцията от SSL библиотеката %s върна грешка. Това обикновено е защото SSL библиотеката вече е била използвана. Заради това SSL паметта няма да се инструментира."

ER_IB_MSG_MADV_DONTDUMP_UNSUPPORTED
  eng "Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet MADV_DONTDUMP is not supported on this platform"

ER_IB_MSG_MADVISE_FAILED
  eng "Disabling @@core_file because @@innodb_buffer_pool_in_core_file is disabled, yet madvise(%p,%zu,%s) failed with %s"

OBSOLETE_ER_COLUMN_CHANGE_SIZE
  eng "Could not change column '%s' of table '%s'. The resulting size of index '%s' would exceed the max key length of %d bytes."

ER_WARN_REMOVED_SQL_MODE
  eng "sql_mode=0x%08x has been removed and will be ignored"

ER_IB_MSG_FAILED_TO_ALLOCATE_WAIT
  eng "Failed to allocate memory for a pool of size %zu bytes. Will wait for %zu seconds for a thread to free a resource."

OBSOLETE_ER_IB_MSG_NUM_POOLS
 eng "Number of pools: %zu"

ER_IB_MSG_USING_UNDO_SPACE
  eng "Using undo tablespace '%s'."

ER_IB_MSG_FAIL_TO_SAVE_SPACE_STATE
  eng "%s Unable to save the current state of tablespace '%s' to the data dictionary"

ER_IB_MSG_MAX_UNDO_SPACES_REACHED
  eng "Cannot create undo tablespace %s at %s because %d undo tablespaces already exist."

ER_IB_MSG_ERROR_OPENING_NEW_UNDO_SPACE
  eng "Error %d opening newly created undo tablespace %s."

ER_IB_MSG_FAILED_SDI_Z_BUF_ERROR
  eng "SDI Compression failed, Z_BUF_ERROR"

ER_IB_MSG_FAILED_SDI_Z_MEM_ERROR
  eng "SDI Compression failed, Z_MEM_ERROR"

ER_IB_MSG_SDI_Z_STREAM_ERROR
  eng "SDI Compression failed, Z_STREAM_ERROR"

ER_IB_MSG_SDI_Z_UNKNOWN_ERROR
  eng "%s"

ER_IB_MSG_FOUND_WRONG_UNDO_SPACE
  eng "Expected to find undo tablespace '%s' for Space ID=%lu, but found '%s' instead!  Did you change innodb_undo_directory?"

ER_IB_MSG_NOT_END_WITH_IBU
  eng "Cannot use %s as an undo tablespace because it does not end with '.ibu'."

OBSOLETE_ER_IB_MSG_UNDO_TRUNCATE_EMPTY_FILE
  eng "ib_undo_trunc_empty_file"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_DD_UPDATE
  eng "ib_undo_trunc_before_dd_update"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_UNDO_LOGGING
  eng "ib_undo_trunc_before_done_logging"

OBSOLETE_ER_IB_MSG_UNDO_INJECT_BEFORE_RSEG
  eng "ib_undo_trunc_before_rsegs"

ER_IB_MSG_FAILED_TO_FINISH_TRUNCATE
  eng "%s Failed to finish truncating Undo Tablespace '%s'"

ER_IB_MSG_DEPRECATED_INNODB_UNDO_TABLESPACES
  eng "The setting INNODB_UNDO_TABLESPACES is deprecated and is no longer used.  InnoDB always creates 2 undo tablespaces to start with. If you need more, please use CREATE UNDO TABLESPACE."

ER_IB_MSG_WRONG_TABLESPACE_DIR
  eng "The directory for tablespace %s does not exist or is incorrect."

ER_IB_MSG_LOCK_FREE_HASH_USAGE_STATS
  eng "%s"

ER_CLONE_DONOR_TRACE
  eng "Clone donor reported : %.512s."

ER_CLONE_PROTOCOL_TRACE
  eng "Clone received unexpected response from donor : %.512s."

ER_CLONE_CLIENT_TRACE
  eng "Client: %.512s."

ER_CLONE_SERVER_TRACE
  eng "Server: %.512s."

ER_THREAD_POOL_PFS_TABLES_INIT_FAILED
  eng "Failed to initialize the performance schema tables service."

ER_THREAD_POOL_PFS_TABLES_ADD_FAILED
  eng "Failed to add thread pool performance schema tables."

ER_CANT_SET_DATA_DIR
  eng "Failed to set datadir to \'%-.200s\' (OS errno: %d - %s)"

ER_INNODB_INVALID_INNODB_UNDO_DIRECTORY_LOCATION
  eng "The innodb_undo_directory is not allowed to be an ancestor of the datadir."

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_FETCH_KEY
  eng "Failed to fetch key from keyring, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_KEY_NOT_FOUND
  eng "Can't find key from keyring, please check in the server log if a keyring is loaded and initialized successfully."

ER_SERVER_RPL_ENCRYPTION_KEYRING_INVALID_KEY
  eng "Fetched an invalid key from keyring."

ER_SERVER_RPL_ENCRYPTION_HEADER_ERROR
  eng "Error reading a replication log encryption header: %s."

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ROTATE_LOGS
  eng "Failed to rotate some logs after changing binlog encryption settings. Please fix the problem and rotate the logs manually."

ER_SERVER_RPL_ENCRYPTION_KEY_EXISTS_UNEXPECTED
  eng "Key %s exists unexpected."

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_GENERATE_KEY
  eng "Failed to generate key, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_STORE_KEY
  eng "Failed to store key, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_REMOVE_KEY
  eng "Failed to remove key, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_MASTER_KEY_RECOVERY_FAILED
  eng "Unable to recover binlog encryption master key, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_INITIALIZE
  eng "Failed to initialize binlog encryption, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_UNABLE_TO_ROTATE_MASTER_KEY_AT_STARTUP
  eng "Failed to rotate binlog encryption master key at startup, please check if keyring is loaded."

ER_SERVER_RPL_ENCRYPTION_IGNORE_ROTATE_MASTER_KEY_AT_STARTUP
  eng "Ignoring binlog_rotate_encryption_master_key_at_startup because binlog_encryption option is disabled."

ER_INVALID_ADMIN_ADDRESS
  eng "Invalid value for command line option admin-address: '%s'"

ER_SERVER_STARTUP_ADMIN_INTERFACE
  eng "Admin interface ready for connections, address: '%s'  port: %d"

ER_CANT_CREATE_ADMIN_THREAD
  eng "Can't create thread to handle admin connections (errno= %d)"

ER_WARNING_RETAIN_CURRENT_PASSWORD_CLAUSE_VOID
  eng "RETAIN CURRENT PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords."

ER_WARNING_DISCARD_OLD_PASSWORD_CLAUSE_VOID
  eng "DISCARD OLD PASSWORD ignored for user '%s'@'%s' as its authentication plugin %s does not support multiple passwords."

OBSOLETE_ER_SECOND_PASSWORD_CANNOT_BE_EMPTY
  eng "Empty password can not be retained as second password for user '%s'@'%s'."

OBSOLETE_ER_PASSWORD_CANNOT_BE_RETAINED_ON_PLUGIN_CHANGE
  eng "Current password can not be retained for user '%s'@'%s' because authentication plugin is being changed."

OBSOLETE_ER_CURRENT_PASSWORD_CANNOT_BE_RETAINED
  eng "Current password can not be retained for user '%s'@'%s' because new password is empty."

ER_WARNING_AUTHCACHE_INVALID_USER_ATTRIBUTES
  eng "Can not read and process value of User_attributes column from mysql.user table for user: '%s@%s'; Ignoring user."

ER_MYSQL_NATIVE_PASSWORD_SECOND_PASSWORD_USED_INFORMATION
  eng "Second password was used for login by user: '%s'@'%s'."

ER_SHA256_PASSWORD_SECOND_PASSWORD_USED_INFORMATION
  eng "Second password was used for login by user: '%s'@'%s'."

ER_CACHING_SHA2_PASSWORD_SECOND_PASSWORD_USED_INFORMATION
  eng "Second password was used for login by user: '%s'@'%s'."

ER_GRP_RPL_SEND_TRX_PREPARED_MESSAGE_FAILED
  eng "Error sending transaction '%d:%lld' prepared message from session '%u'."

ER_GRP_RPL_RELEASE_COMMIT_AFTER_GROUP_PREPARE_FAILED
  eng "Error releasing transaction '%d:%lld' for commit on session '%u' after being prepared on all group members."

ER_GRP_RPL_TRX_ALREADY_EXISTS_ON_TCM_ON_AFTER_CERTIFICATION
  eng "Transaction '%d:%lld' already exists on Group Replication consistency manager while being registered after conflict detection."

ER_GRP_RPL_FAILED_TO_INSERT_TRX_ON_TCM_ON_AFTER_CERTIFICATION
  eng "Error registering transaction '%d:%lld' on Group Replication consistency manager after conflict detection."

ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_GROUP_PREPARE_FAILED
  eng "Error registering transaction '%d:%lld' from session '%u' to wait for being prepared on all group members."

ER_GRP_RPL_TRX_WAIT_FOR_GROUP_PREPARE_FAILED
  eng "Error on transaction '%d:%lld' from session '%u' while waiting for being prepared on all group members."

ER_GRP_RPL_TRX_DOES_NOT_EXIST_ON_TCM_ON_HANDLE_REMOTE_PREPARE
  eng "Transaction '%d:%lld' does not exist on Group Replication consistency manager while receiving remote transaction prepare."

ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_DEPENDENCIES_COMMIT_FAILED
  eng "Error releasing transaction '%d:%lld' for execution on session '%u' after its dependencies did complete commit."

ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_DEPENDENCIES_FAILED
  eng "Error registering transaction from session '%u' to wait for its dependencies to complete commit."

ER_GRP_RPL_WAIT_FOR_DEPENDENCIES_FAILED
  eng "Error on session '%u' while waiting for its dependencies to complete commit."

ER_GRP_RPL_REGISTER_TRX_TO_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED
  eng "Error registering transaction from session '%u' to wait for sync before execution."

ER_GRP_RPL_SEND_TRX_SYNC_BEFORE_EXECUTION_FAILED
  eng "Error sending sync before execution message from session '%u'."

ER_GRP_RPL_TRX_WAIT_FOR_SYNC_BEFORE_EXECUTION_FAILED
  eng "Error on transaction from session '%u' while waiting for sync before execution."

ER_GRP_RPL_RELEASE_BEGIN_TRX_AFTER_WAIT_FOR_SYNC_BEFORE_EXEC
  eng "Error releasing transaction for execution on session '%u' after wait for sync before execution."

ER_GRP_RPL_TRX_WAIT_FOR_GROUP_GTID_EXECUTED
  eng "Error waiting for group executed transactions commit on session '%u'."

OBSOLETE_ER_UNIT_NOT_FOUND SU001
  eng "There's no unit of measure named '%s'."

OBSOLETE_ER_GEOMETRY_IN_UNKNOWN_LENGTH_UNIT SU001
  eng "The function %s uses %s as a unit, but was passed geometry without units (\"SRID 0\"). Conversion is not possible."

ER_WARN_PROPERTY_STRING_PARSE_FAILED
  eng "Could not parse key-value pairs in property string '%s'"

ER_INVALID_PROPERTY_KEY
  eng "Property key '%s' is invalid."

ER_GRP_RPL_GTID_SET_EXTRACT_ERROR_DURING_RECOVERY
  eng "Error when extracting the group_replication_applier channel received transactions set. Unable to ensure the execution of group transactions received during recovery."

ER_SERVER_RPL_ENCRYPTION_FAILED_TO_ENCRYPT
  eng "Failed to encrypt content to write into binlog file: %s."

ER_CANNOT_GET_SERVER_VERSION_FROM_TABLESPACE_HEADER
  eng "Cannot get the server version number from the dictionary tablespace header."

ER_CANNOT_SET_SERVER_VERSION_IN_TABLESPACE_HEADER
  eng "Cannot set the server version number in the dictionary tablespace header."

ER_SERVER_UPGRADE_VERSION_NOT_SUPPORTED
  eng "Upgrading the server from server version '%u' is not supported."

ER_SERVER_UPGRADE_FROM_VERSION
  eng "MySQL server upgrading from version '%u' to '%u'."

ER_GRP_RPL_ERROR_ON_CERT_DB_INSTALL
  eng "The certification information could not be set in this server: '%s'"

ER_GRP_RPL_FORCE_MEMBERS_WHEN_LEAVING
  eng "A request to force a new group membership was issued when the member is leaving the group."

ER_TRG_WRONG_ORDER
  eng "Trigger %s.%s for table %s.%s is listed in wrong order. Please drop and recreate all triggers for the table."

OBSOLETE_ER_SECONDARY_ENGINE_PLUGIN
  eng "%s"

ER_LDAP_AUTH_GRP_SEARCH_NOT_SPECIAL_HDL
  eng "Special handling for group search, {GA} not found"

ER_LDAP_AUTH_GRP_USER_OBJECT_HAS_GROUP_INFO
  eng "User group retrieval: User object has group information"

ER_LDAP_AUTH_GRP_INFO_FOUND_IN_MANY_OBJECTS
  eng "Group information found in multiple user objects. Search filter configuration is incorrect."

ER_LDAP_AUTH_GRP_INCORRECT_ATTRIBUTE
  eng "User group retrieval: no group attribute found. Incorrect group search attribute. "

ER_LDAP_AUTH_GRP_NULL_ATTRIBUTE_VALUE
  eng "User group retrieval: Group attribute values is NULL. "

ER_LDAP_AUTH_GRP_DN_PARSING_FAILED
  eng "User group retrieval: parsing DN failed. "

ER_LDAP_AUTH_GRP_OBJECT_HAS_USER_INFO
  eng "User group retrieval: Group object has user information"

ER_LDAP_AUTH_LDAPS
  eng "Reserved port for ldaps using ldaps"

ER_LDAP_MAPPING_GET_USER_PROXY
  eng "Get user proxy"

ER_LDAP_MAPPING_USER_DONT_BELONG_GROUP
  eng "Get user proxy: User doesn't belongs to any group, user name will be treated as authenticated user."

ER_LDAP_MAPPING_INFO
  eng "Get user proxy: configured mapping info: %s"

ER_LDAP_MAPPING_EMPTY_MAPPING
  eng "Get user proxy: User doesn't have group mapping information, First LDAP group will be treated as authenticated user."

ER_LDAP_MAPPING_PROCESS_MAPPING
  eng "Process group proxy mapping"

ER_LDAP_MAPPING_CHECK_DELIMI_QUOTE
  eng "Check delimiter after quote"

ER_LDAP_MAPPING_PROCESS_DELIMITER
  eng "Processing delimiter"

ER_LDAP_MAPPING_PROCESS_DELIMITER_EQUAL_NOT_FOUND
  eng "Processing delimiter, separator = not found, resetting position"

ER_LDAP_MAPPING_PROCESS_DELIMITER_TRY_COMMA
  eng ""Processing delimiter, failed to get data for = separator try for separator ,.""

ER_LDAP_MAPPING_PROCESS_DELIMITER_COMMA_NOT_FOUND
  eng "Processing delimiter, separator , not found, resetting position"

ER_LDAP_MAPPING_NO_SEPEARATOR_END_OF_GROUP
  eng "Processing delimiter: No mapping separator is found, end of group information"

ER_LDAP_MAPPING_GETTING_NEXT_MAPPING
  eng "Getting next mapping information"

ER_LDAP_MAPPING_PARSING_CURRENT_STATE
  eng "Parsing mapping, current state: %d  delimiter char: %c "

ER_LDAP_MAPPING_PARSING_MAPPING_INFO
  eng "Parsing mapping info, LDAP group: %s MySQL proxy: %s"

ER_LDAP_MAPPING_PARSING_ERROR
  eng "Mapping parsing error"

ER_LDAP_MAPPING_TRIMMING_SPACES
  eng "Trimming left spaces"

ER_LDAP_MAPPING_IS_QUOTE
  eng "Checking if current characters is quote"

ER_LDAP_MAPPING_NON_DESIRED_STATE
  eng "Not desired state or un-defined states."

ER_INVALID_NAMED_PIPE_FULL_ACCESS_GROUP
  eng "Invalid value for named_pipe_full_access_group."

# This error is not supposed to be reported to the users. It is only
# meant for internal use to signal that a statement should be
# reprepared for a secondary storage engine. The error should be
# caught and handled by the server.
ER_PREPARE_FOR_SECONDARY_ENGINE
  eng "Retry the statement using a secondary storage engine."

ER_SERVER_WARN_DEPRECATED
  eng "'%s' is deprecated and will be removed in a future release. Please use %s instead"
ER_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES
  eng "Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege."

ER_SERVER_BINLOG_MASTER_KEY_RECOVERY_OUT_OF_COMBINATION
  eng "Unable to recover binary log master key, the combination of new_master_key_seqno=%u, master_key_seqno=%u and old_master_key_seqno=%u are wrong."

ER_SERVER_BINLOG_MASTER_KEY_ROTATION_FAIL_TO_CLEANUP_AUX_KEY
  eng "Failed to remove auxiliary binary log encryption key from keyring, please check if keyring is loaded. The cleanup of the binary log master key rotation process did not finish as expected and the cleanup will take place upon server restart or next 'ALTER INSTANCE ROTATE BINLOG MASTER KEY' execution."

OBSOLETE_ER_CANNOT_GRANT_SYSTEM_PRIV_TO_MANDATORY_ROLE
  eng "AuthId `%.64s`@`%.64s` is set as mandatory_roles. Cannot grant the '%s' privilege."

OBSOLETE_ER_PARTIAL_REVOKE_AND_DB_GRANT_BOTH_EXISTS
  eng "'%s' privilege for database '%s' exists both as partial revoke and mysql.db simultaneously. It could mean 'mysql' schema is corrupted."

OBSOLETE_ER_DB_ACCESS_DENIED
  eng "Access denied for AuthId `%.64s`@`%.64s` to database '%-.192s'."

OBSOLETE_ER_PARTIAL_REVOKES_EXIST
  eng "At least one partial revoke exists on a database. The system variable '@@partial_revokes' must be set to ON."

ER_TURNING_ON_PARTIAL_REVOKES
  eng "At least one partial revoke exists on a database. Turning ON the system variable '@@partial_revokes'."

ER_WARN_PARTIAL_REVOKE_AND_DB_GRANT
  eng "For user '%s'@'%s', one or more privileges granted through mysql.db for database '%s', conflict with partial revoke. It could mean 'mysql' schema is corrupted."

ER_WARN_INCORRECT_PRIVILEGE_FOR_DB_RESTRICTIONS
  eng "For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as these are not valid database privileges."

ER_WARN_INVALID_DB_RESTRICTIONS
  eng "For user %s, ignored restrictions for privilege(s) '%s' for database '%s' as corresponding global privilege(s) are not granted."

ER_GRP_RPL_INVALID_COMMUNICATION_PROTOCOL
  eng "'%s' is an invalid value for group_replication_communication_protocol_join, please use a MySQL version between 5.7.14 and this server's version"

ER_GRP_RPL_STARTED_AUTO_REJOIN
  eng "Started auto-rejoin procedure attempt %lu of %lu"

ER_GRP_RPL_TIMEOUT_RECEIVED_VC_ON_REJOIN
  eng "Timeout while waiting for a view change event during the auto-rejoin procedure"

ER_GRP_RPL_FINISHED_AUTO_REJOIN
  eng "Auto-rejoin procedure attempt %lu of %lu finished. Member was%s able to join the group."

ER_GRP_RPL_DEFAULT_TABLE_ENCRYPTION_DIFF_FROM_GRP
  eng "The member is configured with a default_table_encryption option value '%d' different from the group '%d'. The member will now exit the group."

ER_SERVER_UPGRADE_OFF
  eng "Server shutting down because upgrade is required, yet prohibited by the command line option '--upgrade=NONE'."

ER_SERVER_UPGRADE_SKIP
  eng "Server upgrade is required, but skipped by command line option '--upgrade=MINIMAL'."

ER_SERVER_UPGRADE_PENDING
  eng "Server upgrade started with version %d, but server upgrade of version %d is still pending."

ER_SERVER_UPGRADE_FAILED
  eng "Failed to upgrade server."

ER_SERVER_UPGRADE_STATUS
  eng "Server upgrade from '%d' to '%d' %s."

ER_SERVER_UPGRADE_REPAIR_REQUIRED
  eng "Table '%s' requires repair."

ER_SERVER_UPGRADE_REPAIR_STATUS
  eng "Table '%s' repair %s."

ER_SERVER_UPGRADE_INFO_FILE
  eng "Could not open server upgrade info file '%s' for writing. Please make sure the file is writable."

ER_SERVER_UPGRADE_SYS_SCHEMA
  eng "Upgrading the sys schema."

ER_SERVER_UPGRADE_MYSQL_TABLES
  eng "Running queries to upgrade MySQL server."

ER_SERVER_UPGRADE_SYSTEM_TABLES
  eng "Upgrading system table data."

ER_SERVER_UPGRADE_EMPTY_SYS
  eng "Found empty sys database. Installing the sys schema."

ER_SERVER_UPGRADE_NO_SYS_VERSION
  eng "A sys schema exists with no sys.version view. If you have a user created sys schema, this must be renamed for the upgrade to succeed."

ER_SERVER_UPGRADE_SYS_VERSION_EMPTY
  eng "A sys schema exists with a sys.version view, but it returns no results."

ER_SERVER_UPGRADE_SYS_SCHEMA_OUTDATED
  eng "Found outdated sys schema version %s."

ER_SERVER_UPGRADE_SYS_SCHEMA_UP_TO_DATE
  eng "The sys schema is already up to date (version %s)."

ER_SERVER_UPGRADE_SYS_SCHEMA_OBJECT_COUNT
  eng "Found %d sys %s, but expected %d. Re-installing the sys schema."

ER_SERVER_UPGRADE_CHECKING_DB
  eng "Checking '%s' schema."

ER_IB_MSG_DDL_LOG_DELETE_BY_ID_TMCT
  eng "Too many concurrent transactions while clearing the DDL Log. Please increase the number of Rollback Segments."

ER_IB_MSG_POST_RECOVER_DDL_LOG_RECOVER
  eng "Error in DDL Log recovery during Post-Recovery processing."

ER_IB_MSG_POST_RECOVER_POST_TS_ENCRYPT
  eng "Error in Post-Tablespace-Encryption during Post-Recovery processing."

ER_IB_MSG_DDL_LOG_FAIL_POST_DDL
  eng "Error in DLL Log cleanup during Post-DDL processing."

ER_SERVER_BINLOG_UNSAFE_SYSTEM_FUNCTION
  eng "'%s' statement is unsafe because it uses a system function that may return a different value on the replica."

ER_SERVER_UPGRADE_HELP_TABLE_STATUS
  eng "Upgrade of help tables %s."

OBSOLETE_ER_GRP_RPL_SRV_GTID_WAIT_ERROR
  eng "Error when waiting for the server to execute local transactions in order assure the group change proper logging"

OBSOLETE_ER_GRP_DELAYED_VCLE_LOGGING
  eng "Unable to log the group change View log event in its exaction position in the log. This will not however affect the group replication recovery process or the overall plugin process."

OBSOLETE_ER_CANNOT_GRANT_ROLES_TO_ANONYMOUS_USER
  eng "Cannot grant roles to an anonymous user."

ER_BINLOG_UNABLE_TO_ROTATE_GTID_TABLE_READONLY
  eng "Unable to create a new binlog file: Table `mysql.gtid_executed` couldn't be opened. %s"

ER_NETWORK_NAMESPACES_NOT_SUPPORTED
  eng "Network Namespaces is not supported on this platform"

ER_UNKNOWN_NETWORK_NAMESPACE
  eng "Unknown network namespace '%s'"

ER_NETWORK_NAMESPACE_NOT_ALLOWED_FOR_WILDCARD_ADDRESS
  eng "Network namespace not allowed for wildcard interface address"

ER_SETNS_FAILED
  eng "setns() failed with error '%s'"

ER_WILDCARD_NOT_ALLOWED_FOR_MULTIADDRESS_BIND
  eng "Wildcard address value not allowed for multivalued bind address"

ER_NETWORK_NAMESPACE_FILE_PATH_TOO_LONG
  eng "The path to a special network namespace file is too long. (got %u > max %u)"

ER_IB_MSG_TOO_LONG_PATH
  eng "Cannot create tablespace '%s'. The filepath is too long for this OS."

ER_IB_RECV_FIRST_REC_GROUP_INVALID
  eng "The last block of redo had corrupted first_rec_group and became fixed (%u -> %u)."

ER_DD_UPGRADE_COMPLETED
  eng "Data dictionary upgrade from version '%u' to '%u' completed."

ER_SSL_SERVER_CERT_VERIFY_FAILED
  eng "Server SSL certificate doesn't verify: %s"

ER_PERSIST_OPTION_USER_TRUNCATED
  eng "Truncated a user name for %s that was too long while reading the persisted variables file"

ER_PERSIST_OPTION_HOST_TRUNCATED
  eng "Truncated a host name for %s that was too long while reading the persisted variables file"

ER_NET_WAIT_ERROR
  eng "The wait_timeout period was exceeded, the idle time since last command was too long."

ER_IB_MSG_1285
  eng "'%s' found not encrypted while '%s' is ON. Trying to encrypt it now."

ER_IB_MSG_CLOCK_MONOTONIC_UNSUPPORTED
  eng "CLOCK_MONOTONIC is unsupported, so do not change the system time when MySQL is running !"

ER_IB_MSG_CLOCK_GETTIME_FAILED
  eng "clock_gettime() failed: %s"

ER_PLUGIN_NOT_EARLY_DUP
  eng "Plugin '%s' is not to be used as an "early" plugin. Don't add it to --early-plugin-load, keyring migration etc."
  bgn "Приставката '%s' не може да се използва като ранна приставка. Не я добавайте в --early-plugin-load и т.н."

ER_PLUGIN_NO_INSTALL_DUP
  eng "Plugin '%s' is marked as not dynamically installable. You have to stop the server to install it."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
OBSOLETE_ER_WARN_DEPRECATED_SQL_CALC_FOUND_ROWS
  eng "SQL_CALC_FOUND_ROWS is deprecated and will be removed in a future release. Consider using two separate queries instead."

# When using this error message, use the ER_WARN_DEPRECATED_SYNTAX error
# code.
OBSOLETE_ER_WARN_DEPRECATED_FOUND_ROWS
  eng "FOUND_ROWS() is deprecated and will be removed in a future release. Consider using COUNT(*) instead."

ER_BINLOG_UNSAFE_DEFAULT_EXPRESSION_IN_SUBSTATEMENT
  eng "The statement is unsafe because it invokes a trigger or a stored function that modifies a table that has a column with a DEFAULT expression that may return a different value on the replica."

ER_GRP_RPL_MEMBER_VER_READ_COMPATIBLE
  eng "Member version is read compatible with the group."

ER_LOCK_ORDER_INIT_FAILED
  eng "Lock order disabled (reason: init failed)."

ER_AUDIT_LOG_KEYRING_ID_TIMESTAMP_VALUE_IS_INVALID
  eng "Keyring ID timestamp value is invalid: '%s'"

ER_AUDIT_LOG_FILE_NAME_TIMESTAMP_VALUE_IS_MISSING_OR_INVALID
  eng "Cannot process audit log file. File name timestamp value is missing or invalid: '%s'"

ER_AUDIT_LOG_FILE_NAME_DOES_NOT_HAVE_REQUIRED_FORMAT
  eng "Cannot process audit log file. File name does not have required format: '%s'"

ER_AUDIT_LOG_FILE_NAME_KEYRING_ID_VALUE_IS_MISSING
  eng "Cannot process audit log file. File name keyring ID value is missing: '%s'"

ER_AUDIT_LOG_FILE_HAS_BEEN_SUCCESSFULLY_PROCESSED
  eng "Audit log file has been successfully processed: '%s'"

ER_AUDIT_LOG_COULD_NOT_OPEN_FILE_FOR_READING
  eng "Could not open audit log file for reading: '%s'"

ER_AUDIT_LOG_INVALID_FILE_CONTENT
  eng "Invalid audit log file content: '%s'"

ER_AUDIT_LOG_CANNOT_READ_PASSWORD
  eng "Cannot read password: '%.32s'."

ER_AUDIT_LOG_CANNOT_STORE_PASSWORD
  eng "Cannot store password: '%.32s'."

ER_AUDIT_LOG_CANNOT_REMOVE_PASSWORD
  eng "Cannot remove password: '%.32s'."

ER_AUDIT_LOG_PASSWORD_HAS_BEEN_COPIED
  eng "'audit_log' password has been copied into '%.32s' and will be removed with first purged password."

OBSOLETE_ER_AUDIT_LOG_INSUFFICIENT_PRIVILEGE
  eng "Request ignored for '%.64s'@'%.64s'. Role needed to perform operation: '%.32s'"

OBSOLETE_ER_WRONG_MVI_VALUE
  eng "Can't store an array or an object in a scalar key part of the index '%.192s'"

OBSOLETE_ER_WARN_FUNC_INDEX_NOT_APPLICABLE
  eng "Cannot use functional index '%-.64s' due to type or collation conversion"

OBSOLETE_ER_EXCEEDED_MV_KEYS_NUM
  eng "Exceeded max number of values per record for multi-valued index '%-.64s' by %u value(s)"

OBSOLETE_ER_EXCEEDED_MV_KEYS_SPACE
  eng "Exceeded max total length of values per record for multi-valued index '%-.64s' by %u bytes"

OBSOLETE_ER_FUNCTIONAL_INDEX_DATA_IS_TOO_LONG 22001
  eng "Data too long for functional index '%-.64s'"

OBSOLETE_ER_INVALID_JSON_VALUE_FOR_FUNC_INDEX 22018
  eng "Invalid JSON value for CAST for functional index '%-.64s'"

OBSOLETE_ER_JSON_VALUE_OUT_OF_RANGE_FOR_FUNC_INDEX 22003
  eng "Out of range JSON value for CAST for functional index '%-.64s'"

ER_LDAP_EMPTY_USERDN_PASSWORD
  eng "Empty user dn or password is not allowed, not attempting LDAP bind."

OBSOLETE_ER_GROUPING_ON_TIMESTAMP_IN_DST
  eng "Grouping on temporal is non-deterministic for timezones having DST. Please consider switching to UTC for this query."

ER_ACL_WRONG_OR_MISSING_ACL_TABLES_LOG
  eng "The current layout of the ACL tables does not conform to the server's expected layout. They're either altered, missing or not upgraded from a previous version. However a best effort attempt to read data from these tables will still be made."

ER_LOCK_ORDER_FAILED_WRITE_FILE
  eng "LOCK_ORDER: Failed to write to file <%s>."

ER_LOCK_ORDER_FAILED_READ_FILE
  eng "LOCK_ORDER: Failed to read from file <%s>."

ER_LOCK_ORDER_MESSAGE
  eng "LOCK_ORDER message: %s"

ER_LOCK_ORDER_DEPENDENCIES_SYNTAX
  eng "Lock order dependencies file <%s> (%d:%d) - (%d:%d) : %s"

ER_LOCK_ORDER_SCANNER_SYNTAX
  eng "Lock order scanner: (%d:%d) - (%d:%d) : %s"

ER_DATA_DIRECTORY_UNUSABLE_DELETABLE
  eng "The newly created data directory %s by --initialize is unusable. You can remove it."
  bgn "Новосъздадената от --initialize папка за базата %s е неизползваема. Можете да я изтриете."

ER_IB_MSG_BTREE_LEVEL_LIMIT_EXCEEDED
  eng "No. of B-tree level created for index %s has crossed the permissible limit. If debug option innodb_limit_optimistic_insert_debug is being used try tweaking it to include more records in a page."

ER_IB_CLONE_START_STOP
  eng "%s"

ER_IB_CLONE_OPERATION
  eng "%s"

ER_IB_CLONE_RESTART
  eng "%s"

ER_IB_CLONE_USER_DATA
  eng "Clone removing all user data for provisioning: %s"

ER_IB_CLONE_NON_INNODB_TABLE
  eng "Non innodb table: %s.%s is not cloned and is empty."

ER_CLONE_SHUTDOWN_TRACE
  eng "Clone shutting down server as RESTART failed. Please start server to complete clone operation."

ER_GRP_RPL_GTID_PURGED_EXTRACT_ERROR
  eng "Error when extracting this member GTID purged set. Operations and checks made to group joiners may be incomplete."

ER_GRP_RPL_CLONE_PROCESS_PREPARE_ERROR
  eng "There was an issue when configuring the remote cloning process: %s"

ER_GRP_RPL_CLONE_PROCESS_EXEC_ERROR
  eng "There was an issue when cloning from another server: %s"

ER_GRP_RPL_RECOVERY_EVAL_ERROR
  eng "There was an issue when trying to evaluate the best distributed recovery strategy while joining.%s"

ER_GRP_RPL_NO_POSSIBLE_RECOVERY
  eng "No valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs."

ER_GRP_RPL_CANT_KILL_THREAD
  eng "The group replication plugin could not kill the plugin routine for %s. %s"

ER_GRP_RPL_RECOVERY_STRAT_CLONE_THRESHOLD
  eng "This member will start distributed recovery using clone. It is due to the number of missing transactions being higher than the configured threshold of %llu."

ER_GRP_RPL_RECOVERY_STRAT_CLONE_PURGED
  eng "This member will start distributed recovery using clone. It is due to no ONLINE member has the missing data for recovering in its binary logs."

ER_GRP_RPL_RECOVERY_STRAT_CHOICE
  eng "Distributed recovery will transfer data using: %s"

ER_GRP_RPL_RECOVERY_STRAT_FALLBACK
  eng "Due to some issue on the previous step distributed recovery is now executing: %s"

ER_GRP_RPL_RECOVERY_STRAT_NO_FALLBACK
  eng "Due to a critical cloning error or lack of donors, distributed recovery cannot be executed. The member will now leave the group."

ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_CLONE
  eng "The '%s' thread of channel '%s' will error out as the server will attempt to clone another server"

ER_UNKNOWN_TABLE_IN_UPGRADE
  eng "Unknown table '%-.129s'"

ER_IDENT_CAUSES_TOO_LONG_PATH_IN_UPGRADE
  eng "Long database name and identifier for object resulted in path length exceeding %d characters. Path: '%s'."

ER_XA_CANT_CREATE_MDL_BACKUP
  eng "XA: Failed to take MDL Lock backup of PREPARED XA transaction during client disconnect."

ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED
  eng "SUPER privilege or AUDIT_ADMIN role required for '%s'@'%s' user."

ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE
  eng "Invalid argument type"

ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT
  eng "Invalid argument count"

ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED
  eng "audit_log plugin has not been installed using INSTALL PLUGIN syntax."

ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE
  eng "Invalid \"max_array_length\" argument type."

ER_LOG_CANNOT_WRITE_EXTENDED
  eng "Failed to write to %s: %s (%s)"

OBSOLETE_ER_UPGRADE_WITH_PARTITIONED_TABLES_REJECTED
  eng "Upgrading from server version %d with partitioned tables and lower_case_table_names == 1 on a case sensitive file system may cause issues, and is therefore prohibited. To upgrade anyway, restart the new server version with the command line option 'upgrade=FORCE'. When upgrade is completed, please execute 'RENAME TABLE <part_table_name> TO <new_table_name>; RENAME TABLE <new_table_name> TO <part_table_name>;' for each of the partitioned tables. Please see the documentation for further information."

ER_KEYRING_AWS_INCORRECT_PROXY
  eng "Incorrect environment variable %s, invalid port: %s"

ER_GRP_RPL_SERVER_SET_TO_OFFLINE_MODE_DUE_TO_ERRORS
  eng "The server was automatically set into offline mode after an error was detected."

ER_GRP_RPL_MESSAGE_SERVICE_FATAL_ERROR
  eng "A message sent through the Group Replication message deliver service was not delivered successfully. The server will now leave the group. Try to add the server back to the group and check if the problem persists, or check previous messages in the log for hints of what could be the problem."

ER_WARN_WRONG_COMPRESSION_ALGORITHM_LOG
  eng "Invalid SOURCE_COMPRESSION_ALGORITHMS '%.192s' found in repository for channel '%.192s'. Resetting to 'uncompressed' (no compression)."

ER_WARN_WRONG_COMPRESSION_LEVEL_LOG
  eng "Invalid SOURCE_ZSTD_COMPRESSION_LEVEL found in repository for channel '%.192s'. Resetting to %u."

ER_PROTOCOL_COMPRESSION_RESET_LOG
  eng "Option --protocol-compression-algorithms is reset to default value."

ER_XPLUGIN_COMPRESSION_ERROR
  eng "Fatal error while compressing outgoing data - %s"

ER_MYSQLBACKUP_MSG
  eng "%s"

ER_WARN_UNKNOWN_KEYRING_AWS_REGION
  eng "Unknown keyring_aws_region '%.192s'. Connection to AWS KMS may fail."

ER_WARN_LOG_PRIVILEGE_CHECKS_USER_DOES_NOT_EXIST
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this is not an existing user. Correct this before starting replication threads."

ER_WARN_LOG_PRIVILEGE_CHECKS_USER_CORRUPT
  eng "Invalid, corrupted PRIVILEGE_CHECKS_USER was found in the replication configuration repository for channel '%.192s'. Use CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER to correct the configuration."

ER_WARN_LOG_PRIVILEGE_CHECKS_USER_NEEDS_RPL_APPLIER_PRIV
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' was set to `%.64s`@`%.255s`, but this user does not have REPLICATION_APPLIER privilege. Correct this before starting the replication threads."

ER_OBSOLETE_FILE_PRIVILEGE_FOR_REPLICATION_CHECKS
  eng "The PRIVILEGE_CHECKS_USER for channel '%.192s' would need FILE privilege to execute a LOAD DATA INFILE statement replicated in statement format. Consider using binlog_format=ROW on source. If the replicated events are trusted, recover from the failure by temporarily granting FILE to the PRIVILEGE_CHECKS_USER."

ER_RPL_REPLICA_SQL_THREAD_STARTING_WITH_PRIVILEGE_CHECKS
  eng "Replica SQL thread%s initialized, starting replication in log '%s' at position %s, relay log '%s' position: %s, user: '%.64s'@'%.255s', roles: %.512s"

ER_AUDIT_LOG_CANNOT_GENERATE_PASSWORD
  eng "Cannot generate password: '%.32s'"

ER_INIT_FAILED_TO_GENERATE_ROOT_PASSWORD
  eng "Failed to generate a random password for root. Probabably not enough enthropy."

ER_PLUGIN_LOAD_OPTIONS_IGNORED
  eng "Ignoring --plugin-load[_add] list as the server is running with --initialize(-insecure)."

ER_WARN_AUTH_ID_WITH_SYSTEM_USER_PRIV_IN_MANDATORY_ROLES
  eng "Cannot set mandatory_roles: AuthId `%.64s`@`%.64s` has '%s' privilege. AuthId(s) set in the mandatory_roles are ignored."

ER_IB_MSG_SKIP_HIDDEN_DIR
  eng "Directory '%s' will not be scanned because it is a hidden directory."

ER_WARN_RPL_RECOVERY_NO_ROTATE_EVENT_FROM_SOURCE_EOF
  eng "Server was not able to find a rotate event from source server to initialize relay log recovery for channel '%s'. Skipping relay log recovery for the channel."

ER_IB_LOB_ROLLBACK_INDEX_LEN
  eng "Rolling back LOB for transaction %llu undo number %llu : current index length %llu. (iteration %llu)"

ER_CANT_PROCESS_EXPRESSION_FOR_GENERATED_COLUMN_TO_DD
  eng "Error in processing (possibly deprecated) expression or function '%.128s' for generated column %.64s.%.64s.%.64s"

ER_RPL_REPLICA_QUEUE_EVENT_FAILED_INVALID_NON_ROW_FORMAT
  eng "The queue event failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found."

ER_OBSOLETE_REQUIRE_ROW_FORMAT_VIOLATION
  eng "The application of relay events failed for channel '%s' as an invalid event according to REQUIRE_ROW_FORMAT was found."

ER_LOG_PRIV_CHECKS_REQUIRE_ROW_FORMAT_NOT_SET
  eng "PRIVILEGE_CHECKS_USER for replication channel '%.192s' can't be set to `%.64s`@`%.255s` unless REQUIRE_ROW_FORMAT is also set to %d."

ER_RPL_REPLICA_SQL_THREAD_DETECTED_UNEXPECTED_EVENT_SEQUENCE
  eng "An unexpected event sequence was detected by the SQL thread while applying an event."

ER_IB_MSG_UPGRADE_PARTITION_FILE
  eng "Updating partition file name '%s' to '%s' and all other partition files during upgrade"

ER_IB_MSG_DOWNGRADE_PARTITION_FILE
  eng "Updating partition file name '%s' to '%s' and all other partition files during downgrade"

ER_IB_MSG_UPGRADE_PARTITION_FILE_IMPORT
  eng "Updating partition file name '%s' to '%s' for import"

ER_IB_WARN_OPEN_PARTITION_FILE
  eng "Unable to open partition file with new name '%s'. Please check if innodb_directories is set to include all external file paths"

ER_IB_MSG_FIL_STATE_MOVED_CORRECTED
  eng "%s DD ID: %llu - Partition tablespace %u, name '%s' is corrected to '%s'"

ER_IB_MSG_FIL_STATE_MOVED_CHANGED_PATH
  eng "%s DD ID: %llu - Tablespace %u, name '%s', '%s' is moved to '%s'"

ER_IB_MSG_FIL_STATE_MOVED_CHANGED_NAME
  eng "%s DD ID: %llu - Partition tablespace %u, name '%s', '%s' is updated to '%s'"

ER_IB_MSG_FIL_STATE_MOVED_TOO_MANY
  eng "%s Too many files have been moved, disabling logging of detailed messages"

ER_GR_ELECTED_PRIMARY_GTID_INFORMATION
  eng "Elected primary member %s: %s"

ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED
  eng "Schema name '%s' containing upper case characters is not allowed with lower_case_table_names = 1."

ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED
  eng "Table name '%s.%s' containing upper case characters is not allowed with lower_case_table_names = 1."

ER_SCHEMA_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK
  eng "Schema name '%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1."

ER_TABLE_NAME_IN_UPPER_CASE_NOT_ALLOWED_FOR_FK
  eng "Table name '%s.%s' containing upper case characters, used by foreign key '%s' in table '%s.%s', is not allowed with lower_case_table_names = 1."

ER_IB_MSG_DICT_PARTITION_NOT_FOUND
  eng "Table Partition: %s is not found in InnoDB dictionary"

ER_ACCESS_DENIED_FOR_USER_ACCOUNT_BLOCKED_BY_PASSWORD_LOCK
  eng "Access denied for user '%-.48s'@'%-.64s'. Account is blocked for %s day(s) (%s day(s) remaining) due to %u consecutive failed logins. Use FLUSH PRIVILEGES or ALTER USER to reset."

ER_INNODB_OUT_OF_RESOURCES
  eng "%s"

ER_DD_UPGRADE_FOUND_PREPARED_XA_TRANSACTION
  eng "Upgrade cannot proceed due to an existing prepared XA transaction."

ER_MIGRATE_TABLE_TO_DD_OOM
  eng "Could not allocate memory for key_info when migrating table %s.%s"

ER_RPL_RELAY_LOG_RECOVERY_INFO_AFTER_CLONE
  eng "Applier metadata information for channel '%s' was found after a clone operation. Relay log recovery will be executed to adjust positions and file information for this new server. Should that automatic procedure fail please adjust the positions through 'CHANGE REPLICATION SOURCE TO'"

ER_IB_MSG_57_UNDO_SPACE_DELETE_FAIL
  eng "Failed to delete 5.7 undo tablespace: %s during upgrade"

ER_IB_MSG_DBLWR_1285
  eng "Empty doublewrite file: %s"

ER_IB_MSG_DBLWR_1286
  eng "Using '%s' for doublewrite"

ER_IB_MSG_DBLWR_1287
  eng  "Error reading doublewrite buffer from the system tablespace"

ER_IB_MSG_DBLWR_1288
  eng "Cannot create doublewrite buffer: you must increase your buffer pool size. Cannot continue operation."

ER_IB_MSG_DBLWR_1290
  eng "The page in the doublewrite file is corrupt. Cannot continue operation. You can try to recover the database with innodb_force_recovery=6"

ER_IB_MSG_BAD_DBLWR_FILE_NAME
  eng "The doublewrite filename '%s' is incorrect."

OBSOLETE_ER_IB_MSG_DBLWR_1292
  eng "%s"

ER_IB_MSG_DBLWR_1293
  eng "Doublewrite file create failed: %s"

ER_IB_MSG_DBLWR_1294
  eng "DBLWRThread: pthread_setaffinity() failed!"

ER_IB_MSG_DBLWR_1295
  eng "%s"

ER_IB_MSG_DBLWR_1296
  eng "%s"

ER_IB_MSG_DBLWR_1297
  eng "Doublewrite file read failed: %s"

ER_IB_MSG_DBLWR_1298
  eng "Dump of the data file page:"

ER_IB_MSG_DBLWR_1300
  eng "%s"

ER_IB_MSG_DBLWR_1301
  eng "%s"

ER_IB_MSG_DBLWR_1304
  eng "%s"

ER_IB_MSG_DBLWR_1305
  eng "%s"

ER_IB_MSG_DBLWR_1306
  eng "%s"

ER_IB_MSG_DBLWR_1307
  eng "%s"

ER_IB_MSG_DBLWR_1308
  eng "%s"

ER_IB_MSG_DBLWR_1309
  eng "%s"

ER_IB_MSG_DBLWR_1310
  eng "%s"

ER_IB_MSG_DBLWR_1311
  eng "%s"

ER_IB_MSG_DBLWR_1312
  eng "%s"

ER_IB_MSG_DBLWR_1313
  eng "%s"

ER_IB_MSG_DBLWR_1314
  eng "%s"

ER_IB_MSG_DBLWR_1315
  eng "%s"

ER_IB_MSG_DBLWR_1316
  eng "%s"

ER_IB_MSG_DBLWR_1317
  eng "%s"

ER_IB_MSG_DBLWR_1318
  eng "%s"

ER_IB_MSG_DBLWR_1319
  eng "Doublewrite load file %s size %lu is not a multiple of the configured page size %lu""

ER_IB_MSG_DBLWR_1320
  eng "Doublewrite file %s truncate failed"

ER_IB_MSG_DBLWR_1321
  eng "Doublewrite file %s failed to writ zeros"

ER_IB_MSG_DBLWR_1322
  eng "Doublewrite create file %s size %lu is not a multiple of the configured page size %lu""

ER_IB_MSG_DBLWR_1323
  eng "%s"

ER_IB_MSG_DBLWR_1324
  eng "%s"

ER_IB_MSG_DBLWR_1325
  eng "%s"

ER_IB_MSG_DBLWR_1326
  eng "%s"

ER_IB_MSG_DBLWR_1327
  eng "%s"

ER_IB_MSG_GTID_FLUSH_AT_SHUTDOWN
  eng "Could not flush all GTIDs during slow shutdown. Will recover GTIDs when server restarts."

ER_IB_MSG_57_STAT_SPACE_DELETE_FAIL
  eng "Failed to delete 5.7 stat tablespace: %s during upgrade"

ER_NDBINFO_UPGRADING_SCHEMA
  eng "Installing ndbinfo schema version %s"

ER_NDBINFO_NOT_UPGRADING_SCHEMA
  eng "Installed ndbinfo schema is current. Not upgrading."

ER_NDBINFO_UPGRADING_SCHEMA_FAIL
  eng "Failed to upgrade ndbinfo schema."

OBSOLETE_ER_IB_MSG_CREATE_LOG_FILE
  eng "%s"

ER_IB_MSG_INNODB_START_INITIALIZE
  eng "InnoDB initialization has started."

ER_IB_MSG_INNODB_END_INITIALIZE
  eng "InnoDB initialization has ended."

ER_IB_MSG_PAGE_ARCH_NO_RESET_POINTS
  eng "Could not find appropriate reset points."

ER_IB_WRN_PAGE_ARCH_FLUSH_DATA
  eng "Unable to flush. Page archiving data may be corrupt in case of a crash."

ER_IB_ERR_PAGE_ARCH_INVALID_DOUBLE_WRITE_BUF
  eng "Page archiver's doublewrite buffer for %ld is not valid."

ER_IB_ERR_PAGE_ARCH_RECOVERY_FAILED
  eng "Page archiver system's recovery failed."

ER_IB_ERR_PAGE_ARCH_INVALID_FORMAT
  eng "Invalid archived file name format. The archived file is supposed to have the format %s + [0-9]*."

ER_INVALID_XPLUGIN_SOCKET_SAME_AS_SERVER
  eng "X Plugins UNIX socket must use different file than MySQL server. X Plugin won't be accessible through UNIX socket"

ER_INNODB_UNABLE_TO_ACQUIRE_DD_OBJECT
  eng "%s"

ER_WARN_LOG_DEPRECATED_PARTITION_PREFIX_KEY
  eng "Column '%.64s.%.64s.%.64s' having prefix key part '%.64s(%u)' is ignored by the partitioning function. Use of prefixed columns in the PARTITION BY KEY() clause is deprecated and will be removed in a future release."

ER_IB_MSG_UNDO_TRUNCATE_TOO_OFTEN
  eng "Undo Truncation is occurring too often. Consider increasing --innodb-max-undo-log-size."

ER_GRP_RPL_IS_STARTING
  eng "Plugin 'group_replication' is starting."

ER_IB_MSG_INVALID_LOCATION_FOR_TABLESPACE
  eng "Cannot create tablespace %s because the directory is not a valid location. %s";

ER_IB_MSG_INVALID_LOCATION_WRONG_DB
  eng "Scanned file '%s' for tablespace %s cannot be opened because it is not in a sub-directory named for the schema.");

ER_IB_MSG_CANNOT_FIND_DD_UNDO_SPACE
  eng "Cannot find undo tablespace %s with filename '%s' as indicated by the Data Dictionary. Did you move or delete this tablespace? Any undo logs in it cannot be used."

ER_GRP_RPL_RECOVERY_ENDPOINT_FORMAT
  eng "Invalid input value for recovery socket endpoints '%s'. Please, provide a valid, comma separated, list of endpoints (IP:port)".

ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID
  eng "The server is not listening on endpoint '%s'. Only endpoints that the server is listening on are valid recovery endpoints."

ER_GRP_RPL_RECOVERY_ENDPOINT_INVALID_DONOR_ENDPOINT
  eng "Received invalid recovery endpoints configuration from donor. This member is not a valid donor for recovery, so it will be skipped."

ER_GRP_RPL_RECOVERY_ENDPOINT_INTERFACES_IPS
  eng "Failed to retrieve IP addresses from enabled host network interfaces."

ER_WARN_TLS_CHANNEL_INITIALIZATION_ERROR
  eng "Failed to initialize TLS for channel: %s. See below for the description of exact issue."

ER_XPLUGIN_FAILED_TO_VALIDATE_ADDRESS
  eng "Validation of value '%s' set to `Mysqlx_bind_address` failed: %s. Skipping this value."

ER_XPLUGIN_FAILED_TO_BIND_INTERFACE_ADDRESS
  eng "Value '%s' set to `Mysqlx_bind_address`, X Plugin can't bind to it. Skipping this value."

ER_IB_ERR_RECOVERY_REDO_DISABLED
  eng "Server was killed when InnoDB redo logging was disabled. Data files could be corrupt. You can try to restart the database with innodb_force_recovery=6"

ER_IB_WRN_FAST_SHUTDOWN_REDO_DISABLED
  eng "InnoDB cannot do cold shutdown 'innodb_fast_shutdown = 2' and is forcing 'innodb_fast_shutdown = 1' as redo logging is disabled. InnoDB would flush all dirty pages to ensure physical data consistency."

OBSOLETE_ER_IB_WRN_REDO_DISABLED
  eng "InnoDB redo logging is disabled. All data could be lost in case of a server crash."

ER_IB_WRN_REDO_ENABLED
  eng "InnoDB redo logging is enabled. Data is now safe and can be recovered in case of a server crash."

ER_TLS_CONFIGURED_FOR_CHANNEL
  eng "Channel %s configured to support TLS. Encrypted connections are now supported for this channel."

ER_TLS_CONFIGURATION_REUSED
  eng "No TLS configuration was given for channel %s; re-using TLS configuration of channel %s."

ER_IB_TABLESPACE_PATH_VALIDATION_SKIPPED
  eng "Skipping InnoDB tablespace path validation. Manually moved tablespace files will not be detected!"

ER_IB_CANNOT_UPGRADE_WITH_DISCARDED_TABLESPACES
  eng "Upgrade failed because database contains discarded tablespaces."

ER_USERNAME_TRUNKATED
  eng "The user name '%s' exceeds the maximum number of allowed characters %d and is trunkated."

ER_HOSTNAME_TRUNKATED
  eng "The host name '%s' exceeds the maximum number of allowed characters %d and is trunkated."

ER_IB_MSG_TRX_RECOVERY_ROLLBACK_NOT_COMPLETED
  eng "Rollback of non-prepared transactions not completed, due to fast shutdown"

ER_AUTHCACHE_ROLE_EDGES_IGNORED_EMPTY_NAME
  eng "Found an entry in the 'role_edges' table with empty authorization ID; Skipped"

ER_AUTHCACHE_ROLE_EDGES_UNKNOWN_AUTHORIZATION_ID
  eng "Found an entry in the 'role_edges' table with unknown authorization ID '%s'; Skipped"

ER_AUTHCACHE_DEFAULT_ROLES_IGNORED_EMPTY_NAME
  eng "Found an entry in the 'default_roles' table with empty authorization ID; Skipped"

ER_AUTHCACHE_DEFAULT_ROLES_UNKNOWN_AUTHORIZATION_ID
  eng "Found an entry in the 'default_roles' table with unknown authorization ID '%s'; Skipped"

ER_IB_ERR_DDL_LOG_INSERT_FAILURE
  eng "Couldn't insert entry in ddl log for ddl."

ER_IB_LOCK_VALIDATE_LATCH_ORDER_VIOLATION
  eng "%s"

ER_IB_RELOCK_LATCH_ORDER_VIOLATION
  eng "%s"

OBSOLETE_ER_IB_MSG_1352
  eng "%s"

OBSOLETE_ER_IB_MSG_1353
  eng "%s"

OBSOLETE_ER_IB_MSG_1354
  eng "%s"

OBSOLETE_ER_IB_MSG_1355
  eng "%s"

OBSOLETE_ER_IB_MSG_1356
  eng "%s"

ER_IB_MSG_1357
  eng "%s"

ER_IB_MSG_1358
  eng "%s"

ER_IB_MSG_1359
  eng "%s"

ER_IB_FAILED_TO_DELETE_TABLESPACE_FILE
  eng "%s"

ER_IB_UNABLE_TO_EXPAND_TEMPORARY_TABLESPACE_POOL
  eng "%s"

ER_IB_TMP_TABLESPACE_CANNOT_CREATE_DIRECTORY
  eng "%s"

ER_IB_MSG_SCANNING_TEMP_TABLESPACE_DIR
  eng "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_DOESNT_EXIST
  eng "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_EMPTY
  eng "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_CONTAINS_SEMICOLON
  eng "%s"

ER_IB_ERR_TEMP_TABLESPACE_DIR_SUBDIR_OF_DATADIR
  eng "%s"

ER_IB_ERR_SCHED_SETAFFNINITY_FAILED
  eng "%s"

ER_IB_ERR_UNKNOWN_PAGE_FETCH_MODE
  eng "%s"

ER_IB_ERR_LOG_PARSING_BUFFER_OVERFLOW
  eng "%s"

ER_IB_ERR_NOT_ENOUGH_MEMORY_FOR_PARSE_BUFFER
  eng "%s"

ER_IB_MSG_1372
  eng "%s"

ER_IB_MSG_1373
  eng "%s"

ER_IB_MSG_1374
  eng "%s"

ER_IB_MSG_1375
  eng "%s"

ER_IB_ERR_ZLIB_UNCOMPRESS_FAILED
  eng "%s"

ER_IB_ERR_ZLIB_BUF_ERROR
  eng "%s"

ER_IB_ERR_ZLIB_MEM_ERROR
  eng "%s"

ER_IB_ERR_ZLIB_DATA_ERROR
  eng "%s"

ER_IB_ERR_ZLIB_UNKNOWN_ERROR
  eng "%s"

ER_IB_MSG_1381
  eng "%s"

ER_IB_ERR_INDEX_RECORDS_WRONG_ORDER
  eng "%s"

ER_IB_ERR_INDEX_DUPLICATE_KEY
  eng "%s"

ER_IB_ERR_FOUND_N_DUPLICATE_KEYS
  eng "%s"

ER_IB_ERR_FOUND_N_RECORDS_WRONG_ORDER
  eng "%s"

ER_IB_ERR_PARALLEL_READ_OOM
  eng "%s"

ER_IB_MSG_UNDO_MARKED_ACTIVE
  eng "The state of undo tablespace %s is set to active implicitly."

ER_IB_MSG_UNDO_ALTERED_ACTIVE
  eng "The state of undo tablespace %s is set to 'active' by ALTER TABLESPACE."

ER_IB_MSG_UNDO_ALTERED_INACTIVE
  eng "The state of undo tablespace %s is set to 'inactive' by ALTER TABLESPACE."

ER_IB_MSG_UNDO_MARKED_EMPTY
  eng "The state of undo tablespace %s is set to 'empty'."

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_CLONE
  eng "Delaying truncate of undo tablespace %s due to clone activity."

ER_IB_MSG_UNDO_TRUNCATE_DELAY_BY_MDL
  eng "Delaying truncate of undo tablespace %s due to a metadata lock."

ER_IB_MSG_INJECT_CRASH
  eng "Injected debug crash point: %s"

ER_IB_MSG_INJECT_FAILURE
  eng "Injected debug failure point: %s"

ER_GRP_RPL_TIMEOUT_RECEIVED_VC_LEAVE_ON_REJOIN
  eng "Timeout while waiting for a view change event during the leave step before a auto-rejoin attempt."

ER_RPL_ASYNC_RECONNECT_FAIL_NO_SOURCE
  eng "Failed to automatically re-connect to a different source, for channel '%s', because %s. To fix this %s."

ER_UDF_REGISTER_SERVICE_ERROR
  eng "Could not execute the installation of UDF functions. Check for other errors in the log"

ER_UDF_REGISTER_ERROR
  eng "Could not execute the installation of UDF function: %s. Check if the function is already present, if so, try to remove it."

ER_UDF_UNREGISTER_ERROR
  eng "Could not uninstall UDF functions. Try to remove them manually if present."

ER_EMPTY_PRIVILEGE_NAME_IGNORED
  eng "An empty or illegal privilege identifier was ignored when global privileges were read from disk."

ER_IB_MSG_INCORRECT_SIZE
  eng "%s"

ER_TMPDIR_PATH_TOO_LONG
  eng "A tmpdir temporary path \"%s\" is too long (> %zu) for this OS. This would not leave enough space for a temporary filename of length %zu within it."

ER_ERROR_LOG_DESTINATION_NOT_A_FILE
  eng "Error-log destination \"%s\" is not a file. Can not restore error log messages from previous run."

ER_NO_ERROR_LOG_PARSER_CONFIGURED
  eng "None of the log-sinks selected with --log-error-services=... provides a log-parser. The server will not be able to make the previous runs' error-logs available in performance_schema.error_log."

ER_UPGRADE_NONEXISTENT_SCHEMA
  eng "The schema \"%.64s\" referenced by %.16s \"%.128s\" does not exist. Please clean up any orphan %.16s before upgrading."

ER_IB_MSG_CREATED_UNDO_SPACE
  eng "Created undo tablespace '%s'."

ER_IB_MSG_DROPPED_UNDO_SPACE
  eng "Dropped undo tablespace '%s'."

ER_IB_MSG_MASTER_KEY_ROTATED
  eng "The InnoDB Encryption Master Key has been rotated in %d tablespaces."

ER_IB_DBLWR_DECOMPRESS_FAILED
  eng "Failed to decompress a DBLWR page (err=%d).  The original size is %d. Reporting the dblwr page as corrupted."

ER_IB_DBLWR_DECRYPT_FAILED
  eng "Decrypting a page in doublewrite file failed: %s."

ER_IB_DBLWR_KEY_MISSING
  eng "Encryption key missing: %s."

ER_INNODB_IO_WRITE_ERROR_RETRYING
  eng "I/O error while writing to file: %s. Retrying ..."

ER_INNODB_IO_WRITE_FAILED
  eng "Failed to write data to file: %s"

ER_LOG_COMPONENT_CANNOT_INIT
  eng "Log component %s failed to initialize."

ER_RPL_ASYNC_CHANNEL_CANT_CONNECT
  eng "The Monitor IO thread failed to connect to the source (host:%s port:%u network_namespace:%s) for channel '%s', thence it will try to connect to another source."

ER_RPL_ASYNC_SENDER_ADDED
  eng  "The source (host:%s port:%u network_namespace:%s) for channel '%s' has joined the group (group_name: %s), and so added its entry into replication_asynchronous_connection_failover table."

ER_RPL_ASYNC_SENDER_REMOVED
  eng "The source (host:%s port:%u network_namespace:%s) for channel '%s' has left the group (group_name: %s), and so removed its entry from replication_asynchronous_connection_failover table."

ER_RPL_ASYNC_CHANNEL_STOPPED_QUORUM_LOST
  eng "The Monitor IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source."

ER_RPL_ASYNC_CHANNEL_CANT_CONNECT_NO_QUORUM
  eng "The IO thread detected that the source (host:%s port:%u network_namespace:%s) does not belong to the group majority, thence the channel '%s' will try to connect to another source."

ER_RPL_ASYNC_EXECUTING_QUERY
  eng "%s on the source (host:%s port:%u network_namespace:%s) for channel '%s'."

ER_RPL_REPLICA_MONITOR_IO_THREAD_EXITING
  eng "Replica Monitor IO thread exiting."

ER_RPL_ASYNC_MANAGED_NAME_REMOVED
  eng "The group (group_name: %s) for the channel '%s' has been removed, and so removed its entry from replication_asynchronous_connection_failover_managed and all the group members from replication_asynchronous_connection_failover table."

ER_RPL_ASYNC_MANAGED_NAME_ADDED
  eng "The group (group_name: %s) for the channel '%s' has been added, and so added its entry in replication_asynchronous_connection_failover_managed and source to replication_asynchronous_connection_failover table."

ER_RPL_ASYNC_READ_FAILOVER_TABLE
  eng "Error reading failover sources for channel '%s' from replication_asynchronous_connection_failover table."

ER_RPL_REPLICA_MONITOR_IO_THREAD_RECONNECT_CHANNEL
  eng "Error %s the channel '%s', the operation will be automatically retried."

ER_REPLICA_ANON_TO_GTID_IS_LOCAL_OR_UUID_AND_GTID_MODE_NOT_ON
  eng "Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s', which is invalid when GTID_MODE <> ON. If you intend to use GTID_MODE = ON everywhere, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = OFF and use the procedure for enabling GTIDs online (see the documentation). If you intend to use GTIDs on this replica and cannot enable GTIDs on the source, enable GTID_MODE = ON and leave ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS = LOCAL|<UUID>. If you intend to not use GTIDs at all in the replication topology, change to ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS=OFF and leave GTID_MODE = '%s'."

ER_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_GROUP_NAME
  eng "Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_group_name. To fix this issue, either change the group_replication_group_name  or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS."

ER_GRP_RPL_GRP_NAME_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID
  eng "The group_replication_group_name '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel"

ER_WARN_GTID_THRESHOLD_BREACH
  eng "The integer component of the GTID number is high. Suggest restarting the server with a new server_uuid to prevent it from reaching the maximum number 2^63-1, which will make it impossible to write the binary log and invoke the behavior specified by binlog_error_action."

ER_HEALTH_INFO
  eng "%s"

ER_HEALTH_WARNING
  eng "%s"

ER_HEALTH_ERROR
  eng "%s"

ER_HEALTH_WARNING_DISK_USAGE_LEVEL_1
  eng "%s: Warning Level 1 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB"

ER_HEALTH_WARNING_DISK_USAGE_LEVEL_2
  eng "%s: Warning Level 2 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB"

ER_HEALTH_WARNING_DISK_USAGE_LEVEL_3
  eng "%s: Warning Level 3 (%llu MiB): mount point = '%s', available = %llu MiB, total = %llu MiB, used = %.2f%%, low limit = %llu MiB, critical level = %llu MiB"

ER_IB_INNODB_TBSP_OUT_OF_SPACE
  eng "InnoDB: Size of tablespace %s is more than the maximum size allowed."

ER_GRP_RPL_APPLIER_CHANNEL_STILL_RUNNING
  eng "The group_replication_applier channel is still running, most likely it is waiting for a database/table lock, which is preventing the channel from stopping. Please check database/table locks, including the ones created by backup tools."

ER_RPL_ASYNC_RECONNECT_GTID_MODE_OFF_CHANNEL
  eng "Detected misconfiguration: replication channel \'%.192s\' was configured with SOURCE_CONNECTION_AUTO_FAILOVER = 1, but the server was started with a value other then --gtid-mode = ON. Either reconfigure replication using CHANGE REPLICATION SOURCE TO SOURCE_CONNECTION_AUTO_FAILOVER = 0 FOR CHANNEL \'%.192s\', or change GTID_MODE to value ON, before starting the replica receiver thread."

ER_FIREWALL_SERVICES_NOT_ACQUIRED
  eng "Could not acquire required component services."

ER_FIREWALL_UDF_REGISTER_FAILED
  eng "Automatic registration of function(s) failed."

ER_FIREWALL_PFS_TABLE_REGISTER_FAILED
  eng "Automatic registration of Performance schema table(s) failed."

ER_IB_MSG_STATS_SAMPLING_TOO_LARGE
  eng "%s"

ER_AUDIT_LOG_FILE_PRUNE_FAILED
  eng "Failed to auto-prune file '%s', Error (%d): %s"

ER_AUDIT_LOG_FILE_AUTO_PRUNED
  eng "File '%s' auto-pruned"

ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_INIT
  eng "Received an error while processing components from manifest file: %s"

ER_COMPONENTS_INFRASTRUCTURE_MANIFEST_DEINIT
  eng "Received an error while unloading components read from manifest file: %s"

ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_NOT_RO
  eng "Manifest file '%s' is not read-only. For better security, please make sure that the file is read-only."

ER_WARN_NO_KEYRING_COMPONENT_SERVICE_FOUND
  eng "No suitable '%s' service implementation found to fulfill the request."

ER_NOTE_KEYRING_COMPONENT_INITIALIZED
  eng "Keyring component initialized successfully."

ER_KEYRING_COMPONENT_NOT_INITIALIZED
  eng "The component is not initialized properly. Make sure that configuration is proper and use ALTER INSTANCE RELOAD KEYRING to reinitialize the component."

ER_KEYRING_COMPONENT_EXCEPTION
  eng "Keyring component encountered an exception while executing : '%s' API of service: '%s'"

ER_KEYRING_COMPONENT_MEMORY_ALLOCATION_ERROR
  eng "Failed to allocated memory for '%s' while executing: '%s' API of service: '%s'"

ER_NOTE_KEYRING_COMPONENT_AES_INVALID_MODE_BLOCK_SIZE
  eng "Empty or 0 values for AES encryption mode and/or block size are not permitted."

ER_NOTE_KEYRING_COMPONENT_AES_DATA_IDENTIFIER_EMPTY
  eng "A valid data identifier is required in order to fetch the key required for the AES operation."

ER_NOTE_KEYRING_COMPONENT_AES_INVALID_KEY
  eng "Key identified by Data ID: '%s' and Auth ID: '%s' is not of type AES."

ER_NOTE_KEYRING_COMPONENT_AES_OPERATION_ERROR
  eng "Encountered error: '%s' while executing '%s' API of keyring_aes service. Key details are Data ID: '%s' and Auth ID: '%s'."

ER_NOTE_KEYRING_COMPONENT_READ_DATA_NOT_FOUND
  eng "Could not find the data corresponding to Data ID: '%s', Auth ID: '%s'."

ER_NOTE_KEYRING_COMPONENT_WRITE_MAXIMUM_DATA_LENGTH
  eng "Maximum permissible size of data is '%zu' bits"

ER_NOTE_KEYRING_COMPONENT_STORE_FAILED
  eng "Error writing data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error."

ER_NOTE_KEYRING_COMPONENT_REMOVE_FAILED
  eng "Error removing data for Data ID: '%s', Auth ID: '%s'. Either data does not exists with same identifier or keyring backend encountered an error."

ER_NOTE_KEYRING_COMPONENT_GENERATE_FAILED
  eng "Error generating data for Data ID: '%s', Auth ID: '%s'. Either data already exists with same identifier or keyring backend encountered an error."

ER_NOTE_KEYRING_COMPONENT_KEYS_METADATA_ITERATOR_FETCH_FAILED
  eng "Failed to get metadata from current keys metadata iterator position."

ER_NOTE_KEYRING_COMPONENT_METADATA_ITERATOR_INVALID_OUT_PARAM
  eng "Key and value length parameters must not be null."

ER_IB_WRN_FAILED_TO_ACQUIRE_SERVICE
  eng "Innodb could not acquire service : %s"

ER_IB_WRN_OLD_GEOMETRY_TYPE
  eng "Column %s of type GEOMETRY is in old (5.6) format which could be deprecated in the future. To change the format to latest, please consider rebuilding the table after the upgrade."

ER_NET_WAIT_ERROR2
  eng "'wait_timeout' period of %s seconds was exceeded for %s. The idle time since last command was too long."

ER_GRP_RPL_MEMBER_ACTION_TRIGGERED
  eng "The member action "%s" for event "%s" with priority "%u" will be run."

ER_GRP_RPL_MEMBER_ACTION_FAILURE_IGNORE
  eng "The member action "%s" for event "%s" with priority "%u" failed, this error is ignored as instructed. Please check previous messages in the error log for hints about what could have caused this failure."

ER_GRP_RPL_MEMBER_ACTION_FAILURE
  eng "The member action "%s" for event "%s" with priority "%u" failed. Please check previous messages in the error log for hints about what could have caused this failure."

ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_RECEIVE
  eng "Unable to parse the member actions configuration sent by the primary."

ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS
  eng "Unable to update the member actions configuration with the one sent by the primary. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_GET_EXCHANGEABLE_DATA
  eng "Unable to read the member actions configuration during group membership change. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_DEFAULT_CONFIGURATION
  eng "This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one."

ER_GRP_RPL_MEMBER_ACTION_UNABLE_TO_SET_DEFAULT_CONFIGURATION
  eng "Unable to reset to member actions default configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_PARSE_ON_MEMBER_JOIN
  eng "Unable to parse the member actions configuration sent by the group on member join."

ER_GRP_RPL_MEMBER_ACTION_UPDATE_ACTIONS_ON_MEMBER_JOIN
  eng "Unable to update the member actions configuration on member join. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version'."

ER_GRP_RPL_MEMBER_ACTION_INVALID_ACTIONS_ON_MEMBER_JOIN
  eng "The group members were unable to send their member actions configuration. Please check the tables 'mysql.replication_group_member_actions' and 'mysql.replication_group_configuration_version' on all members."

ER_GRP_RPL_MEMBER_ACTION_ENABLED
  eng "Member action enabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s"."

ER_GRP_RPL_MEMBER_ACTION_DISABLED
  eng "Member action disabled: "%s", type: "%s", event: "%s", priority: "%u", error_handling: "%s"."

ER_GRP_RPL_MEMBER_ACTIONS_RESET
  eng "Member actions configuration was reset."

OBSOLETE_ER_DEPRECATED_TLS_VERSION_SESSION
  eng "Accepted a connection with deprecated protocol '%s' for account `%s`@`%s` from host `%s`. Client supplied username `%s`"

OBSOLETE_ER_WARN_DEPRECATED_TLS_VERSION_FOR_CHANNEL
  eng "A deprecated TLS version %s is enabled for channel %s"

ER_FIREWALL_DEPRECATED_USER_PROFILE
  eng "User profile \'%s\' loaded. Firewall user profiles are deprecated, consider migrating to group profiles."

ER_GRP_RPL_VIEW_CHANGE_UUID_INVALID
  eng "Invalid input value for group_replication_view_change_uuid '%s'. Please, provide a valid UUID."

ER_GRP_RPL_VIEW_CHANGE_UUID_SAME_AS_GROUP_NAME
  eng "Variable 'group_replication_view_change_uuid' cannot be set to the value of '%s'. If you want to use the UUID of 'group_replication_group_name' for the UUID of View_change_log_events, please set 'group_replication_view_change_uuid' to AUTOMATIC."

ER_GRP_RPL_GROUP_NAME_SAME_AS_VIEW_CHANGE_UUID
  eng "group_replication_group_name '%s', which is the same as group_replication_view_change_uuid. Please change group_replication_view_change_uuid to AUTOMATIC"

ER_GRP_RPL_VIEW_CHANGE_UUID_IS_SAME_AS_ANONYMOUS_TO_GTID_UUID
  eng "The group_replication_view_change_uuid '%s' is the same as the UUID value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS in a server channel"

ER_GRP_RPL_GRP_VIEW_CHANGE_UUID_IS_INCOMPATIBLE_WITH_SERVER_UUID
  eng "group_replication_view_change_uuid is incompatible with group. group_replication_view_change_uuid %s matches server_uuid %s."

ER_GRP_RPL_VIEW_CHANGE_UUID_DIFF_FROM_GRP
  eng "The member is configured with a group_replication_view_change_uuid option value '%s' different from the group '%s'. The member will now exit the group."

ER_WARN_REPLICA_ANONYMOUS_TO_GTID_UUID_SAME_AS_VIEW_CHANGE_UUID
  eng "Replication channel '%.192s' is configured with ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS='%s' which is equal to group_replication_view_change_uuid. To fix this issue, either change the group_replication_view_change_uuid or use a different value for ASSIGN_GTIDS_TO_ANONYMOUS_TRANSACTIONS."

ER_GRP_RPL_FAILED_TO_PARSE_THE_VIEW_CHANGE_UUID
  eng "Unable to parse the group_replication_view_change_uuid."

ER_GRP_RPL_FAILED_TO_GENERATE_SIDNO_FOR_VIEW_CHANGE_UUID
  eng "Unable to generate sidno for group_replication_view_change_uuid."

ER_GRP_RPL_VIEW_CHANGE_UUID_PARSE_ERROR
  eng "Unable to parse the group_replication_view_change_uuid during the Certification module initialization."

ER_GRP_RPL_UPDATE_GRPGTID_VIEW_CHANGE_UUID_EXECUTED_ERROR
  eng "Error updating group_gtid_executed GTID set with view change uuid during the Certification module initialization."

ER_GRP_RPL_ADD_VIEW_CHANGE_UUID_TO_GRP_SID_MAP_ERROR
  eng "Unable to add the group_replication_view_change_uuid sidno in the group_gtid_sid_map during the Certification module initialization."

ER_GRP_RPL_DONOR_VIEW_CHANGE_UUID_TRANS_INFO_ERROR
  eng "Unable to handle the donor's view change uuid transaction information when initializing the conflict detection component. Possible out of memory error."

ER_WARN_GRP_RPL_VIEW_CHANGE_UUID_FAIL_GET_VARIABLE
  eng "Unable to retrieve group_replication_view_change_uuid during server checks on replication operations."

ER_WARN_ADUIT_LOG_MAX_SIZE_AND_PRUNE_SECONDS_LOG
  eng "Both audit_log_max_size and audit_log_prune_seconds are set to non-zero. audit_log_max_size takes precedence and audit_log_prune_seconds is ignored"

ER_WARN_ADUIT_LOG_MAX_SIZE_CLOSE_TO_ROTATE_ON_SIZE_LOG
  eng "audit_log_rotate_on_size is not granular enough for the value of audit_log_max_size supplied. Should be at least %d times smaller."

ER_PLUGIN_INVALID_TABLE_DEFINITION
  eng "Invalid table definition for '%s.%s'."

ER_AUTH_KERBEROS_LOGGER_GENERIC_MSG
  eng "%s"

ER_INSTALL_PLUGIN_CONFLICT_LOG
  eng "Cannot install the %.192s plugin when the %.192s plugin is installed."

ER_DEPRECATED_PERSISTED_VARIABLE_WITH_ALIAS
  eng "The variable %s has been renamed to %s, and the old name deprecated. Only the old name was found in the persisted variable file. Next time the file is saved, both names will be stored. Issue any SET PERSIST command to save the file, get rid of this warning, and prepare the persisted configuration for when the variable is removed in a future version."

ER_LOG_COMPONENT_FLUSH_FAILED
  eng "%d error logging component(s) failed to flush. For file-based logs this can happen when the path or permissions of the log-file have changed. Failure to flush filed-based logs may affect log-rotation."

ER_IB_MSG_REENCRYPTED_TABLESPACE_KEY
  eng "Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you rebuild the table for better security."

ER_IB_MSG_REENCRYPTED_GENERAL_TABLESPACE_KEY
  eng "Tablespace key for %s has been re-encrypted using the latest InnoDB master key. However, we recommend that you reencrypt the tablespace for better security."

ER_IB_ERR_PAGE_ARCH_DBLWR_INIT_FAILED
  eng "Page Archiver's doublewrite buffer initialisation failed. Page tracking is at risk of losing tracked information."

ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__SKIP_IBUF_MERGES
  eng "There is not enough free space in the redo log during recovery to perform pending ibuf merges. Please retry starting MySQL with --innodb-force-recovery=4."

ER_IB_MSG_RECOVERY_NO_SPACE_IN_REDO_LOG__UNEXPECTED
  eng "There is not enough free space in the redo log during recovery, restore from backup (or retry with --innodb-force-recovery=6)."

ER_WARN_AUDIT_LOG_FORMAT_UNIX_TIMESTAMP_ONLY_WHEN_JSON_LOG
  eng "audit_log_format_unix_timestamp is applicable only when audit_log_format = JSON."

# This error is not supposed to be reported to the users. It is only
# meant for internal use to signal that a statement should be
# reprepared for the primary storage engine, without transformations.
# The error should be caught and handled by the server.
ER_PREPARE_FOR_PRIMARY_ENGINE
  eng "Retry the statement using the primary storage engine."

ER_IB_MSG_PAR_RSEG_INIT_COMPLETE_MSG
  eng "Parallel initialization of rseg complete"

ER_IB_MSG_PAR_RSEG_INIT_TIME_MSG
  eng "Time taken to initialize rseg using %u thread: %u ms."

ER_DDL_MSG_1
  eng "DDL failed to create a thread to load an index, fall back to single thread"

ER_MTR_MSG_1
  eng "Debug_check_no_latching failed, slot->type=%d"

ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_CONN_ERR
  eng "Failed to establish MySQL client connection in Group Replication. Error establishing connection. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections."

ER_GRP_RPL_MYSQL_NETWORK_PROVIDER_CLIENT_ERROR_COMMAND_ERR
  eng "Failed to establish MySQL client connection in Group Replication. Error sending connection delegation command. Please refer to the manual to make sure that you configured Group Replication properly to work with MySQL Protocol connections."

ER_GRP_RPL_FAILOVER_CONF_GET_EXCHANGEABLE_DATA
  eng "Unable to read the replication failover channels configuration during group membership change. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'."

ER_GRP_RPL_FAILOVER_CONF_DEFAULT_CONFIGURATION
  eng "This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one."

ER_GRP_RPL_FAILOVER_CONF_UNABLE_TO_SET_DEFAULT_CONFIGURATION
  eng "Unable to reset to replication failover channels default configuration on member join. Please check the tables 'mysql.replication_asynchronous_connection_failover', 'mysql.replication_asynchronous_connection_failover_managed' and 'mysql.replication_group_configuration_version'."

ER_GRP_RPL_FAILOVER_CONF_PARSE_ON_MEMBER_JOIN
  eng "Unable to parse the replication failover channels configuration sent by the group on member join."

ER_GRP_RPL_FAILOVER_CONF_CHANNEL_DOES_NOT_EXIST
  eng "Unable to set SOURCE_CONNECTION_AUTO_FAILOVER on a non-existent or misconfigured replication channel '%s', please create the channel and rejoin the server to the group."

ER_GRP_RPL_FAILOVER_REGISTER_MESSAGE_LISTENER_SERVICE
  eng "Unable to register the listener 'replication_asynchronous_connection_failover_configuration' to the service 'group_replication_message_service_recv'."

ER_GRP_RPL_FAILOVER_PRIMARY_WITHOUT_MAJORITY
  eng "This server is not able to reach a majority of members in the group. This server will skip the replication failover channels handling until this server is back to the group majority."

ER_GRP_RPL_FAILOVER_PRIMARY_BACK_TO_MAJORITY
  eng "This server is back to the group majority. Replication failover channels handling is resumed."

ER_RPL_INCREMENTING_MEMBER_ACTION_VERSION
  eng "Error incrementing member action configuration version for %s.%s table."

ER_GRP_RPL_REPLICA_THREAD_ERROR_ON_SECONDARY_MEMBER
  eng "The '%s' thread of channel '%s' will error out as this server is a group secondary."

ER_IB_MSG_CLONE_DDL_NTFN
  eng "Clone DDL Notification: %s"

ER_IB_MSG_CLONE_DDL_APPLY
  eng "Clone DDL APPLY: %s"

ER_IB_MSG_CLONE_DDL_INVALIDATE
  eng "Clone DDL Invalidate : %s"

ER_IB_MSG_UNDO_ENCRYPTION_INFO_LOADED
  eng "Encryption key is loaded for undo tablespace '%s'."

ER_IB_WRN_ENCRYPTION_INFO_SIZE_MISMATCH
  eng "Ignoring encryption INFO size in redo log: %zu, expected: %zu"

ER_INVALID_AUTHENTICATION_POLICY
  eng "Option --authentication-policy is set to an invalid value. Please check if the specified authentication plugins are valid."

ER_AUTHENTICATION_PLUGIN_REGISTRATION_FAILED
  eng "Signature verification failed during registration."

ER_AUTHENTICATION_PLUGIN_REGISTRATION_INSUFFICIENT_BUFFER
  eng "Buffer too small to hold registration challenge response."

ER_AUTHENTICATION_PLUGIN_AUTH_DATA_CORRUPT
  eng "FIDO device authenticator data corrupt."

ER_AUTHENTICATION_PLUGIN_SIGNATURE_CORRUPT
  eng "FIDO device signature corrupt."

ER_AUTHENTICATION_PLUGIN_VERIFY_SIGNATURE_FAILED
  eng "Signature verification failed during authentication."

ER_AUTHENTICATION_PLUGIN_OOM
  eng "Out of memory."

ER_AUTHENTICATION_PLUGIN_LOG
  eng "Can't initialize logging service".

ER_WARN_REPLICA_GTID_ONLY_AND_GTID_MODE_NOT_ON
  eng "Replication channel '%.192s' is configured with GTID_ONLY=1, which is invalid when GTID_MODE <> ON. If you intend to disable GTIDs in the replication topology, change GTID_ONLY to 0."

ER_WARN_L_DISABLE_GTID_ONLY_WITH_SOURCE_AUTO_POS_INVALID_POS
  eng "The replication positions relative to the source may be out-of-date on channel '%.192s', due to the use of GTID_ONLY=1. The out-of-date positions can still be used in some cases so, in order to update them, we suggest that you start the replication to receive and apply at least one transaction, which will set the positions to valid values."

ER_RPL_CANNOT_OPEN_RELAY_LOG
  eng "Could not open relay log: %s"

ER_AUTHENTICATION_OCI_PLUGIN_NOT_INITIALIZED
  eng "Authentication plugin not initialized."

ER_AUTHENTICATION_OCI_PRIVATE_KEY_ERROR
  eng "Cannot use the generated private key file."

ER_AUTHENTICATION_OCI_DOWNLOAD_PUBLIC_KEY
  eng "Unavailable public key with fingerprint %s for user %s in tenancy %s ."

ER_AUTHENTICATION_OCI_IMDS
  eng "Cannot obtain the OCI configuration from the IMDS service."

ER_AUTHENTICATION_OCI_IAM
  eng "Cannot initialize the IAM service."

ER_AUTHENTICATION_OCI_INVALID_AUTHENTICATION_STRING
  eng "Invalid authentication string details for user: `%s`@`%s`."

ER_AUTHENTICATION_OCI_NO_MATCHING_GROUPS
  eng "None of the groups returned by IAM matches any of the entries from authentication string."

ER_AUTHENTICATION_OCI_NO_GROUPS_FOUND
  eng "User is not part of any groups. However, account is configured to use group mapping."

ER_AUTHENTICATION_OCI_NONCE
  eng "Received OpenSSL error: %s while authenticating user %s with fingerprint %s in tenancy %s ."

ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_1
  eng "%s: Warning Level 1 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB"

ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_2
  eng "%s: Warning Level 2 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB"

ER_HEALTH_WARNING_MEMORY_USAGE_LEVEL_3
  eng "%s: Warning Level 3 (%llu MiB): available=%llu MiB, total=%llu MiB, used=%.2f%%, mysqld=%llu MiB"

ER_GRP_RPL_SET_SINGLE_CONSENSUS_LEADER
  eng "The member %s:%u, with UUID: %s, was set as the single preferred consensus leader."

ER_GRP_RPL_ERROR_SET_SINGLE_CONSENSUS_LEADER
  eng "Something went wrong trying to set the member %s:%u, with UUID: %s, as the single preferred consensus leader. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the preferred consensus leader matches the current primary. If not, consider electing a different primary to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong."

ER_GRP_RPL_SET_MULTI_CONSENSUS_LEADER
  eng "All members were set as consensus leaders."

ER_GRP_RPL_ERROR_SET_MULTI_CONSENSUS_LEADER
  eng "Something went wrong trying to set all members as consensus leaders. Please query the performance_schema.replication_group_communication_information table to see whether the operation took effect, i.e. whether the consensus leaders match all members. If not, consider resetting the group communication protocol to a version < 8.0.22, or switch to single-primary mode and back again to multi-primary mode, to try again. Please check the error log and GCS_DEBUG_TRACE for more information that may help understanding what went wrong."

ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_GRP
  eng "This member is configured with a group_replication_paxos_single_leader option value of '%d' that is different from the group's value ('%d'). This member will now exit the group."

ER_MFA_USER_ATTRIBUTES_CORRUPT
  eng "Invalid and/or corrupted multi factor authentication methods in User_attributes column in mysql.user table. \"%s\"."

ER_MFA_PLUGIN_NOT_LOADED
  eng "Plugin \'%-.192s\' is not loaded; Ignoring user"

ER_WARN_DEPRECATED_CHARSET_OPTION
  eng "%s: The character set %s is deprecated and will be removed in a future release. Please consider using %s instead."

ER_WARN_DEPRECATED_COLLATION_OPTION
  eng "%s: '%-.64s' is a collation of the deprecated character set %s. Please consider using %s with an appropriate collation instead."

ER_REGEXP_MISSING_ICU_DATADIR
  eng "Missing data directory for ICU regular expressions: %s."

ER_IB_WARN_MANY_NON_LRU_FILES_OPENED
  eng "More than 90%% of files opened out of the innodb_open_files limit are files that are not easy to close. The performance of system may degrade. Consider increasing value of the innodb_open_files system variable. There are %zu such files opened out of the total limit for all files opened of %zu."

ER_IB_MSG_TRYING_TO_OPEN_FILE_FOR_LONG_TIME
  eng "Trying to open a file for %lld seconds. Configuration only allows for %zu open files. Consider setting innobase_open_files higher."

ER_GLOBAL_CONN_LIMIT
  eng "Connection closed. Global connection memory limit %llu bytes exceeded. Consumed %llu bytes."

ER_CONN_LIMIT
  eng "Connection closed. Connection memory limit %llu bytes exceeded. Consumed %llu bytes."

ER_WARN_AUDIT_LOG_DISABLED
  eng "Audit Log is disabled. Enable it with audit_log_disable = false."

ER_INVALID_TLS_VERSION
  eng "Option --tls-version or --admin-tls-version is set to an invalid value %s."

ER_RPL_RELAY_LOG_RECOVERY_GTID_ONLY
  eng "Relay log recovery on channel with GTID_ONLY=1. The channel will switch to a new relay log and the GTID protocol will be used to replicate unapplied transactions."

ER_KEYRING_OKV_STANDBY_SERVER_COUNT_EXCEEDED
  eng "Number of STANDBY_SERVER values exceeded maximum limit of 64."

ER_WARN_MIGRATION_EMPTY_SOURCE_KEYRING
  eng "Source keyring does not have any keys to migrate."

ER_WARN_CANNOT_PERSIST_SENSITIVE_VARIABLES
  eng "Cannot persist SENSITIVE system variables because keyring component support is unavailable and persist_sensitive_variables_in_plaintext is set to OFF. Please make sure that keyring services are active and required keys are available."

ER_CANNOT_INTERPRET_PERSISTED_SENSITIVE_VARIABLES
  eng "Cannot interpret persisted SENSITIVE system variables. Please make sure that keyring services are active and required keys are available."

ER_PERSISTED_VARIABLES_KEYRING_SUPPORT_REQUIRED
  eng "Keyring has to be loaded through manifest file in order to support secure storage for persisted variables"

ER_PERSISTED_VARIABLES_MASTER_KEY_NOT_FOUND
  eng "Could not find master key %s in keyring"

ER_PERSISTED_VARIABLES_MASTER_KEY_CANNOT_BE_GENERATED
  eng "A new master key %s could not be generated"

ER_PERSISTED_VARIABLES_ENCRYPTION_FAILED
  eng "Failed to encrypt %s using %s"

ER_PERSISTED_VARIABLES_DECRYPTION_FAILED
  eng "Failed to decrypt %s using %s"

ER_PERSISTED_VARIABLES_LACK_KEYRING_SUPPORT
  eng "Persisting SENSITIVE variables in encrypted form requires keyring component loaded through manifest file."

ER_MY_MALLOC_USING_JEMALLOC
  eng "Using jemalloc.dll for my_malloc and ut::malloc etc."

ER_MY_MALLOC_USING_STD_MALLOC
  eng "%s."

ER_MY_MALLOC_LOADLIBRARY_FAILED
  eng "%s."

ER_MY_MALLOC_GETPROCADDRESS_FAILED
  eng "%s."

ER_ACCOUNT_WITH_EXPIRED_PASSWORD
  eng "Password for the account '%-.48s'@'%-.64s' has expired. To log in, either change it using a client that supports expired passwords or send the change request to an administrator."

ER_THREAD_POOL_PLUGIN_STARTED
  eng "Thread pool plugin started successfully with parameters: %s"

ER_THREAD_POOL_DEDICATED_LISTENERS_INVALID
  eng "thread_pool_dedicated_listeners cannot be set unless thread_pool_max_transactions_limit > 0"

ER_IB_DBLWR_BYTES_INFO
  eng "%s"

ER_IB_RDBLWR_BYTES_INFO
  eng "%s"

ER_IB_MSG_LOG_FILE_IS_EMPTY
  eng "The redo log file %s is empty, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file or try recovering without the redo files, in read-only mode, by providing --innodb-force-recovery=6."

ER_IB_MSG_LOG_FILE_TOO_SMALL
  eng "The redo log file %s is smaller than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file."

ER_IB_MSG_LOG_FILE_TOO_BIG
  eng "The redo log file %s is larger than %llu bytes, which indicates it was not generated by InnoDB or become corrupted. Please restore the correct file."

ER_IB_MSG_LOG_FILE_HEADER_READ_FAILED
  eng "Failed to read header of the redo log file %s"

ER_IB_MSG_LOG_INIT_DIR_NOT_EMPTY_WONT_INITIALIZE
  eng "--initialize specified but the redo log directory %s has redo log files inside. Aborting."

ER_IB_MSG_LOG_INIT_DIR_LIST_FAILED
  eng "Failed to list redo log files in the redo log directory %s"

ER_IB_MSG_LOG_INIT_DIR_MISSING_SUBDIR
  eng "Neither found %s subdirectory, nor %s* files in %s"

ER_IB_MSG_LOG_FILES_CREATED_BY_CLONE_AND_READ_ONLY_MODE
  eng "Cannot restore cloned data directory, InnoDB running in read-only mode!"

ER_IB_MSG_LOG_WRITER_WRITE_FAILED
  eng "Error %d encountered when writing to the redo log file: %s."

OBSOLETE_ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE
  eng "Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity."

ER_IB_MSG_RECOVERY_CHECKPOINT_OUTSIDE_LOG_FILE
  eng "Found checkpoint LSN %llu in a redo log file %s, but the file represents range of LSN values [%llu, %llu), so the file is corrupted."

ER_IB_MSG_LOG_WRITER_ENTERED_EXTRA_MARGIN
  eng "Redo log is running out of free space, pausing user threads... Consider increasing innodb_redo_log_capacity."

ER_IB_MSG_LOG_WRITER_EXITED_EXTRA_MARGIN
  eng "Redo log reclaimed some free space, resuming user threads."

ER_IB_MSG_LOG_PARAMS_FILE_SIZE_UNUSED
  eng "Ignored deprecated configuration parameter innodb_log_file_size. Used innodb_redo_log_capacity instead."

ER_IB_MSG_LOG_PARAMS_N_FILES_UNUSED
  eng "Ignored deprecated configuration parameter innodb_log_files_in_group. Used innodb_redo_log_capacity instead."

ER_IB_MSG_LOG_UPGRADE_FORCED_RECV
  eng "Cannot upgrade format (v%lu) of redo log files when innodb-force-recovery > 0."

ER_IB_MSG_LOG_UPGRADE_IN_READ_ONLY_MODE
  eng "Cannot upgrade format (v%lu) of redo log files in read-only mode (--innodb-read-only)."

ER_IB_MSG_LOG_UPGRADE_CLONED_DB
  eng "Cannot upgrade format (v%lu) of redo log files on cloned data directory. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."

ER_IB_MSG_LOG_UPGRADE_UNINITIALIZED_FILES
  eng "Cannot upgrade format (v%lu) of redo log files because they are marked as uninitialized. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."

ER_IB_MSG_LOG_UPGRADE_CORRUPTION__UNEXPECTED
  eng "Cannot upgrade format (v%lu) of redo log files when the redo log is corrupted. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."

OBSOLETE_ER_IB_MSG_LOG_UPGRADE_NON_PERSISTED_DD_METADATA
  eng "Cannot upgrade format (v%lu) of redo log files when there is non-persisted DD metadata in redo. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."

OBSOLETE_ER_IB_MSG_LOG_UPGRADE_FLUSH_FAILED__UNEXPECTED
  eng "Cannot upgrade format (v%lu) of redo log files, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."

OBSOLETE_ER_IB_MSG_LOG_FILES_RESIZE_ON_START_FAILED__UNEXPECTED
  eng "Failed to resize the redo log synchronously, because InnoDB failed to reach state in which redo log is logically empty. Please use an older version of MySQL - recover and shutdown (with innodb-fast-shutdown < 2)."

ER_IB_MSG_LOG_FILE_FOREIGN_UUID
  eng "The redo log file %s comes from other data directory than redo log file %s."

ER_IB_MSG_LOG_FILE_INVALID_START_LSN
  eng "The redo log file %s has invalid start_lsn %llu."

ER_IB_MSG_LOG_FILE_INVALID_LSN_RANGES
  eng "The redo log file %s has start_lsn %llu but expected %llu (end_lsn of the previous redo log file)."

ER_IB_MSG_LOG_FILE_MISSING_FOR_ID
  eng "Missing redo log file %s (with start_lsn = %llu)."

ER_IB_MSG_LOG_CHECKPOINT_FOUND
  eng "The latest found checkpoint is at lsn = %llu in redo log file %s."

ER_IB_MSG_LOG_FILES_CAPACITY_CHANGED
  eng "User has set innodb_redo_log_capacity to %lluM."

ER_IB_MSG_LOG_FILES_RESIZE_REQUESTED
  eng "Redo log has been requested to resize from %lluM to %lluM."

ER_IB_MSG_LOG_FILES_RESIZE_CANCELLED
  eng "Redo log resize has been cancelled."

ER_IB_MSG_LOG_FILES_RESIZE_FINISHED
  eng "Redo log has been resized to %lluM."

ER_IB_MSG_LOG_FILES_UPGRADE
  eng "Upgrading redo log: %lluM, LSN=%llu."

ER_IB_MSG_LOG_FILE_MARK_CURRENT_AS_INCOMPLETE
  eng "Marked the current redo log file %s as incomplete."

ER_IB_MSG_LOG_FILE_REMOVE_FAILED
  eng "Failed to remove redo log file %s."

ER_IB_MSG_LOG_FILE_RENAME_ON_CREATE_FAILED
  eng "Failed to rename %s when creating redo log file %s (error: %d)"

ER_IB_MSG_LOG_FILES_CREATED_BY_UNKNOWN_CREATOR
  eng "Redo log files created by unknown creator %s."

ER_IB_MSG_LOG_FILES_FOUND_MISSING
  eng "Found existing redo log files, but at least one is missing. It is unknown if recovery could reach physically consistent state. Please consider restoring from backup or providing --innodb-force-recovery > 0."

ER_IB_MSG_LOG_FILE_FORMAT_TOO_NEW
  eng "Found redo log file %s which has format (v%lu) and is stored outside #innodb_redo."

ER_IB_MSG_LOG_FILE_FORMAT_TOO_OLD
  eng "Found redo log file %s which has format (v%lu) and is stored inside #innodb_redo."

ER_IB_MSG_LOG_FILE_DIFFERENT_FORMATS
  eng "Found redo log files with different formats: %s has format v%lu, %s has format v%lu."

ER_IB_MSG_LOG_PRE_8_0_30_MISSING_FILE0
  eng "Missing ib_logfile0 in the directory %s."

ER_IB_MSG_LOG_PFS_ACQUIRE_SERVICES_FAILED
  eng "Failed to initialize services required to handle redo log PFS tables."

ER_IB_MSG_LOG_PFS_CREATE_TABLES_FAILED
  eng "Failed to create redo log PFS tables."

ER_IB_MSG_LOG_FILE_TRUNCATE
  eng "Truncating redo log file %s..."

ER_IB_MSG_LOG_FILE_UNUSED_RESIZE_FAILED
  eng "Failed to resize unused redo log file %s to %llu MB (%s)."

ER_IB_MSG_LOG_FILE_UNUSED_REMOVE_FAILED
  eng "Failed to remove unused redo log file %s."

ER_IB_MSG_LOG_FILE_UNUSED_RENAME_FAILED
  eng "Failed to rename unused redo log file %s to %s."

ER_IB_MSG_LOG_FILE_UNUSED_MARK_AS_IN_USE_FAILED
  eng "Failed to mark unused redo log file %s as in use (by renaming to %s)."

ER_IB_MSG_LOG_FILE_MARK_AS_UNUSED_FAILED
  eng "Failed to mark redo log file %s as unused (by renaming to %s)."

ER_IB_MSG_LOG_PARAMS_DEDICATED_SERVER_IGNORED
  eng "Option innodb_dedicated_server is ignored for innodb_redo_log_capacity, because innodb_redo_log_capacity, innodb_log_file_size or innodb_log_files_in_group is specified explicitly. Redo log capacity: %lluM."

ER_IB_MSG_LOG_PARAMS_LEGACY_USAGE
  eng "Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=%llu. Please use innodb_redo_log_capacity instead."

ER_GRP_RPL_FAILED_TO_LOG_VIEW_CHANGE
  eng "This member was unable to log the View_change_log_event into the binary log, hence it will leave the group. Please check that there is available disk space and add the member back to the group."

ER_BINLOG_CRASH_RECOVERY_MALFORMED_LOG
  eng "Found invalid event sequence while recovering from binary log file '%s', between positions %llu and %llu: %s. The recovery process was stopped early and no transaction was recovered. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the binary log or, to release possibly acquired locks, disable the binary log during server recovery. Note that disabling the binary log may lead to loss of transactions that were already acknowledged as successful to client connections and may have been replicated to other servers in the topology."

ER_BINLOG_CRASH_RECOVERY_ERROR_RETURNED_SE
  eng "Storage engines failed to recover one or more transactions. The recovery process was stopped early, check previous messages for the details on failed transactions. Side effects may be transactions in an inconsistent state between the binary log and the storage engines, or transactions kept by storage engines in a prepared state (possibly holding locks). Either fix the issues with the storage engine (out-of-memory, no disk space, etc) or, to release possibly acquired locks held by XA transactions, disable the binary log during server recovery and check consistency between storage engines and binary log files."

ER_BINLOG_CRASH_RECOVERY_ENGINE_RESULTS
  eng "Crash recovery finished in %s engine. %s"

ER_BINLOG_CRASH_RECOVERY_COMMIT_FAILED
  eng "Failed to commit %s in %s, with failure code %s."

ER_BINLOG_CRASH_RECOVERY_ROLLBACK_FAILED
  eng "Failed to rollback %s in %s, with failure code %s."

ER_BINLOG_CRASH_RECOVERY_PREPARE_FAILED
  eng "Failed to prepare %s in %s, with failure code %s."
ER_COMPONENT_EE_SYS_VAR_REGISTRATION_FAILURE
  eng "Cannot register variable '%s'. Please check if it is not already registered by another component."

ER_COMPONENT_EE_SYS_VAR_DEREGISTRATION_FAILURE
  eng "Cannot unregister variable '%s'. Please check if it was registered properly in the first place."

ER_COMPONENT_EE_FUNCTION_REGISTRATION_FAILURE
  eng "Cannot register function '%s'. Please check if it is not already registered."

ER_COMPONENT_EE_FUNCTION_DEREGISTRATION_FAILURE
  eng "Cannot unregister function '%s'. Please check if it was registered properly in the first place."

ER_COMPONENT_EE_FUNCTION_INVALID_ARGUMENTS
  eng "Invalid arguments to function '%s'. Expected values: %s."

ER_COMPONENT_EE_FUNCTION_INVALID_ALGORITHM
  eng "Invalid algorithm value '%.20s' in function %s."

ER_COMPONENT_EE_FUNCTION_KEY_LENGTH_OUT_OF_RANGE
  eng "Invalid key length '%d' for function '%s' with algorithm '%.20s'. Please provide a value between [%d, %d]."

ER_COMPONENT_EE_FUNCTION_PRIVATE_KEY_GENERATION_FAILURE
  eng "Failed to generate private key of length '%d' with algorithm '%.20s' in function '%s'. More details about the error would have been logged before this message."

ER_COMPONENT_EE_FUNCTION_PUBLIC_KEY_GENERATION_FAILURE
  eng "Failed to generate public key with algorithm '%.20s' for given private key in function '%s'. More details about the error would have been logged before this message."

ER_COMPONENT_EE_DATA_LENGTH_OUT_OF_RAGE
  eng "Invalid data length '%d' (in bytes) for function '%s' with algorithm '%.20s'. The maximum support data length for given private key is %d (in bytes)."

ER_COMPONENT_EE_DATA_ENCRYPTION_ERROR
  eng "Could not encrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message."

ER_COMPONENT_EE_DATA_DECRYPTION_ERROR
  eng "Could not decrypt data in function '%s' using algorithm '%.20s'. Data length was '%d' bytes. More details about the error would have been logged before this message."

ER_COMPONENT_EE_DATA_SIGN_ERROR
  eng "Could not sign data in function '%s' using algorithm '%.20s' and digest type '%.20s'. More details about the error would have logged before this message."

ER_COMPONENT_EE_OPENSSL_ERROR
  eng "Received OpenSSL error in function '%s' for algorithm '%s': '%s'"

ER_COMPONENT_EE_INSUFFICIENT_LENGTH
  eng "In function '%s' with algorithm '%s': insufficient output buffer length '%zu'. Required length '%zu'."

ER_SYSTEMD_NOTIFY_DEBUG
  eng "%s%s"

ER_TMP_SESSION_FOR_VAR
  eng "Setting session values for system variables only makes sense in a user session (failed to set '%.256s')."

ER_BUILD_ID
  eng "BuildID[sha1]=%s"

ER_THREAD_POOL_CANNOT_REGISTER_DYNAMIC_PRIVILEGE
  eng "Failed to register dynamic privilege %s."

ER_IB_MSG_LOG_WRITER_WAIT_ON_CONSUMER
  eng "Redo log writer is waiting for %s redo log consumer which is currently reading LSN=%llu preventing reclamation of subsequent portion of the redo log. Consider increasing innodb_redo_log_capacity."

ER_CONDITIONAL_DEBUG
  eng "%s"

ER_IB_MSG_PARSE_OLD_REDO_INDEX_VERSION
  eng "Recovery: Generating index information for INSTANT DDL Table in 8.0.29 format"

OBSOLETE_ER_RES_GRP_FAILED_TO_SWITCH_RESOURCE_GROUP
  eng "Failed to switch resource group. %s".

OBSOLETE_ER_RES_GRP_SWITCH_FAILED_COULD_NOT_ACQUIRE_GLOBAL_LOCK
  eng "Failed to switch resource group. Could not acquire resource groups global lock."

OBSOLETE_ER_RES_GRP_SWITCH_FAILED_COULD_NOT_ACQUIRE_LOCK
  eng "Failed to switch resource group. Could not acquire lock on resource group %s."

OBSOLETE_ER_RES_GRP_SWITCH_FAILED_UNABLE_TO_APPLY_RES_GRP
  eng "Failed to switch resource group. Unable to apply resource group controller %s."

ER_IB_MSG_CLEAR_INSTANT_DROP_COLUMN_METADATA
  eng "Failed to clear instant drop column metadata for table %s"

ER_COMPONENT_KEYRING_OCI_OPEN_KEY_FILE
  eng "Cannot open signing key file %s."

ER_COMPONENT_KEYRING_OCI_CREATE_PRIVATE_KEY
  eng "Out of memory! Cannot create private key."

ER_COMPONENT_KEYRING_OCI_READ_KEY_FILE
  eng "Cannot read signing key file %s."

ER_NOTE_COMPONENT_KEYRING_OCI_MISSING_NAME_OR_TYPE
  eng "Incomplete key: missing Name/Type for the Key: %s."

ER_WARN_COMPONENT_KEYRING_OCI_DUPLICATE_KEY
  eng "Duplicate key found in keyring with Name: %s and Owner: %s."

ER_KEYRING_OCI_PARSE_JSON
  eng "Error parsing JSON response %s."

ER_KEYRING_OCI_INVALID_JSON
  eng "Invalid JSON response!"

ER_KEYRING_OCI_HTTP_REQUEST
  eng "HTTP request failed with error: '%s'"

ER_THREAD_POOL_SYSVAR_CHANGE
  eng "Variable thread_pool.%s was updated: %s"

ER_STACK_BACKTRACE
  eng "%s"

ER_IB_MSG_BUF_POOL_RESIZE_COMPLETE_CUR_CODE
  eng "Status code %u: Completed"

ER_IB_MSG_BUF_POOL_RESIZE_PROGRESS_UPDATE
  eng "Status code %u: %u%% complete"

ER_IB_MSG_BUF_POOL_RESIZE_CODE_STATUS
  eng "Status code %u: %s"

ER_THREAD_POOL_QUERY_THREADS_PER_GROUP_INVALID
  eng "Invalid value set to thread_pool_query_threads_per_group. Valid value range is %u - %u."

ER_THREAD_POOL_QUERY_THRS_PER_GRP_EXCEEDS_TXN_THR_LIMIT
  eng "Query threads count(%u) exceeds transaction threads limit(%u) per group. Please use query threads count per group smaller or equal to max transaction threads limit per group"

ER_IB_MSG_INVALID_PAGE_TYPE
  eng "Found page type mismatch. Expected %u, found %u, in page: space_id=%lu page_no= %lu"

ER_IB_PARALLEL_READER_WORKER_INFO
  eng "preader: space_id=%zu, table=%s, index=%s, scan_ctx=%zu, ctx=%zu, thread_id=%zu, n_threads=%zu"

ER_IB_BULK_LOAD_SUBTREE_INFO
  eng "bulkload: space_id=%zu, table=%s, index=%s, height=%zu, n_extents=%zu, n_pages=%zu"

ER_IB_BULK_FLUSHER_INFO
  eng "bulkflusher: sleep_count=%zu, sleep_duration=%zu milliseconds, total_sleep=%zu milliseconds, pages_flushed=%zu"

ER_IB_BUFFER_POOL_OVERUSE
  eng "%s: Over 67 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics."

ER_IB_BUFFER_POOL_FULL
  eng "%s: Over 95 percent of the buffer pool (curr_size=%zu MB) is occupied by lock heaps or the adaptive hash index or BUF_BLOCK_MEMORY pages. Check that your transactions do not set too many row locks. Maybe you should make the buffer pool bigger?. We intentionally generate a seg fault to print a stack trace on Linux!";

ER_IB_DUPLICATE_KEY
  eng "%s: table=%s, index=%s, n_uniq=%zu, n_fields=%zu, lhs=(%s), rhs=(%s)"

ER_REPLICATION_INCOMPATIBLE_TABLE_WITH_GIPK
  eng "Failed to apply row event with %d columns, originating from a server of version %s on table '%-.192s.%-.192s', which has %d columns, one of which is a generated implicit primary key. Replication is unsupported when the source server is older than 8.0.30, the replica table has a generated implicit primary key, and there is a difference in column count, not counting the replica's generated implicit primary key. Align the table schemas on source and replica, and restart replication."

ER_BULK_EXECUTOR_INFO
  eng "Bulk executor: %s"

ER_BULK_LOADER_INFO
  eng "Bulk loader: %s"

ER_BULK_LOADER_FILE_CONTAINS_LESS_LINES_THAN_IGNORE_CLAUSE_LOG
  eng "The first file being loaded contained less lines than the ignore clause"

ER_BULK_READER_INFO
  eng "Bulk reader: %s"

ER_BULK_READER_LIBCURL_INIT_FAILED_LOG
  eng "Bulk reader failed to initialize libcurl"

ER_BULK_READER_LIBCURL_ERROR_LOG
  eng "Bulk reader got libcurl error: %s"

ER_BULK_READER_SERVER_ERROR_LOG
  eng "Bulk reader got error response from server: %ld"

ER_BULK_READER_COMMUNICATION_ERROR_LOG
  eng "Bulk reader got error in communication with source server, check the error log for additional details"

ER_BULK_PARSER_MISSING_ENCLOSED_BY_LOG
  eng "Missing ENCLOSED BY character at row %ld in file %s. Add OPTIONALLY to the ENCLOSED BY clause to allow this input."

ER_BULK_PARSER_ROW_BUFFER_MAX_TOTAL_COLS_EXCEEDED_LOG
  eng "The number of input columns that need to be buffered for parsing exceeded predefined buffer max size for file '%s'."

ER_BULK_PARSER_COPY_BUFFER_SIZE_EXCEEDED_LOG
  eng "The column data that needed to be copied due to escaped characters exceeded the size of the internal copy buffer for file '%s'."

ER_BULK_PARSER_UNEXPECTED_END_OF_INPUT_LOG
  eng "Unexpected end of input found at row %ld in file '%s'. Data for some columns is missing."

ER_BULK_PARSER_UNEXPECTED_ROW_TERMINATOR_LOG
  eng "Unexpected row terminator found at row %ld in file '%s'. Data for some columns is missing."

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_ENDING_ENCLOSED_BY_LOG
  eng "Unexpected characters after ending ENCLOSED BY character found at row %ld in file '%s'."

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_NULL_ESCAPE_LOG
  eng "Unexpected characters after NULL escape (\N) found at row %ld in file '%s'."

ER_BULK_PARSER_UNEXPECTED_CHAR_AFTER_COLUMN_TERMINATOR_LOG
  eng "Unexpected characters after column terminator found at row %ld in file '%s'."

ER_BULK_PARSER_INCOMPLETE_ESCAPE_SEQUENCE_LOG
  eng "Unexpected end of input found at row %ld in file '%s' resulting in incomplete escape sequence."

ER_LOAD_BULK_DATA_WRONG_VALUE_FOR_FIELD_LOG
  eng "Incorrect %-.32s value: '%-.128s' for column '%-.192s' at row %ld in file '%-.192s'"

ER_LOAD_BULK_DATA_WARN_NULL_TO_NOTNULL_LOG
  eng "NULL supplied to NOT NULL column '%s' at row %ld in file '%-.192s'"

ER_IB_BULK_LOAD_THREAD_FAIL
   eng "%s: LOAD BULK DATA thread failure (err=%lu), table=%s, index=%s"

ER_IB_BULK_LOAD_MERGE_FAIL
   eng "%s: Failed to merge sub-trees in LOAD BULK DATA, table=%s, index=%s, details=%s"

ER_IB_LOAD_BULK_CONCURRENCY_REDUCED
   eng "LOAD BULK DATA: Buffer pool size is %zu. Reducing concurrency from %zu to %zu. table=%s."

ER_PLUGIN_EXCEPTION_OPERATION_FAILED
   eng "C++ Exception caught while %s the %s plugin: [%s]"

ER_REQUIRE_TABLE_PRIMARY_KEY_CHECK_GENERATE_WITH_GR_IN_REPO
   eng "Replication configuration appears to be corrupted. On Group Replication channel '%s', setting REQUIRE_TABLE_PRIMARY_KEY_CHECK to 'GENERATE' is not allowed. Run RESET REPLICA ALL to reset it."

ER_CHECK_TABLE_INSTANT_VERSION_BIT_SET
   eng "Record has both instant and version bit set."

ER_GRP_RPL_PAXOS_SINGLE_LEADER_DIFF_FROM_OLD_GRP
  eng "This member is configured with a group_replication_paxos_single_leader option value of 1 and it is trying to join a group with Communication Protocol Version below 8.0.27. In order to join this group, group_replication_paxos_single_leader value must be configured to the value 0. This member will now exit the group."

ER_IB_WRN_IGNORE_REDO_LOG_CAPACITY
  eng "Ignored the innodb-redo-log-capacity option in the Innodb read-only mode. Server is using active redo log files."

ER_IB_PRIMARY_KEY_IS_INSTANT
  eng "Unexpected INSTANTLY Added / Dropped column: '%s' at position %lu for Table '%s', Index '%s' while getting Primary Key for row logging"

ER_THREAD_POOL_IDLE_CONNECTION_CLOSED
   eng "%s"

ER_IB_HIDDEN_NAME_CONFLICT
   eng "Column name %s and internally generated INSTANT DROP column name %s is causing a conflict."

ER_IB_DICT_INVALID_COLUMN_POSITION
   eng "Field number: %llu too large, Total fields in Record: %zu."

ER_IB_DICT_LOG_TABLE_INFO
   eng "%s"

ER_RPL_ASYNC_NEXT_FAILOVER_CHANNEL_SELECTED
  eng "The connection has timed out after %lu retries connecting to '%s@%s:%d'%s, and therefore the MySQL server is going to attempt an asynchronous replication connection failover, to '%s@%s:%d'"

ER_RPL_REPLICA_SOURCE_UUID_HAS_NOT_CHANGED
  eng "The Replica which was connected to source \'%s:%d\', is now connected to new source \'%s:%d\', but still has the same server_uuid %s."

ER_RPL_REPLICA_SOURCE_UUID_HAS_CHANGED_HOST_PORT_UNCHANGED
  eng "The server_uuid for source server \'%s:%d\' has changed from %s to %s. This should not happen unless you have changed it manually."

ER_RPL_REPLICA_SOURCE_UUID_HOST_PORT_HAS_CHANGED
  eng "The source server has changed from \'%s:%d\' with server_uuid %s, to \'%s:%d\' with server_uuid %s."

ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_FILE_BASED
  eng "Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting replication from file '%s', position '%s'."

ER_RPL_REPLICA_CONNECTED_TO_SOURCE_RPL_STARTED_GTID_BASED
  eng "Replica receiver thread%s: connected to source \'%s@%s:%d\' with server_uuid=%s, server_id=%d. Starting GTID-based replication."

ER_IB_INDEX_LOADER_DONE
   eng "Loader::build_all(): Completed building %zu indexes for old_table=%s, new_table=%s, err=%zu."

ER_IB_INDEX_BUILDER_DONE
   eng "Builder::finish(): Completed building index=%s of table=%s, err=%zu."

ER_WARN_DEPRECATED_USER_DEFINED_COLLATIONS_OPTION
   eng "%s: '%s' is a user defined collation. User defined collations are deprecated and will be removed in a future release. Consider using a compiled collation instead."

ER_IB_INDEX_BUILDER_INIT
   eng "Builder::init(): Initialize for building index=%s of table=%s, n_threads=%zu, sort buffer size=%zu bytes, i/o buffer size=%zu bytes."

ER_IB_SELECT_COUNT_STAR
   eng "SELECT COUNT(*) FROM table=%s, n_threads=%zu, n_partitions=%zu."

ER_IB_INDEX_LOG_VERSION_MISMATCH
   eng "Index log version %u did not match. Max index version is %u. Recovery can't continue. Please make sure server is not starting up with the datadir generated in future version."

ER_WARN_COMPONENTS_INFRASTRUCTURE_MANIFEST_MULTIPLE_KEYRING
   eng "Multiple keyring component URNs '%s' found in manifest file '%s'. Only one keyring component can be loaded at a time."

ER_GRP_RPL_HAS_STARTED
  eng "Plugin 'group_replication' has been started."

ER_CHECK_TABLE_MIN_REC_FLAG_SET
   eng "Minimum record flag is wrongly set to rec on page '%lu' at level '%lu' for index '%s' of table '%s'."

ER_CHECK_TABLE_MIN_REC_FLAG_NOT_SET
   eng "Minimum record flag is not set to first rec on page '%lu' at level '%lu' for index '%s' of table '%s'."

ER_NOTE_COMPONENT_SLOT_REGISTRATION_SUCCESS
  eng "Successfully registered slot '%d' for component '%s'."

ER_NOTE_COMPONENT_SLOT_DEREGISTRATION_SUCCESS
  eng "Successfully de-registered slot '%d' from component '%s'."

ER_WARN_CANNOT_FREE_COMPONENT_DATA_DEALLOCATION_FAILED
  eng "Cannot free resources stored by component '%s' in thread with ID: '%d'. Component failed to free required resources."

ER_IB_RESURRECT_TRX_INSERT
  eng "Transaction ID: %lu found for resurrecting inserts"

ER_IB_RESURRECT_TRX_UPDATE
  eng "Transaction ID: %lu found for resurrecting updates"

ER_IB_RESURRECT_IDENTIFY_TABLE_TO_LOCK
  eng "Identified table ID: %lu to acquire lock"

ER_IB_RESURRECT_ACQUIRE_TABLE_LOCK
  eng "Acquired lock on table ID: %lu, name: %s"

ER_IB_RESURRECT_RECORD_PROGRESS
  eng "Records read: %lu - Pages read: %lu"

ER_IB_RESURRECT_RECORD_COMPLETE
  eng "Total records resurrected: %lu - Total pages read: %lu - Total tables acquired: %lu"

ER_IB_RESURRECT_TRX_INSERT_COMPLETE
  eng "Resurrected %lu transactions doing inserts."

ER_IB_RESURRECT_TRX_UPDATE_COMPLETE
  eng "Resurrected %lu transactions doing updates."

ER_AUTHENTICATION_OCI_INVALID_TOKEN
  eng "Invalid security token provided by '%s' for '%s'@'%s': %s."

ER_AUTHENTICATION_OCI_TOKEN_DETAILS_MISMATCH
  eng "Unknown user/tenancy (user: %s tenancy: %s) found in security token provided by '%s' for '%s'@'%s'."

ER_AUTHENTICATION_OCI_TOKEN_NOT_VERIFIED
  eng "Verification failed for security token provided by '%s' for '%s'@'%s' : %s."

ER_AUTHENTICATION_OCI_DOWNLOAD_IDDP_PUBLIC_KEY
  eng "Could not download IDDP Public key. Please check if security token provided by '%s' for '%s'@'%s' is valid."

OBSOLETE_ER_AUTHENTICATION_OCI_NO_MATCHING_GROUPS_IN_TOKEN
  eng "None of the groups extracted from security token matches any of the entries from authentication string."

ER_SYS_VAR_REGISTRATION
  eng "Cannot register variable '%s'. Please check if it is not already registered by another component."

ER_SYS_VAR_DEREGISTRATION
  eng "Cannot unregister variable '%s'. Please check if it was registered properly in the first place."

ER_UDF_REGISTRATION
  eng "Cannot register function '%s'. Please check if it is not already registered by another component."

ER_UDF_DEREGISTRATION
  eng "Cannot unregister function '%s'. Please check if it was registered properly in the first place."

ER_PRIVILEGE_REGISTRATION
  eng "Cannot register privilege '%s'. Please check if it is not already registered."

ER_PRIVILEGE_DEREGISTRATION
  eng "Cannot unregister privilege '%s'. Please check if it was registered properly in the first place."

ER_UDF_EXEC_FAILURE
  eng "Error while executing UDF %s."

ER_UDF_EXEC_FAILURE_REASON
  eng "Error while executing UDF %s: %s."

ER_COMPONENT_SERVICE_CALL
  eng "%s failed."

ER_COMPONENT_SERVICE_CALL_RESULT
  eng "%s failed with %u."

ER_COMPONENT_LOCK
  eng "Lock failed at %s : %u."

ER_COMPONENT_UNLOCK
  eng "Lock from %s : %u failed to unlock."

ER_COMPONENT_MASKING_OTHER_ERROR
  eng "Masking component error: '%s'."

ER_COMPONENT_MASKING_ABI
  eng "%s failed."

ER_COMPONENT_MASKING_ABI_REASON
  eng "%s failed because %s."

ER_COMPONENT_MASKING_RANDOM_CREATE
  eng "Creation of random context failed."

ER_COMPONENT_MASKING_RANDOM_CREATE_REASON
  eng "Creation of random context failed because %s."

ER_COMPONENT_MASKING_CANNOT_ACCESS_TABLE
  eng "Cannot access %s.%s table."

ER_REDUCED_DBLWR_FILE_CORRUPTED
  eng "Cannot recover from detect_only doublewrite buffer as page %u from batch doublewrite file is corrupted."

ER_REDUCED_DBLWR_PAGE_FOUND
  eng "Database page corruption of tablespace %s space_id: %u page_num: %u. Cannot recover it from the doublewrite buffer because it was written in detect_only-doublewrite mode."

ER_CONN_INIT_CONNECT_IGNORED_MFA
  eng "init_connect variable is ignored for user: %s host: %s due to multi-factor registration required sandboxing"

ER_SECONDARY_ENGINE_DDL_FAILED
  eng "Execution of alter table %s %s failed because %s."

ER_THREAD_POOL_CONNECTION_REPORT
   eng "TP conn (port: managed(delta), active, opened, closed, added, dropped): %s"

ER_WARN_SCHEDULED_TASK_RUN_FAILED
   eng "Scheduled run of task %s failed"

ER_AUDIT_LOG_INVALID_FLUSH_INTERVAL_VALUE
   eng "Invalid flush interval specified: %lu. Valid values are 0 (off) or greater than or equal to %d. Adjusting to %d"

ER_LOG_CANNOT_PURGE_BINLOG_WITH_BACKUP_LOCK
  eng "Could not purge binary logs since another session is executing LOCK INSTANCE FOR BACKUP. Wait for that session to release the lock."

ER_CONVERT_MULTI_VALUE
   eng "Multi-values cannot be converted to MySQL format: %s"

ER_IB_DDL_CONVERT_HEAP_NOT_FOUND
  eng "Heap required to convert columns is not present."

ER_SERVER_DOWNGRADE_FROM_VERSION
  eng "MySQL server downgrading from version '%u' to '%u'."

ER_BEYOND_SERVER_DOWNGRADE_THRESHOLD
  eng "Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Target MySQL server version is lower than the server downgrade threshold %u."

ER_BEYOND_SERVER_UPGRADE_THRESHOLD
  eng "Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Target MySQL server version is lower than the server upgrade threshold %u."

ER_INVALID_SERVER_UPGRADE_NOT_LTS
  eng "Invalid MySQL server upgrade: Cannot upgrade from %u to %u. Upgrade to next major version is only allowed from the last LTS release, which version %u is not."

ER_INVALID_SERVER_DOWNGRADE_NOT_PATCH
  eng "Invalid MySQL server downgrade: Cannot downgrade from %u to %u. Downgrade is only permitted between patch releases."

ER_FAILED_GET_DD_PROPERTY
  eng "Failed to get the data dictionary property %s."

ER_FAILED_SET_DD_PROPERTY
  eng "Failed to set the data dictionary property %s."

ER_SERVER_DOWNGRADE_STATUS
  eng "Server downgrade from '%d' to '%d' %s."

ER_INFORMATION_SCHEMA_VERSION_CHANGE
  eng "%s information schema from version %u to %u."

ER_PERFORMANCE_SCHEMA_VERSION_CHANGE
  eng "%s performance schema from version %u to %u."

ER_WARN_DEPRECATED_OR_BLOCKED_CIPHER
   eng "Value for option '%s' contains cipher '%s' that is either blocked or deprecated (and will be removed in a future release). Please refer to the documentation for more details."

ER_IB_MSG_DDL_FAIL_NO_BUILDER
  eng "DDL failed as Builder is already freed. Builder: state=%u, error_state=%u. Index: id=%zu, name='%s', space_id=%u, page=%u. Table: old_name='%s', new_name='%s'."

ER_GRP_RPL_MEMBER_INFO_DOES_NOT_EXIST
  eng "Member identified %s: '%s' does not exist on Group Replication membership during %s."

ER_USAGE_DEPRECATION_COUNTER
  eng "Deprecated '%s' used %s times, last time used '%s'."

ER_WAITING_FOR_NO_CONNECTIONS
  eng "Waiting for %u connections to be closed."

ER_WAITING_FOR_NO_THDS
  eng "Waiting for THDs in partition %u to be closed, %u still left. %u THDs left in total for all partitions."

ER_IB_INDEX_PART_TOO_LONG
  eng "Index %s of %s.%s exceeds limit of %lu bytes per column."

ER_DD_UPDATE_DATADIR_FLAG_FAIL
  eng "Failed to update data directory flag for dd table with tablespace id '%llu' when ibd file for '%s' is moved to new location '%s' during server shutdown"

ER_IB_MSG_FIL_STATE_MOVED_PREV
  eng "%s DD ID: %llu - Tablespace %u, name '%s', found at '%s' outside default data directory, but DD misses info about DATA DIRECTORY"

ER_RPL_KILL_OLD_DUMP_THREAD_ENCOUNTERED
  eng "Upon reconnection with the replica, while initializing the dump thread for %s <%s>, an existing dump thread with the same %s was detected. The source is terminating the previous dump thread (%u), which is normal and expected."

ER_RPL_MTA_ALLOW_COMMIT_OUT_OF_ORDER
  eng "The transaction '%-.192s' will commit out of order with respect to its source to follow the group global order."

ER_CHECK_TABLE_FUNCTIONS
  eng "Can not open table `%s`.`%s`; functions in constraints, partitions, or virtual columns may have failed."

ER_CHECK_TABLE_FUNCTIONS_DETAIL
  eng "%s"

ER_GRP_RPL_CERT_BROADCAST_THREAD_CREATE_FAILED
  eng "Failed to create the Group Replication certifier broadcast thread (THD_certifier_broadcast)."

ER_GRP_RPL_CERT_BROADCAST_THREAD_STARTED
  eng "The Group Replication certifier broadcast thread (THD_certifier_broadcast) started."

ER_GRP_RPL_CERT_BROADCAST_THREAD_STOPPED
  eng "The Group Replication certifier broadcast thread (THD_certifier_broadcast) stopped."

ER_GRP_RPL_APPLIER_THD_KILLED_BY_SQL_KILL
   eng "The group replication applier thread has received KILL request."

ER_IB_MSG_WAITING_ON_LAGGING_REDO_LOG_CONSUMER
  eng "Threads are unable to reserve space in redo log which can't be reclaimed due to the '%s' consumer still lagging behind at LSN = %llu. Consider increasing innodb_redo_log_capacity."

ER_IB_MSG_ABORTING_LOG_ARCHIVER
  eng "The redo log archiver is aborted as it was lagging behind at LSN = %llu and unable to advance for more than 2 seconds. Consider increasing the innodb_redo_log_capacity."

ER_IB_INSTANT_ADD_DROP_COLUMN_NOT_ALLOWED
  eng "Trying to add or drop column(s) in table '%s' for which the current record size is %zu which is more than the maximum allowed size (%zu) for a record. Therefore ADD or DROP column with ALGORITHM = INSTANT is not allowed."

ER_IB_INSTANT_ADD_NOT_POSSIBLE
  eng "Cannot add %zu field(s) in table '%s' because after adding it, the record size would be %zu which is more than the maximum allowed size (%zu) for a record."

ER_IB_WRN_REDO_DISABLED_INFO
  eng "InnoDB redo logging is disabled. All data could be lost in case of a server crash. Current lsn is %llu."

ER_IB_MSG_LOG_WRITER_WAIT_ON_NEW_LOG_FILE_INFO
  eng "Redo log writer is waiting for a new redo log file. Consider increasing innodb_redo_log_capacity. The current log capacity is %llu bytes. The log capacity used is %llu bytes."

# DO NOT add server-to-client messages here;
# they go in messages_to_clients.txt
# in the same directory as this file.
#
# This file is for messages intended for the error log only.
#
# See the FAQ in errmsg_readme.txt in the
# same directory as this file for more
# information.

#
# End of 8.0 error messages intended to be written to the server error log.
#

################################################################################
# Error numbers 50000 to 51999 are reserved. Please do not use them for
# other error messages.
################################################################################
reserved-error-section 50000 51999

# DO NOT append error messages here at the end.
#
#   If you came here to add a message, please read the FAQ in
#   errmsg_readme.txt to see where it should go.
#
#   Messages the server sends to the error log and messages
#   the server sends to its clients go to different places.
#   Messages for different server versions go to different places.
#   Messages that are built into the client library (libmysql/C-API)
#   go into yet a different place.
PK� �\`�7r�c�cdictionary.txtnu�[���0000
1111
123456
12345
password
password1
123456789
12345678
1234567890
abc123
computer
tigger
1234
qwerty
money
carmen
mickey
secret
summer
internet
a1b2c3
service
canada
hello
ranger
shadow
baseball
donald
harley
hockey
letmein
maggie
mike
mustang
snoopy
buster
dragon
jordan
michael
michelle
mindy
patrick
123abc
andrew
bear
calvin
changeme
diamond
fuckme
fuckyou
matthew
miller
tiger
trustno1
alex
apple
avalon
brandy
chelsea
coffee
falcon
freedom
gandalf
green
helpme
linda
magic
merlin
newyork
soccer
thomas
wizard
asdfgh
bandit
batman
boris
butthead
dorothy
eeyore
fishing
football
george
happy
iloveyou
jennifer
jonathan
love
marina
master
missy
monday
monkey
natasha
ncc1701
pamela
pepper
piglet
poohbear
pookie
rabbit
rachel
rocket
rose
smile
sparky
spring
steven
success
sunshine
victoria
whatever
zapata
8675309
amanda
andy
angel
august
barney
biteme
boomer
brian
casey
cowboy
delta
doctor
fisher
island
john
joshua
karen
marley
orange
please
rascal
richard
sarah
scooter
shalom
silver
skippy
stanley
taylor
welcome
zephyr
111111
aaaaaa
access
albert
alexander
andrea
anna
anthony
asdfjkl;
ashley
basketball
beavis
black
bob
booboo
bradley
brandon
buddy
caitlin
camaro
charlie
chicken
chris
cindy
cricket
dakota
dallas
daniel
david
debbie
dolphin
elephant
emily
friend
fucker
ginger
goodluck
hammer
heather
iceman
jason
jessica
jesus
joseph
jupiter
justin
kevin
knight
lacrosse
lakers
lizard
madison
mary
mother
muffin
murphy
nirvana
paris
pentium
phoenix
picture
rainbow
sandy
saturn
scott
shannon
shithead
skeeter
sophie
special
stephanie
stephen
steve
sweetie
teacher
tennis
test
test123
tommy
topgun
tristan
wally
william
wilson
1q2w3e
654321
666666
a12345
a1b2c3d4
alpha
amber
angela
angie
archie
asdf
blazer
bond007
booger
charles
christin
claire
control
danny
david1
dennis
digital
disney
edward
elvis
felix
flipper
franklin
frodo
honda
horses
hunter
indigo
james
jasper
jeremy
julian
kelsey
killer
lauren
marie
maryjane
matrix
maverick
mayday
mercury
mitchell
morgan
mountain
niners
nothing
oliver
peace
peanut
pearljam
phantom
popcorn
princess
psycho
pumpkin
purple
randy
rebecca
reddog
robert
rocky
roses
salmon
samson
sharon
sierra
smokey
startrek
steelers
stimpy
sunflower
superman
support
sydney
techno
walter
willie
willow
winner
ziggy
zxcvbnm
alaska
alexis
alice
animal
apples
barbara
benjamin
billy
blue
bluebird
bobby
bonnie
bubba
camera
chocolate
clark
claudia
cocacola
compton
connect
cookie
cruise
douglas
dreamer
dreams
duckie
eagles
eddie
einstein
enter
explorer
faith
family
ferrari
flamingo
flower
foxtrot
francis
freddy
friday
froggy
giants
gizmo
global
goofy
happy1
hendrix
henry
herman
homer
honey
house
houston
iguana
indiana
insane
inside
irish
ironman
jake
jasmin
jeanne
jerry
joey
justice
katherine
kermit
kitty
koala
larry
leslie
logan
lucky
mark
martin
matt
minnie
misty
mitch
mouse
nancy
nascar
nelson
pantera
parker
penguin
peter
piano
pizza
prince
punkin
pyramid
raymond
robin
roger
rosebud
route66
royal
running
sadie
sasha
security
sheena
sheila
skiing
snapple
snowball
sparrow
spencer
spike
star
stealth
student
sunny
sylvia
tamara
taurus
teresa
theresa
thunderbird
tigers
tony
toyota
travel
tuesday
victory
viper1
wesley
whisky
winnie
winter
wolves
xyz123
zorro
123123
1234567
696969
888888
Anthony
Joshua
Matthew
Tigger
aaron
abby
abcdef
adidas
adrian
alfred
arthur
athena
austin
awesome
badger
bamboo
beagle
bears
beatles
beautiful
beaver
benny
bigmac
bingo
bitch
blonde
boogie
boston
brenda
bright
bubba1
bubbles
buffy
button
buttons
cactus
candy
captain
carlos
caroline
carrie
casper
catch22
chance
charity
charlotte
cheese
cheryl
chloe
chris1
clancy
compaq
conrad
cooper
cooter
copper
cosmos
cougar
cracker
crawford
crystal
curtis
cyclone
dance
diablo
dollars
dookie
dumbass
dundee
elizabeth
eric
europe
farmer
firebird
fletcher
fluffy
france
freak1
friends
fuckoff
gabriel
galaxy
gambit
garden
garfield
garnet
genesis
genius
godzilla
golfer
goober
grace
greenday
groovy
grover
guitar
hacker
harry
hazel
hector
herbert
horizon
hornet
howard
icecream
imagine
impala
jack
janice
jasmine
jason1
jeanette
jeffrey
jenifer
jenni
jesus1
jewels
joker
julie
julie1
junior
justin1
kathleen
keith
kelly
kelly1
kennedy
kevin1
knicks
larry1
leonard
lestat
library
lincoln
lionking
london
louise
lucky1
lucy
maddog
margaret
mariposa
marlboro
martin1
marty
master1
mensuck
mercedes
metal
midori
mikey
millie
mirage
molly
monet
money1
monica
monopoly
mookie
moose
moroni
music
naomi
nathan
nguyen
nicholas
nicole
nimrod
october
olive
olivia
online
oscar
oxford
pacific
painter
peaches
penelope
pepsi
petunia
philip
phoenix1
photo
pickle
player
poiuyt
porsche
porter
puppy
python
quality
raquel
raven
remember
robbie
robert1
roman
rugby
runner
russell
ryan
sailing
sailor
samantha
savage
scarlett
school
sean
seven
shadow1
sheba
shelby
shit
shoes
simba
simple
skipper
smiley
snake
snickers
sniper
snoopdog
snowman
sonic
spitfire
sprite
spunky
starwars
station
stella
stingray
storm
stormy
stupid
sunny1
sunrise
surfer
susan
tammy
tango
tanya
teddy1
theboss
theking
thumper
tina
tintin
tomcat
trebor
trevor
tweety
unicorn
valentine
valerie
vanilla
veronica
victor
vincent
viper
warrior
warriors
weasel
wheels
wilbur
winston
wisdom
wombat
xavier
yellow
zeppelin
1111
1212
Andrew
Family
Friends
Michael
Michelle
Snoopy
abcd1234
abcdefg
abigail
account
adam
alex1
alice1
allison
alpine
andre1
andrea1
angel1
anita
annette
antares
apache
apollo
aragorn
arizona
arnold
arsenal
asdfasdf
asdfg
asdfghjk
avenger
baby
babydoll
bailey
banana
barry
basket
batman1
beaner
beast
beatrice
bella
bertha
bigben
bigdog
biggles
bigman
binky
biology
bishop
blondie
bluefish
bobcat
bosco
braves
brazil
bruce
bruno
brutus
buffalo
bulldog
bullet
bullshit
bunny
business
butch
butler
butter
california
carebear
carol
carol1
carole
cassie
castle
catalina
catherine
cccccc
celine
center
champion
chanel
chaos
chelsea1
chester1
chicago
chico
christian
christy
church
cinder
colleen
colorado
columbia
commander
connie
cookies
cooking
corona
cowboys
coyote
craig
creative
cuddles
cuervo
cutie
daddy
daisy
daniel1
danielle
davids
death
denis
derek
design
destiny
diana
diane
dickhead
digger
dodger
donna
dougie
dragonfly
dylan
eagle
eclipse
electric
emerald
etoile
excalibur
express
fender
fiona
fireman
flash
florida
flowers
foster
francesco
francine
francois
frank
french
fuckface
gemini
general
gerald
germany
gilbert
goaway
golden
goldfish
goose
gordon
graham
grant
gregory
gretchen
gunner
hannah
harold
harrison
harvey
hawkeye
heaven
heidi
helen
helena
hithere
hobbit
ibanez
idontknow
integra
ireland
irene
isaac
isabel
jackass
jackie
jackson
jaguar
jamaica
japan
jenny1
jessie
johan
johnny
joker1
jordan23
judith
julia
jumanji
kangaroo
karen1
kathy
keepout
keith1
kenneth
kimberly
kingdom
kitkat
kramer
kristen
laura
laurie
lawrence
lawyer
legend
liberty
light
lindsay
lindsey
lisa
liverpool
lola
lonely
louis
lovely
loveme
lucas
madonna
malcolm
malibu
marathon
marcel
maria1
mariah
mariah1
marilyn
mario
marvin
maurice
maxine
maxwell
me
meggie
melanie
melissa
melody
mexico
michael1
michele
midnight
mike1
miracle
misha
mishka
molly1
monique
montreal
moocow
moore
morris
mouse1
mulder
nautica
nellie
newton
nick
nirvana1
nissan
norman
notebook
ocean
olivier
ollie
oranges
oregon
orion
panda
pandora
panther
passion
patricia
pearl
peewee
pencil
penny
people
percy
person
peter1
petey
picasso
pierre
pinkfloyd
polaris
police
pookie1
poppy
power
predator
preston
q1w2e3
queen
queenie
quentin
ralph
random
rangers
raptor
reality
redrum
remote
reynolds
rhonda
ricardo
ricardo1
ricky
river
roadrunner
robinhood
rocknroll
rocky1
ronald
roxy
ruthie
sabrina
sakura
sally
sampson
samuel
sandra
santa
sapphire
scarlet
scorpio
scott1
scottie
scruffy
seattle
serena
shanti
shark
shogun
simon
singer
skull
skywalker
slacker
smashing
smiles
snowflake
snuffy
soccer1
soleil
sonny
spanky
speedy
spider
spooky
stacey
star69
start
steven1
stinky
strawberry
stuart
sugar
sundance
superfly
suzanne
suzuki
swimmer
swimming
system
taffy
tarzan
teddy
teddybear
terry
theatre
thunder
thursday
tinker
tootsie
tornado
tracy
tricia
trident
trojan
truman
trumpet
tucker
turtle
tyler
utopia
voyager
warcraft
warlock
warren
water
wayne
wendy
williams
willy
winona
woody
woofwoof
wrangler
wright
xfiles
xxxxxx
yankees
yvonne
zebra
zenith
zigzag
zombie
zxc123
zxcvb
000000
007007
11111
11111111
123321
171717
181818
1a2b3c
1chris
4runner
54321
55555
6969
7777777
789456
88888888
Alexis
Bailey
Charlie
Chris
Daniel
Dragon
Elizabeth
HARLEY
Heather
Jennifer
Jessica
Jordan
KILLER
Nicholas
Password
Princess
Purple
Rebecca
Robert
Shadow
Steven
Summer
Sunshine
Superman
Taylor
Thomas
Victoria
abcd123
abcde
accord
active
africa
airborne
alfaro
alicia
aliens
alina
aline
alison
allen
aloha
alpha1
althea
altima
amanda1
amazing
america
amour
anderson
andre
andrew1
andromeda
angels
angie1
annie
anything
apple1
apple2
applepie
april
aquarius
ariane
ariel
arlene
artemis
asdf1234
asdfjkl
ashley1
ashraf
ashton
asterix
attila
autumn
avatar
babes
bambi
barbie
barney1
barrett
bball
beaches
beanie
beans
beauty
becca
belize
belle
belmont
benji
benson
bernardo
berry
betsy
betty
bigboss
bigred
billy1
birdie
birthday
biscuit
bitter
blackjack
blah
blanche
blood
blowjob
blowme
blueeyes
blues
bogart
bombay
boobie
boots
bootsie
boxers
brandi
brent
brewster
bridge
bronco
bronte
brooke
brother
bryan
bubble
buddha
budgie
burton
butterfly
byron
calendar
calvin1
camel
camille
campbell
camping
cancer
canela
cannon
carbon
carnage
carolyn
carrot
cascade
catfish
cathy
catwoman
cecile
celica
change
chantal
charger
cherry
chiara
chiefs
china
chris123
christ1
christmas
christopher
chuck
cindy1
cinema
civic
claude
clueless
cobain
cobra
cody
colette
college
colors
colt45
confused
cool
corvette
cosmo
country
crusader
cunningham
cupcake
cynthia
dagger
dammit
dancer
daphne
darkstar
darren
darryl
darwin
deborah
december
deedee
deeznuts
delano
delete
demon
denise
denny
desert
deskjet
detroit
devil
devine
devon
dexter
dianne
diesel
director
dixie
dodgers
doggy
dollar
dolly
dominique
domino
dontknow
doogie
doudou
downtown
dragon1
driver
dude
dudley
dutchess
dwight
eagle1
easter
eastern
edith
edmund
eight
element
elissa
ellen
elliot
empire
enigma
enterprise
erin
escort
estelle
eugene
evelyn
explore
family1
fatboy
felipe
ferguson
ferret
ferris
fireball
fishes
fishie
flight
florida1
flowerpot
forward
freddie
freebird
freeman
frisco
fritz
froggie
froggies
frogs
fucku
future
gabby
games
garcia
gaston
gateway
george1
georgia
german
germany1
getout
ghost
gibson
giselle
gmoney
goblin
goblue
gollum
grandma
gremlin
grizzly
grumpy
guess
guitar1
gustavo
haggis
haha
hailey
halloween
hamilton
hamlet
hanna
hanson
happy123
happyday
hardcore
harley1
harriet
harris
harvard
health
heart
heather1
heather2
hedgehog
helene
hello1
hello123
hellohello
hermes
heythere
highland
hilda
hillary
history
hitler
hobbes
holiday
holly
honda1
hongkong
hootie
horse
hotrod
hudson
hummer
huskies
idiot
iforget
iloveu
impact
indonesia
irina
isabelle
israel
italia
italy
jackie1
jacob
jakey
james1
jamesbond
jamie
jamjam
jeffrey1
jennie
jenny
jensen
jesse
jesse1
jester
jethro
jimbob
jimmy
joanna
joelle
john316
jordie
jorge
josh
journey
joyce
jubilee
jules
julien
juliet
junebug
juniper
justdoit
karin
karine
karma
katerina
katie
katie1
kayla
keeper
keller
kendall
kenny
ketchup
kings
kissme
kitten
kittycat
kkkkkk
kristi
kristine
labtec
laddie
ladybug
lance
laurel
lawson
leader
leland
lemon
lester
letter
letters
lexus1
libra
lights
lionel
little
lizzy
lolita
lonestar
longhorn
looney
loren
lorna
loser
lovers
loveyou
lucia
lucifer
lucky14
maddie
madmax
magic1
magnum
maiden
maine
management
manson
manuel
marcus
maria
marielle
marine
marino
marshall
martha
maxmax
meatloaf
medical
megan
melina
memphis
mermaid
miami
michel
michigan
mickey1
microsoft
mikael
milano
miles
millenium
million
miranda
miriam
mission
mmmmmm
mobile
monkey1
monroe
montana
monty
moomoo
moonbeam
morpheus
motorola
movies
mozart
munchkin
murray
mustang1
nadia
nadine
napoleon
nation
national
nestle
newlife
newyork1
nichole
nikita
nikki
nintendo
nokia
nomore
normal
norton
noway
nugget
number9
numbers
nurse
nutmeg
ohshit
oicu812
omega
openup
orchid
oreo
orlando
packard
packers
paloma
pancake
panic
parola
parrot
partner
pascal
patches
patriots
paula
pauline
payton
peach
peanuts
pedro1
peggy
perfect
perry
peterpan
philips
phillips
phone
pierce
pigeon
pink
pioneer
piper1
pirate
pisces
playboy
pluto
poetry
pontiac
pookey
popeye
prayer
precious
prelude
premier
puddin
pulsar
pussy
pussy1
qwert
qwerty12
qwertyui
rabbit1
rachelle
racoon
rambo
randy1
ravens
redman
redskins
reggae
reggie
renee
renegade
rescue
revolution
richard1
richards
richmond
riley
ripper
robby
roberts
rock
rocket1
rockie
rockon
roger1
rogers
roland
rommel
rookie
rootbeer
rosie
rufus
rusty
ruthless
sabbath
sabina
safety
saint
samiam
sammie
sammy
samsam
sandi
sanjose
saphire
sarah1
saskia
sassy
saturday
science
scooby
scoobydoo
scooter1
scorpion
scotty
scouts
search
september
server
seven7
sexy
shaggy
shanny
shaolin
shasta
shayne
shelly
sherry
shirley
shorty
shotgun
sidney
simba1
sinatra
sirius
skate
skipper1
skyler
slayer
sleepy
slider
smile1
smitty
smoke
snakes
snapper
snoop
solomon
sophia
space
sparks
spartan
spike1
sponge
spurs
squash
stargate
starlight
stars
steph1
steve1
stevens
stewart
stone
stranger
stretch
strong
studio
stumpy
sucker
suckme
sultan
summit
sunfire
sunset
super
superstar
surfing
susan1
sutton
sweden
sweetpea
sweety
swordfish
tabatha
tacobell
taiwan
tamtam
tanner
target
tasha
tattoo
tequila
terry1
texas
thankyou
theend
thompson
thrasher
tiger2
timber
timothy
tinkerbell
topcat
topher
toshiba
tototo
travis
treasure
trees
tricky
trish
triton
trombone
trouble
trucker
turbo
twins
tyler1
ultimate
unique
united
ursula
vacation
valley
vampire
vanessa
venice
venus
vermont
vicki
vicky
victor1
vincent1
violet
violin
virgil
virginia
vision
volley
voodoo
vortex
waiting
wanker
warner
water1
wayne1
webster
weezer
wendy1
western
white
whitney
whocares
wildcat
william1
wilma
window
winniethepooh
wolfgang
wolverine
wonder
xxxxxxxx
yamaha
yankee
yogibear
yolanda
yomama
yvette
zachary
zebras
zxcvbn
00000000
121212
1234qwer
131313
13579
90210
99999999
ABC123
action
amelie
anaconda
apollo13
artist
asshole
benoit
bernard
bernie
bigbird
blizzard
bluesky
bonjour
caesar
cardinal
carolina
cesar
chandler
chapman
charlie1
chevy
chiquita
chocolat
coco
cougars
courtney
dolphins
dominic
donkey
dusty
eminem
energy
fearless
forest
forever
glenn
guinness
hotdog
indian
jared
jimbo
johnson
jojo
josie
kristin
lloyd
lorraine
lynn
maxime
memory
mimi
mirror
nebraska
nemesis
network
nigel
oatmeal
patton
pedro
planet
players
portland
praise
psalms
qwaszx
raiders
rambo1
rancid
shawn
shelley
softball
speedo
sports
ssssss
steele
steph
stephani
sunday
tiffany
tigre
toronto
trixie
undead
valentin
velvet
viking
walker
watson
young
babygirl
pretty
hottie
teamo
987654321
naruto
spongebob
daniela
princesa
christ
blessed
single
qazwsx
pokemon
iloveyou1
iloveyou2
fuckyou1
hahaha
poop
blessing
blahblah
blink182
123qwe
trinity
passw0rd
google
looking
spirit
iloveyou!
qwerty1
onelove
mylove
222222
ilovegod
football1
loving
emmanuel
1q2w3e4r
red123
blabla
112233
hallo
spiderman
simpsons
monster
november
brooklyn
poopoo
darkness
159753
pineapple
chester
1qaz2wsx
drowssap
monkey12
wordpass
q1w2e3r4
coolness
11235813
something
alexandra
estrella
miguel
iloveme
sayang
princess1
555555
999999
alejandro
brittany
alejandra
tequiero
antonio
987654
00000
fernando
corazon
cristina
kisses
myspace
rebelde
babygurl
alyssa
mahalkita
gabriela
pictures
hellokitty
babygirl1
angelica
mahalko
mariana
eduardo
andres
ronaldo
inuyasha
adriana
celtic
samsung
angelo
456789
sebastian
karina
hotmail
0123456789
barcelona
cameron
slipknot
cutiepie
50cent
bonita
maganda
babyboy
natalie
cuteako
javier
789456123
123654
bowwow
portugal
777777
volleyball
january
cristian
bianca
chrisbrown
101010
sweet
panget
benfica
love123
lollipop
camila
qwertyuiop
harrypotter
ihateyou
christine
lorena
andreea
charmed
rafael
brianna
aaliyah
johncena
lovelove
gangsta
333333
hiphop
mybaby
sergio
metallica
myspace1
babyblue
badboy
fernanda
westlife
sasuke
steaua
roberto
slideshow
asdfghjkl
santiago
jayson
5201314
jerome
gandako
gatita
babyko
246810
sweetheart
chivas
alberto
valeria
nicole1
12345678910
leonardo
jayjay
liliana
sexygirl
232323
amores
anthony1
bitch1
fatima
miamor
lover
lalala
252525
skittles
colombia
159357
manutd
123456a
britney
katrina
christina
pasaway
mahal
tatiana
cantik
0123456
teiubesc
147258369
natalia
francisco
amorcito
paola
angelito
manchester
mommy1
147258
amigos
marlon
linkinpark
147852
diego
444444
iverson
andrei
justine
frankie
pimpin
fashion
bestfriend
england
hermosa
456123
102030
sporting
hearts
potter
iloveu2
number1
212121
truelove
jayden
savannah
hottie1
ganda
scotland
ilovehim
shakira
estrellita
brandon1
sweets
familia
love12
omarion
monkeys
loverboy
elijah
ronnie
mamita
999999999
broken
rodrigo
westside
mauricio
amigas
preciosa
shopping
flores
isabella
martinez
elaine
friendster
cheche
gracie
connor
valentina
darling
santos
joanne
fuckyou2
pebbles
sunshine1
gangster
gloria
darkangel
bettyboop
jessica1
cheyenne
dustin
iubire
a123456
purple1
bestfriends
inlove
batista
karla
chacha
marian
sexyme
pogiako
jordan1
010203
daddy1
daddysgirl
billabong
pinky
erika
skater
nenita
tigger1
gatito
lokita
maldita
buttercup
bambam
glitter
123789
sister
zacefron
tokiohotel
loveya
lovebug
bubblegum
marissa
cecilia
lollypop
nicolas
puppies
ariana
chubby
sexybitch
roxana
mememe
susana
baller
hotstuff
carter
babylove
angelina
playgirl
sweet16
012345
bhebhe
marcos
loveme1
milagros
lilmama
beyonce
lovely1
catdog
armando
margarita
151515
loves
202020
gerard
undertaker
amistad
capricorn
delfin
cheerleader
password2
PASSWORD
lizzie
matthew1
enrique
badgirl
141414
dancing
cuteme
amelia
skyline
angeles
janine
carlitos
justme
legolas
michelle1
cinderella
jesuschrist
ilovejesus
tazmania
tekiero
thebest
princesita
lucky7
jesucristo
buddy1
regina
myself
lipgloss
jazmin
rosita
chichi
pangit
mierda
741852963
hernandez
arturo
silvia
melvin
celeste
pussycat
gorgeous
honeyko
mylife
babyboo
loveu
lupita
panthers
hollywood
alfredo
musica
hawaii
sparkle
kristina
sexymama
crazy
scarface
098765
hayden
micheal
242424
0987654321
marisol
jeremiah
mhine
isaiah
lolipop
butterfly1
xbox360
madalina
anamaria
yourmom
jasmine1
bubbles1
beatriz
diamonds
friendship
sweetness
desiree
741852
hannah1
bananas
julius
leanne
marie1
lover1
twinkle
february
bebita
87654321
twilight
imissyou
pollito
ashlee
cookie1
147852369
beckham
simone
nursing
torres
damian
123123123
joshua1
babyface
dinamo
mommy
juliana
cassandra
redsox
gundam
0000
ou812
dave
golf
molson
Monday
newpass
thx1138
Internet
coke
foobar
abc
fish
fred
help
ncc1701d
newuser
none
pat
dog
duck
duke
floyd
guest
joe
kingfish
micro
sam
telecom
test1
7777
absolut
babylon5
backup
bill
bird33
deliver
fire
flip
galileo
gopher
hansolo
jane
jim
mom
passwd
phil
phish
porsche911
rain
red
sergei
training
truck
video
volvo
007
1969
5683
Bond007
Friday
Hendrix
October
Taurus
aaa
alexandr
catalog
challenge
clipper
coltrane
cyrano
dan
dawn
dean
deutsch
dilbert
e-mail
export
ford
fountain
fox
frog
gabriell
garlic
goforit
grateful
hoops
lady
ledzep
lee
mailman
mantra
market
mazda1
metallic
ncc1701e
nesbitt
open
pete
quest
republic
research
supra
tara
testing
xanadu
xxxx
zaphod
zeus
0007
1022
10sne1
1973
1978
2000
2222
3bears
Broadway
Fisher
Jeanne
Killer
Knight
Master
Pepper
Sierra
Tennis
abacab
abcd
ace
acropolis
amy
anders
avenir
basil
bass
beer
ben
bliss
blowfish
boss
bridges
buck
bugsy
bull
cannondale
canon
catnip
chip
civil
content
cook
cordelia
crack1
cyber
daisie
dark1
database
deadhead
denali
depeche
dickens
emmitt
entropy
farout
farside
feedback
fidel
firenze
fish1
fletch
fool
fozzie
fun
gargoyle
gasman
gold
graphic
hell
image
intern
intrepid
jeff
jkl123
joel
johanna1
kidder
kim
king
kirk
kris
lambda
leon
logical
lorrie
major
mariner
mark1
max
media
merlot
midway
mine
mmouse
moon
mopar
mortimer
nermal
nina
olsen
opera
overkill
pacers
packer
picard
polar
polo
primus
prometheus
public
radio
rastafarian
reptile
rob
robotech
rodeo
rolex
rouge
roy
ruby
salasana
scarecrow
scout
scuba1
sergey
skibum
skunk
sound
starter
sting1
sunbird
tbird
teflon
temporal
terminal
the
thejudge
time
toby
today
tokyo
tree
trout
vader
val
valhalla
windsurf
wolf
wolf1
xcountry
yoda
yukon
1213
1214
1225
1313
1818
1975
1977
1991
1kitty
2001
2020
2112
2kids
333
4444
5050
57chevy
7dwarfs
Animals
Ariel
Bismillah
Booboo
Boston
Carol
Computer
Creative
Curtis
Denise
Eagles
Esther
Fishing
Freddy
Gandalf
Golden
Goober
Hacker
Harley
Henry
Hershey
Jackson
Jersey
Joanna
Johnson
Katie
Kitten
Liberty
Lindsay
Lizard
Madeline
Margaret
Maxwell
Money
Monster
Pamela
Peaches
Peter
Phoenix
Piglet
Pookie
Rabbit
Raiders
Random
Russell
Sammy
Saturn
Skeeter
Smokey
Sparky
Speedy
Sterling
Theresa
Thunder
Vincent
Willow
Winnie
Wolverine
aaaa
aardvark
abbott
acura
admin
admin1
adrock
aerobics
agent
airwolf
ali
alien
allegro
allstate
altamira
altima1
andrew!
ann
anne
anneli
aptiva
arrow
asdf;lkj
assmunch
baraka
barnyard
bart
bartman
beasty
beavis1
bebe
belgium
beowulf
beryl
best
bharat
bichon
bigal
biker
bilbo
bills
bimmer
biochem
birdy
blinds
blitz
bluejean
bogey
bogus
boulder
bourbon
boxer
brain
branch
britain
broker
bucks
buffett
bugs
bulls
burns
buzz
c00per
calgary
camay
carl
cat
cement
cessna
chad
chainsaw
chameleon
chang
chess
chinook
chouette
chronos
cicero
circuit
cirque
cirrus
clapton
clarkson
class
claudel
cleo
cliff
clock
color
comet
concept
concorde
coolbean
corky
cornflake
corwin
cows
crescent
cross
crowley
cthulhu
cunt
current
cutlass
daedalus
dagger1
daily
dale
dana
daytek
dead
decker
dharma
dillweed
dipper
disco
dixon
doitnow
doors
dork
doug
dutch
effie
ella
elsie
engage
eric1
ernie1
escort1
excel
faculty
fairview
faust
fenris
finance
first
fishhead
flanders
fleurs
flute
flyboy
flyer
franka
frederic
free
front242
frontier
fugazi
funtime
gaby
gaelic
gambler
gammaphi
garfunkel
garth
gary
gateway2
gator1
gibbons
gigi
gilgamesh
goat
godiva
goethe
gofish
good
gramps
gravis
gray
greed
greg
greg1
greta
gretzky
guido
gumby
h2opolo
hamid
hank
hawkeye1
health1
hello8
help123
helper
homerj
hoosier
hope
huang
hugo
hydrogen
ib6ub9
insight
instructor
integral
iomega
iris
izzy
jazz
jean
jeepster
jetta1
joanie
josee
joy
julia2
jumbo
jump
justice4
kalamazoo
kali
kat
kate
kerala
kids
kiwi
kleenex
kombat
lamer
laser
laserjet
lassie1
leblanc
legal
leo
life
lions
liz
logger
logos
loislane
loki
longer
lori
lost
lotus
lou
macha
macross
madoka
makeitso
mallard
marc
math
mattingly
mechanic
meister
mercer
merde
merrill
michal
michou
mickel
minou
mobydick
modem
mojo
montana3
montrose
motor
mowgli
mulder1
muscle
neil
neutrino
newaccount
nicklaus
nightshade
nightwing
nike
none1
nopass
nouveau
novell
oaxaca
obiwan
obsession
orville
otter
ozzy
packrat
paint
papa
paradigm
pass
pavel
peterk
phialpha
phishy
piano1
pianoman
pianos
pipeline
plato
play
poetic
print
printing
provider
qqq111
quebec
qwer
racer
racerx
radar
rafiki
raleigh
rasta1
redcloud
redfish
redwing
redwood
reed
rene
reznor
rhino
ripple
rita
robocop
robotics
roche
roni
rossignol
rugger
safety1
saigon
satori
saturn5
schnapps
scotch
scuba
secret3
seeker
services
sex
shanghai
shazam
shelter
sigmachi
signal
signature
simsim
skydive
slick
smegma
smiths
smurfy
snow
sober1
sonics
sony
spazz
sphynx
spock
spoon
spot
sprocket
starbuck
steel
stephi
sting
stocks
storage
strat
strato
stud
student2
susanna
swanson
swim
switzer
system5
t-bone
talon
tarheel
tata
tazdevil
tester
testtest
thisisit
thorne
tightend
tim
tom
tool
total
toucan
transfer
transit
transport
trapper
trash
trophy
tucson
turbo2
unity
upsilon
vedder
vette
vikram
virago
visual
volcano
walden
waldo
walleye
webmaster
wedge
whale1
whit
whoville
wibble
will
wombat1
word
world
x-files
xxx123
zack
zepplin
zoltan
zoomer
123go
21122112
5555
911
FuckYou
Fuckyou
Gizmo
Hello
Michel
Qwerty
Windows
angus
aspen
ass
bird
booster
byteme
cats
changeit
christia
christoph
classroom
cloclo
corrado
dasha
fiction
french1
fubar
gator
gilles
gocougs
hilbert
hola
home
judy
koko
lulu
mac
macintosh
mailer
mars
meow
ne1469
niki
paul
politics
pomme
property
ruth
sales
salut
scrooge
skidoo
spain
surf
sylvie
symbol
forum
rotimi
god
saved
2580
1998
xxx
1928
777
info
a
netware
sun
tech
doom
mmm
one
ppp
1911
1948
1996
5252
Champs
Tuesday
bach
crow
don
draft
hal9000
herzog
huey
jethrotull
jussi
mail
miki
nicarao
snowski
1316
1412
1430
1952
1953
1955
1956
1960
1964
1qw23e
2200
2252
3010
3112
4788
6262
Alpha
Bastard
Beavis
Cardinal
Celtics
Cougar
Darkman
Figaro
Fortune
Geronimo
Hammer
Homer
Janet
Mellon
Merlot
Metallic
Montreal
Newton
Paladin
Peanuts
Service
Vernon
Waterloo
Webster
aki123
aqua
aylmer
beta
bozo
car
chat
chinacat
cora
courier
dogbert
eieio
elina1
fly
funguy
fuzz
ggeorge
glider1
gone
hawk
heikki
histoire
hugh
if6was9
ingvar
jan
jedi
jimi
juhani
khan
lima
midvale
neko
nesbit
nexus6
nisse
notta1
pam
park
pole
pope
pyro
ram
reliant
rex
rush
seoul
skip
stan
sue
suzy
tab
testi
thelorax
tika
tnt
toto1
tre
wind
x-men
xyz
zxc
369
Abcdef
Asdfgh
Changeme
NCC1701
Zxcvbnm
demo
doom2
good-luck
homebrew
m1911a1
nat
ne1410s
ne14a69
zhongguo
sample123
0852
basf
OU812
!@#$%
informix
majordomo
news
temp
trek
!@#$%^
!@#$%^&*
Pentium
Raistlin
adi
bmw
law
new
opus
plus
visa
www
zzz
1332
1950
3141
3533
4055
4854
6301
Bonzo
ChangeMe
Front242
Gretel
Michel1
Noriko
Sidekick
Sverige
Swoosh
Woodrow
ayelet
barn
betacam
biz
boat
cuda
doc
hal
hallowell
haro
hosehead
ilmari
irmeli
j1l2t3
jer
kcin
kerrya
kissa2
leaf
lissabon
mart
matti1
mech
morecats
paagal
performa
prof
ratio
ship
slip
stivers
tapani
targas
test2
test3
tula
unix
user1
xanth
!@#$%^&
1701d
@#$%^&
Qwert
allo
dirk
newcourt
nite
notused
sss
PK� �\�\�innodb_memcached_config.sqlnu�[���create database innodb_memcache;

use innodb_memcache;

-- ------------------------------------------------------------------------
-- Following are set of "configuration tables" that used to configure
-- the InnoDB Memcached.
-- ------------------------------------------------------------------------

-- ------------------------------------------------------------------------
-- Table `cache_policies`
--
-- Each record in this table represents a named caching policy, specifying:
--  * How the memcache GET command is executed, including whether to get
--    records from local cache only, from InnoDB only, from local cache if
--    present (treating InnoDB as a backing store), or not at all.
--  * Similarly, how memcache SET commands are executed.
--  * How memcache DELETE commands are executed.
--  * Whether flushing the cache should cause a mass delete from NDB.
--
-- ------------------------------------------------------------------------
CREATE  TABLE IF NOT EXISTS `cache_policies` (
	`policy_name` VARCHAR(40) PRIMARY KEY,
	`get_policy` ENUM('innodb_only', 'cache_only', 'caching','disabled')
	 NOT NULL ,
	`set_policy` ENUM('innodb_only', 'cache_only','caching','disabled')
	 NOT NULL ,
	`delete_policy` ENUM('innodb_only', 'cache_only', 'caching','disabled')
	 NOT NULL,
	`flush_policy` ENUM('innodb_only', 'cache_only', 'caching','disabled')
	 NOT NULL
) ENGINE = innodb;

-- ------------------------------------------------------------------------
-- Table `containers`
--
-- A container record describes an InnoDB table used for data storage by
-- InnoDB Memcache.
-- There must be a unique index on the `key column`, and unique index name
-- is specified in the `unique_idx_name_on_key` column of the table
-- `value_columns` are comma-separated lists of the columns that make up
-- the memcache key and value. Each column width is defined such that they
-- are in consistent with NDB memcached.
-- ------------------------------------------------------------------------

CREATE  TABLE IF NOT EXISTS `containers` (
	`name` varchar(50) not null primary key,
	`db_schema` VARCHAR(250) NOT NULL,
	`db_table` VARCHAR(250) NOT NULL,
	`key_columns` VARCHAR(250) NOT NULL,
	`value_columns` VARCHAR(250),
	`flags` VARCHAR(250) NOT NULL DEFAULT "0",
	`cas_column` VARCHAR(250),
	`expire_time_column` VARCHAR(250),
	`unique_idx_name_on_key` VARCHAR(250) NOT NULL
) ENGINE = InnoDB;

CREATE  TABLE IF NOT EXISTS `config_options` (
	`name` varchar(50) not null primary key,
	`value` varchar(50)) ENGINE = InnoDB;

-- ------------------------------------------------------------------------
-- This is an example
-- We create a InnoDB table `demo_test` is the `test` database
-- and insert an entry into contrainers' table to tell InnoDB Memcache
-- that we has such InnoDB table as back store:
-- c1 -> key
-- c2 -> value
-- c3 -> flags
-- c4 -> cas
-- c5 -> exp time
-- PRIMARY -> use primary key to search
-- ------------------------------------------------------------------------

INSERT INTO containers VALUES ("aaa", "test", "demo_test",
			       "c1", "c2",  "c3", "c4", "c5", "PRIMARY");

INSERT INTO cache_policies VALUES("cache_policy", "innodb_only",
				  "innodb_only", "innodb_only", "innodb_only");

INSERT INTO config_options VALUES("separator", "|");
INSERT INTO config_options VALUES("table_map_delimiter", ".");

CREATE DATABASE IF NOT EXISTS test;
USE test

-- ------------------------------------------------------------------------
-- Key (c1) must be VARCHAR or CHAR type, memcached supports key up to 255
-- Bytes
-- Value (c2) must be VARCHAR or CHAR type
-- Flag (c3) is a 32 bits integer
-- CAS (c4) is a 64 bits integer, per memcached define
-- Exp (c5) is again a 32 bits integer
-- ------------------------------------------------------------------------
CREATE TABLE demo_test (c1 VARCHAR(32),
			c2 VARCHAR(1024),
			c3 INT, c4 BIGINT UNSIGNED, c5 INT, primary key(c1))
ENGINE = INNODB;

INSERT INTO demo_test VALUES ("AA", "HELLO, HELLO", 8, 0, 0);
PK� �\qW<���install_rewriter.sqlnu�[���/* Copyright (c) 2015, 2025, Oracle and/or its affiliates.

This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License, version 2.0,
   as published by the Free Software Foundation.

This program is designed to work with certain software (including
   but not limited to OpenSSL) that is licensed under separate terms,
   as designated in a particular file or component or in included license
   documentation.  The authors of MySQL hereby grant you an additional
   permission to link the program and your derivative works with the
   separately licensed software that they have either included with
   the program or referenced in the documentation.

This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License, version 2.0, for more details.

You should have received a copy of the GNU General Public License
   along with this program; if not, write to the Free Software
   Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA */

CREATE DATABASE IF NOT EXISTS query_rewrite;

CREATE TABLE IF NOT EXISTS query_rewrite.rewrite_rules (
  id INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
  pattern VARCHAR(5000) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
  pattern_database VARCHAR(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin,
  replacement VARCHAR(5000) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
  enabled ENUM('YES', 'NO') CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL
    DEFAULT 'YES',
  message VARCHAR(1000) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin,
  pattern_digest VARCHAR(64),
  normalized_pattern VARCHAR(100)
) DEFAULT CHARSET = utf8mb4 ENGINE = INNODB;

INSTALL PLUGIN rewriter SONAME 'rewriter.so';
CREATE FUNCTION load_rewrite_rules RETURNS STRING
SONAME 'rewriter.so';

DELIMITER //

CREATE PROCEDURE query_rewrite.flush_rewrite_rules()
BEGIN
  DECLARE message_text VARCHAR(100);
  COMMIT;
  SELECT load_rewrite_rules() INTO message_text;
  IF NOT message_text IS NULL THEN
    SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = message_text;
  END IF;
END //

DELIMITER ;
PK� �\峉Y��mysql-log-rotatenu�[���# Copyright (c) 2000, 2025, Oracle and/or its affiliates.
# 
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2.0,
# as published by the Free Software Foundation.
#
# This program is designed to work with certain software (including
# but not limited to OpenSSL) that is licensed under separate terms,
# as designated in a particular file or component or in included license
# documentation.  The authors of MySQL hereby grant you an additional
# permission to link the program and your derivative works with the
# separately licensed software that they have either included with
# the program or referenced in the documentation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License, version 2.0, for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA

# The log file name and location can be set in
# /etc/my.cnf by setting the "log-error" option
# in either [mysqld] or [mysqld_safe] section as
# follows:
#
# [mysqld]
# log-error=/var/lib/mysql/mysqld.log
#
# In case the root user has a password, then you
# have to create a /root/.my.cnf configuration file
# with the following content:
#
# [mysqladmin]
# password = <secret> 
# user= root
#
# where "<secret>" is the password. 
#
# ATTENTION: The /root/.my.cnf file should be readable
# _ONLY_ by root !

/var/lib/mysql/mysqld.log {
        # create 600 mysql mysql
        notifempty
        daily
        rotate 5
        missingok
        compress
    postrotate
	# just if mysqld is really running
	if test -x /usr/bin/mysqladmin && \
	   /usr/bin/mysqladmin ping &>/dev/null
	then
	   /usr/bin/mysqladmin flush-logs
	fi
    endscript
}
PK� �\q���uninstall_rewriter.sqlnu�[���/* Copyright (c) 2015, 2025, Oracle and/or its affiliates.

This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License, version 2.0,
   as published by the Free Software Foundation.

This program is designed to work with certain software (including
   but not limited to OpenSSL) that is licensed under separate terms,
   as designated in a particular file or component or in included license
   documentation.  The authors of MySQL hereby grant you an additional
   permission to link the program and your derivative works with the
   separately licensed software that they have either included with
   the program or referenced in the documentation.

This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License, version 2.0, for more details.

You should have received a copy of the GNU General Public License
   along with this program; if not, write to the Free Software
   Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301  USA */

DROP DATABASE IF EXISTS query_rewrite;
DROP FUNCTION load_rewrite_rules;
UNINSTALL PLUGIN rewriter;
PK� �\�b�o����bulgarian/errmsg.sysnu�[���PK� �\�c\ELEL�charsets/Index.xmlnu�[���PK� �\��^���@charsets/READMEnu�[���PK� �\�#�{{�Gcharsets/armscii8.xmlnu�[���PK� �\�ֺHmmy_charsets/ascii.xmlnu�[���PK� �\0�@""(wcharsets/cp1250.xmlnu�[���PK� �\�f�@l"l"��charsets/cp1251.xmlnu�[���PK� �\�[����0�charsets/cp1256.xmlnu�[���PK� �\�%�v�$�$�charsets/cp1257.xmlnu�[���PK� �\%Imm�charsets/cp850.xmlnu�[���PK� �\�?�}}�charsets/cp852.xmlnu�[���PK� �\[!�����(charsets/cp866.xmlnu�[���PK� �\h�g�ll�@charsets/dec8.xmlnu�[���PK� �\z�vdwwH\charsets/geostd8.xmlnu�[���PK� �\��=�KKtcharsets/greek.xmlnu�[���PK� �\���Wrr��charsets/hebrew.xmlnu�[���PK� �\/ۈ,iiE�charsets/hp8.xmlnu�[���PK� �\�"!H���charsets/keybcs2.xmlnu�[���PK� �\]�	qq��charsets/koi8r.xmlnu�[���PK� �\�ooi�charsets/koi8u.xmlnu�[���PK� �\����=(=(charsets/latin1.xmlnu�[���PK� �\�%ա++�/charsets/latin2.xmlnu�[���PK� �\#%ppNcharsets/latin5.xmlnu�[���PK� �\�Ikq���echarsets/latin7.xmlnu�[���PK� �\:�MYZ!Z!��charsets/macce.xmlnu�[���PK� �\~�Xe!e!��charsets/macroman.xmlnu�[���PK� �\y8��mm=�charsets/swe7.xmlnu�[���PK� �\��t������czech/errmsg.sysnu�[���PK� �\K��r�r���danish/errmsg.sysnu�[���PK� �\ݘuh�h�j�dutch/errmsg.sysnu�[���PK� �\�y�ɕ����english/errmsg.sysnu�[���PK� �\��'
����� estonian/errmsg.sysnu�[���PK� �\�J�Q��ɥ&french/errmsg.sysnu�[���PK� �\!�F�++��,german/errmsg.sysnu�[���PK� �\�̦�h�2greek/errmsg.sysnu�[���PK� �\�YZ��ĵ8hungarian/errmsg.sysnu�[���PK� �\q��e�e��>italian/errmsg.sysnu�[���PK� �\��m
m
ŠDjapanese/errmsg.sysnu�[���PK� �\|L�Au�u�u�Jkorean/errmsg.sysnu�[���PK� �\ �������+�Pnorwegian/errmsg.sysnu�[���PK� �\�2���J�Vnorwegian-ny/errmsg.sysnu�[���PK� �\��6�6���\polish/errmsg.sysnu�[���PK� �\���6���bportuguese/errmsg.sysnu�[���PK� �\�6��E�E�L~hromanian/errmsg.sysnu�[���PK� �\��+�+�unrussian/errmsg.sysnu�[���PK� �\C�**�����tserbian/errmsg.sysnu�[���PK� �\�������
�zslovak/errmsg.sysnu�[���PK� �\2�&���spanish/errmsg.sysnu�[���PK� �\�ю������swedish/errmsg.sysnu�[���PK� �\k����z�ukrainian/errmsg.sysnu�[���PK� �\?�*���	��	D��messages_to_clients.txtnu�[���PK� �\����D0�messages_to_error_log.txtnu�[���PK� �\`�7r�c�c�E�dictionary.txtnu�[���PK� �\�\����innodb_memcached_config.sqlnu�[���PK� �\qW<������install_rewriter.sqlnu�[���PK� �\峉Y���¢mysql-log-rotatenu�[���PK� �\q����ʢuninstall_rewriter.sqlnu�[���PK99j6Т

/home/emeraadmin/www/node_modules/form-data/../d3-array/../debug/../../4d695/mysql-8.0.zip